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-2303912 | AGENDA | Approval | SA2#156E meeting Agenda | SA WG2 Chair | Approved | Approved | ||
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#155 Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2303913 | REPORT | Approval | Draft Report of SA WG2 meeting #155 | SA WG2 Secretary | Approved | Approved | ||
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=57 | - | |
| 4.1 | - | - | - | QoS across 5G and Wi-Fi | - | - | Docs:=3 | - | |
| 4.1 | S2-2303915 | LS In | Information | LS from Wi-Fi Alliance: Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks | Wi-Fi Alliance (20221202_WiFi_Alliance) | Revision of postponed S2-2302181 from S2#155. Response drafted in S2-2304475. Noted | Noted | ||
| 4.1 | S2-2304475 | LS OUT | Approval | [DRAFT] LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks | Nokia, Nokia Shanghai Bell | Response to S2-2303915. r05 agreed. Revised to S2-2305730. | Mehrdad (Mediatek Inc.) suggests some changes in the LS reply. Curt (Meta) suggests additional changes in the LS reply below in this. Mehrdad (Samsung) thinks meta suggested changes are related to item 1 and not item 2. Curt (Meta) disagrees with your (Mehrdad) assessment. Laurent (Nokia): provides r01 Marco (Huawei): provides r02 Mehrdad (Mediatek Inc.) can not agree with original version, r01 and r02. Marco (Huawei) comments. Laurent (Nokia): provides r03 Mehrdad (Mediatek Inc.) provides r04 Laurent (Nokia): provides r05 ==== Revisions Deadline ==== Curt (Meta.) is okay with r05 but needs a little editorial fix. Marco (Huawei) ok with R05 + Charter's comment . Object r00, r01 Laurent (Nokia): objects to R02 and R04. Can agree with additions but not with removal proposed by Curt for R05 Sebastian (Qualcomm) is ok with r05 with the following change ' How the mapping is done between 3GPP QoS and DSCP marking (or other Non-3GPP QoS) at the WLAN interface is left to implementation and configuration and considered outside 3GPP scope. ' Mehrdad (Mediatek Inc.) is ok r04, r05 or with r05 + editorial changes as worded by Nokia or Qualcomm, i.e. only adding 'How' and 'is done' but no removal. We object to rest of revisions and original version. Marco (Huawei) is ok with r05 + QC wording. Curt (Meta) is ok with r05 + QC wording as well. ==== Comments Deadline ==== | Revised | |
| 4.1 | S2-2305730 | LS OUT | Approval | LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks | SA WG2 | - | Revision of S2-2304475r05. Approved | Approved | |
| 4.1 | - | - | - | Allowed PDU sessions status IE in non-allowed service area | - | - | Docs:=11 | - | |
| 4.1 | S2-2303916 | LS In | Action | LS from CT WG1: LS on Handling of the Allowed PDU session status IE in Non-allowed service area | CT WG1 (C1-227197) | Rel-18 | Revision of postponed S2-2302183 from S2#155. Responses drafted in S2-2304059, S2-2304589, S2-2305059, S2-2305391. Postponed | Hannu (Nokia) asks which one of the candidate reply LSs should we take as template for further revisions? Lalith(Samsung) replies to Hannu (Nokia) | Postponed |
| 4.1 | S2-2304059 | LS OUT | Approval | [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area | Apple (UK) Limited | Rel-18 | Response to S2-2303916. Merged into S2-2305059 (Postponed) Merge into (revision of) S2-2305059 | Lalith(Samsung) proposes to Merge this tdoc into 5059 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 4.1 | S2-2304589 | LS OUT | Approval | [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area | LG Electronics | Rel-18 | Response to S2-2303916. Merged into S2-2305059 (Postponed) | Lalith(Samsung) proposes to Merge this tdoc into 5059 Myungjune (LGE) is ok to merge this tdoc into 5059 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 4.1 | S2-2305391 | LS OUT | Approval | [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area | OPPO | Response to S2-2303916. Merged into S2-2305059 (Postponed) Merge into (revision of) S2-2305059 | Lalith(Samsung) proposes to Merge this tdoc into 5059 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed | |
| 4.1 | S2-2305059 | LS OUT | Approval | [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area | Samsung | Response to S2-2303916. CC#4. r05 revised to S2-2306255. No agreement. Postponed. Agree r02 + Lalith’s changes? For CC#4. | Haris(Qualcomm) provides r01 Lalith(Samsung) comments on r01 Haris(Qualcomm) responds Lalith(Samsung) responds Haris(Qualcomm) disagrees with Lalith Hannu (Nokia) provides r02. Peng (OPPO) provides r03. ==== Revisions Deadline ==== Haris(Qualcomm) is ok with r01, r02, or r03, objects to r00 Myungjune (LGE) is ok with any revision but prefer r00, r01, r02. Lalith(Samsung) objects r01, r02, or r03. Prefers r00. Hannu (Nokia) prefers r02, can live with r00 and r01. r03 goes too deep into CT1 area and we can't justify such statements on SA2 specifications. Haris(Qualcomm) comments Lalith(Samsung) replies Lalith(Samsung) proposes a way forward Haris(Qualcomm) suggests to Lalith to make text proposal for the LS response Lalith(Samsung) proposes r04 in the draft folder. Lalith (Samsung) proposes to agree r02 with below changes: Include below text under Answer to Q1: It is not clear from SA2 specs if emergency PDU session can be active over non-3GPP access when the scenario described in CT1 LS occurs. SA2 will align their spec after CT1 decision on this point 1st para of Answer2 is replaced by this: Answer: UE shall not include the Uplink data status IE (referred as List Of PDU Sessions To Be Activated in TS 23.501/23.502) and request User Plane resource establishment except for PDU session of emergency services/MPS/MCX in non-allowed area Peng (OPPO) provides comments ==== Comments Deadline ==== Haris(Qualcomm) post revision r04 from Lalith is ok for me Hannu (Nokia) can agree the r02 + revisions from Lalith that is published as late revision r04. Peng (OPPO) is fine with r04+ after adding the proposed statement Peng (OPPO) is fine with r05 | Postponed | |
| 4.1 | S2-2306255 | LS OUT | Approval | [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area | Samsung | - | Revision of S2-2305059r05. CC#4: WITHDRAWN | Withdrawn | |
| 4.1 | S2-2304058 | DISCUSSION | Decision | Handling of the List of allowed PDU sessions IE when the UE is in a non-allowed area | Apple (UK) Limited | Rel-18 | Noted | Noted | |
| 4.1 | S2-2305057 | DISCUSSION | Discussion | Discussion on Service area restrictions and emergency/MCS/MPX | Samsung | Rel-18 | Noted | Haris(Qualcomm) provides comments Lalith(Samsung) comments Haris(Qualcomm) responds ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304060 | CR | Approval | 23.501 CR4199 (Rel-18, 'F'): UE handling of the List of allowed PDU sessions in non-allowed area | Apple (UK) Limited | Rel-18 | CR Cover sheet error! Noted | Lalith(Samsung) proposes to NOTE this paper, based on way forward discussed during CC#1 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304061 | CR | Approval | 23.502 CR3958 (Rel-18, 'F'): UE handling of the List of allowed PDU sessions in non-allowed area | Apple (UK) Limited | Rel-18 | CR Cover sheet error! Noted | Lalith(Samsung) proposes to NOTE this paper, based on way forward discussed during CC#1 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304189 | CR | Approval | 23.501 CR3846R3 (Rel-18, 'F'): Non-allowed area clarification | Ericsson, Samsung, LG Electronics | Rel-18 | Revision of S2-2302318 from S2#155. Noted | Lalith(Samsung) provides r01 Hannu (Nokia) provides r02 and co-signs. Haris(Qualcomm) objects to r01 Haris(Qualcomm) objects to r02, can only accept r00 Hannu (Nokia) provides r03 and answers to Haris Haris(Qualcomm) responds to Hannu Hannu (Nokia) answers to Haris ==== Revisions Deadline ==== Qian (Ericsson) prefers r00, but can live with r03 Hannu (Nokia) prefers to have a decision in this meeting. Either r00 or R03 is acceptable. Haris(Qualcomm) objects to r01, r02 and r03. Accepts only r00 Myungjune (LGE) is ok with r00 or r03 Lalith (Samsung) objects r00. Prefer r01 can live with r02 or r03. Guillaume (MediaTek Inc.) - both r00 and r03 are ok Robert (Apple) responds to the previous e-mails from Qualcomm, Samsung and Mediatek. Lalith(Samsung) responds to Apple. Robert (Apple) responds to Samsung. ==== Comments Deadline ==== | Noted |
| 4.1 | - | - | - | UE memory available for SMS | - | - | Docs:=4 | - | |
| 4.1 | S2-2303938 | LS In | Action | LS from CT WG4: LS on UE memory available for SMS | CT WG4 (C4-230625) | Rel-17 | Response drafted in S2-2304381 (noted). Postponed | Hannu (Nokia) proposes to mark this LS as POSTPONED. The CRs (S2-2304379, 4380) related with the reply LS (S2-2304381) could not be agreed, so we still have a problem to solve next time. | Postponed |
| 4.1 | S2-2304381 | LS OUT | Approval | [DRAFT] LS on UE memory available for SMS | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2303938. Noted | Qian (Ericsson) provides comments and r01 based on alternative for 4379r03 Hannu (Nokia) still prefers r00 and at least an indication of the affected release. ==== Revisions Deadline ==== Qian (Ericsson) can only go with r01. Objects to r00 Hannu (Nokia) comments that this LS depends on the CR that is intended to be attached. No point in discussing the LS text unless we can agree the CR. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304379 | CR | Approval | 23.502 CR3996 (Rel-17, 'F'): SMS memory available | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | LaeYoung (LGE) provides comments. Qian (Ericsson) provides comments and r01. LaeYoung (LGE) is OK with r01. Hannu (Nokia) cannot agree r01, provides r02 and explains why. LaeYoung (LGE) asks a Q on r00 and r02. Hannu (Nokia) answers to LaeYoung Qian (Ericsson) provides further comments LaeYoung (LGE) provides comment. Qian (Ericsson) provides comments and an alternative in r03 Hannu (Nokia) cannot agree r03 as it is incomplete and explains why the comment from LaeYuong on registration is correct. ==== Revisions Deadline ==== Qian (Ericsson) prefers r01 and ok to live with r03. Objects to all other revisions Hannu (Nokia) prefers r02. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304380 | CR | Approval | 23.502 CR3997 (Rel-18, 'A'): SMS memory available | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Noted | Hannu (Nokia) comments that even though we normally do not revise Cat A mirror CRs until the end of the discussion, in addition to the updates that are eventually agreed on Cat F CR, there will be one more on the cover page to correct the reference TS version number. Qian (Ericsson) agrees with the statement from Hannu(Nokia). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | - | - | - | GSMA 5GMMR’s Liaisons | - | - | Docs:=5 | - | |
| 4.1 | S2-2303923 | LS In | Action | LS from GSMA 5GMRR: LS to 3GPP on GSMA requirements regarding intermediaries in the roaming ecosystem (Roaming Hub, IPX and RVAS Providers) | GSMA 5GMRR (5GMRR Doc 41_37r2) | Noted. CC#4: This was postponed. | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | S2-2303924 | LS In | Action | LS from GSMA 5GMRR: LS to 3GPP on IPX Requirements for 5GS Roaming | GSMA 5GMRR (5GMRR#41 Doc 38r2) | Noted. CC#4: This was postponed. | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | S2-2303925 | LS In | Action | LS from GSMA 5GMRR: LS Roaming Value Added Service Requirements | GSMA 5GMRR (5GMRR Doc 41_39r2) | Noted. CC#4: This was postponed. | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | S2-2303926 | LS In | Action | LS from GSMA 5GMRR: LS with Roaming Hubbing requirements and LS response to 3GPP SA3 LS (S3-214456) on 5GS Roaming Hubbing | GSMA 5GMRR (5GMRR Doc 41_40r4) | Noted. CC#4: This was postponed. | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | S2-2303927 | LS In | Action | LS from GSMA 5GMRR: LS on GSMA 5GMRR Working solution assumption on L-PRINS and Data Session Control | GSMA 5GMRR (5GMRR Doc 41_41r3) | Noted. CC#4: This was postponed. | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | - | - | - | 3GPP/non-3GPP VoWi-Fi interworking | - | - | Docs:=2 | - | |
| 4.1 | S2-2303991 | LS In | Information | LS from GSMA TSGUEWIFI: LS to 3GPP SA WG2 on 3GPP and non-3GPP interworking information for VoWiFi | GSMA TSGUEWIFI (UEWIFI07_003) | GSMA revision: This LS should indicate 'Supporting VoNR' in row 1 if the table. Postponed | Laurent (Nokia): Further work may be needed and it is better to postpone this LS Ting Zhang (China Telecom) suggests SA2 address this issue and reply a LS to GSMA. James Jin (vivo) provides comments. Haris(Qualcomm) suggests to postpone the LS, see technical comments in thread of S2-2305264 Ting Zhang (China Telecom) replies to James Jin | Postponed | |
| 4.1 | S2-2305264 | DISCUSSION | Discussion | Discussion on network 3GPP and non-3GPP interworking indication for VoWiFi | China Telecommunications,Xiaomi | Noted | Ting Zhang (China Telecom) provides r01. Haris(Qualcomm) comments Yildirim (Charter) seeks clarification whether the proposed solution would work for both untrusted and trusted non-3GPP access. Ting Zhang (China Telecom) replies to Haris ==== Revisions Deadline ==== Ting Zhang ( China Telecom ) replies to Yildirim (Charter) . ==== Comments Deadline ==== | Noted | |
| 4.1 | - | - | - | APIs for GMEC and AIMLSys services | - | - | Docs:=7 | - | |
| 4.1 | S2-2303934 | LS In | Action | LS from CT WG3: LS on API enhancement for GMEC services and AIMLSys services | CT WG3 (C3-230783) | Rel-18 | Responses drafted in S2-2304257, S2-2304440, S2-2304588, S2-2305040 (noted). Postponed | Postponed | |
| 4.1 | S2-2304255 | DISCUSSION | Discussion | R18 AIMLsys_GMEC Discussion on a general service operation for Group QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 4.1 | S2-2305039 | DISCUSSION | Discussion | Discussion the enhanced NEF API for AIMLSys and GMEC | QUALCOMM JAPAN LLC. | Rel-18 | Noted | Noted | |
| 4.1 | S2-2304257 | LS OUT | Approval | [DRAFT] Reply LS to CT WG3 on Single SO for QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Response to S2-2303934. Noted | Dongjoo (Nokia) provides r01 based on the SoH taken at CC#2 Tricci (OPPO) thanks Dongjoo (Nokia) revised LSout to CT3 and provides r02. Dongjoo (Nokia) provides r03 Tricci (OPPO) thanks Dongjoo (Nokia) provides the revision, however, OPPO does not think the current answer in Question 2 is accurate. Dongjoo (Nokia) responds to Tricci (OPPO) Tricci (OPPO) responds to Dongjoo (Nokia) question. Dongjoo (Nokia) provides feedback to Tricci (OPPO) Tricci (OPPO) agrees with Dongjoo (Nokia) assessments and let's hear more others' opinions. Thanks. Juan Zhang (Qualcomm) provides r04. Qianghua (Huawei) provides r05 Dongjoo (Nokia) object r05 Tricci (OPPO) agrees with Dongjoo (Nokia) and also objects r05. OPPO will ask to re-open this issue in CC#3. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) objects r05 and proposed to agree r04. Qianghua (Huawei) object r00 to r04, only accept r05, or r05 removing 'Yes' in first answer and 'SA2 agrees to not merge GMEC API with AIMLsys API' Dongjoo (Nokia) provides r06. Qianghua (Huawei) objects also to r06. Suggest to postpone or simply state the status as proposed below and ask CT3 what is real technical concern to use separate API. Any hints that SA2 makes formal decision to merge the APIs are not reflecting the truth. That is an indicative vote to get the view in the room. There is no objection vote thus no formal decision. ==== Comments Deadline ==== Dongjoo (Nokia) agrees to Postpone this LS and responds to Qianghua (Huawei). | Noted |
| 4.1 | S2-2304440 | LS OUT | Approval | [DRAFT] ReplyLS on API enhancement for GMEC services and AIMLSys services | Huawei, HiSilicon | Rel-18 | Response to S2-2303934. Merged into S2-2304257 (noted) | Tricci <OPPO> proposes to note this ReplyLS based on the decision in CC#2. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2304588 | LS OUT | Approval | [DRAFT] Reply LS to CT WG3 on API enhancement for GMEC/AIMLSys services | Samsung | Rel-18 | Response to S2-2303934. Merged into S2-2304257 (noted) | Tricci <OPPO> proposes to note this ReplyLS based on the decision in CC#2. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2305040 | LS OUT | Approval | [DRAFT] LS on API enhancement for GMEC services and AIMLSys services | QUALCOMM JAPAN LLC. | Rel-18 | Response to S2-2303934. Merged into S2-2304257 (noted) | Noted | |
| 4.1 | - | - | - | 5QI Priority Level in QoS constraints | - | - | Docs:=6 | - | |
| 4.1 | S2-2305105 | CR | Approval | 23.501 CR3748R1 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-18 | Revision of S2-2209065 from 2022! r00 agreed. Revised to S2-2305731. | Pallab (Nokia) provides comments and requests for clarification Shabnam (Ericsson) would like to mention that the WI code as well as agenda is wrong for this paper and 3 related papers. Offline provided comments before, so expect some updates to be provided including WI code update. Maybe something to discuss at CC#3 to finalise if going forward. Robert (Peraton Labs) provides r01 per suggestions. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2305731 | CR | Approval | 23.501 CR3748R2 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-18 | Revision of S2-2305092r01. Approved | Agreed | |
| 4.1 | S2-2305109 | CR | Approval | 23.502 CR3601R1 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile | Rel-18 | Revision of S2-2209191 from 2022! CR Cover sheet error! r00 agreed. Revised to S2-2305732. | Pallab (Nokia) provides has same comments as discussed in S2-2305105. This CR depends on the outcome of S2-2305105 Shabnam (Ericsson) would like to mention that the WI code as well as agenda is wrong for this paper and 2 related papers. Offline provided comments before, so expect some updates to be provided including WI code update. Maybe something to discuss at CC#3 to finalise if going forward. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2305732 | CR | Approval | 23.502 CR3601R2 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-18 | Revision of S2-2305098r01. Approved | Agreed | |
| 4.1 | S2-2305110 | CR | Approval | 23.503 CR0757R1 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-18 | Revision of S2-2209067 from 2022! r03 agreed. Revised to S2-2305733. | Pallab (Nokia) has same comments as discussed in S2-2305105. This CR depends on the outcome of S2-2305105 Robert (Peraton Labs) provides r01 Shabnam (Ericsson) r02 provided, would like to mention that the WI code as well as agenda is wrong for this paper and 2 related papers. Offline provided comments before, WI code and Category update. Maybe something to discuss at CC#3 to finalise if going forward. Robert (Peraton Labs) responds to Shabnam (Ericsson) and provides r03. ==== Revisions Deadline ==== Pallab (Nokia) is OK with r03. Points out one small editorial error. May be we can open it in CC#3 to correct? Robert (Peraton Labs) responds to Pallab (Nokia). ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2305733 | CR | Approval | 23.503 CR0757R2 (Rel-18, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-18 | Revision of S2-2305110r03. Approved | Agreed | |
| 4.1 | - | - | - | Others | - | - | Docs:=19 | - | |
| 4.1 | S2-2305396 | LS In | Information | LS from GSMA NG/UPG: LS from NG to SA WG4 on IMS Data Channel (multiple application data channels support in a single SDP m=line) | GSMA NG/UPG (UPG06_110r2) | Rel-16 | Noted | Rainer (Nokia) proposes to note the LS. | Noted |
| 4.1 | S2-2303918 | LS In | Action | LS from SA WG5: Reply LS on reporting dynamic satellite backhaul parameters to CHF | SA WG5 (S5-226685) | Rel-18 | Revision of postponed S2-2302192 from S2#155. Noted | Guanglei (Huawei) proposes to move this LS to 9.1.2 5GSATB and note it, as it is for information. Hucheng (CATT) proposes to NOTE this LS due to no real action in SA2. Jean-Yves (Thales) OK to NOTE this LS. Stefan (Ericsson) supports noting the LS | Noted |
| 4.1 | S2-2303937 | LS In | Information | LS from CT WG4: LS Reply on PRINS middle boxes | CT WG4 (C4-230547) | Noted | Noted | ||
| 4.1 | S2-2303939 | LS In | Action | LS from CT WG4: Reply LS on Identifier availability for Lawful Interception during Inter-PLMN handover | CT WG4 (C4-230628) | Rel-18 | Noted | Laurent (Nokia): propose to NOTE the LS (no real action as CT4 have done what we were asking for) Fenqin (Huawei): we share the same view as Laurent and also suggest to NOTE the LS. | Noted |
| 4.1 | S2-2303968 | LS In | Information | LS from SA WG3: LS reply to TSG SA on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future – identified gaps from 5G ACIA | SA WG3 (S3-231387) | Noted | Laurent (Nokia): proposes to Note this LS for Info | Noted | |
| 4.1 | S2-2303969 | LS In | Action | LS from SA WG3: LS Reply on PRINS middle boxes | SA WG3 (S3-231389) | Postponed | Thomas (Nokia) requests to postpone the LS instead of noting it as the LS was for 'action' | Postponed | |
| 4.1 | S2-2303970 | LS In | Action | Reply LS on PLMN ID used in Roaming Scenarios | SA WG3 (S3-231391) | Rel-17 | Noted | Thomas (Nokia) proposes to Note the LS | Noted |
| 4.1 | S2-2303975 | LS In | Action | LS from SA WG4: An Invitation to the SA WG4 Gender Diversity Committee Meetings | SA WG4 (S4-230431) | Postponed | Shabnam (Ericsson) proposes to NOTE the LS, unless chair wants to raise it at one of the remaining CC and then NOTE. | Postponed | |
| 4.1 | S2-2303976 | LS In | Action | LS on management of AS by AF | SA WG4 (S4-230436) | Rel-18 | Postponed | Laurent (Nokia): Further work may be needed and it is better to postpone this LS Hui(Huawei) support to postpone the LS | Postponed |
| 4.1 | S2-2303978 | LS In | Action | LS from SA WG5: Reply LS on CHF Logic Realization w.r.t. Spending Limits functionality | SA WG5 (S5-232735) | Rel-18 | Noted | Pallab (Nokia): propose to NOTE the LS as no response is needed to SA5 | Noted |
| 4.1 | S2-2303979 | LS In | Action | LS from SA WG5: LS on the provisioning services specified in SA WG5 | SA WG5 (S5-232774) | Rel-18 | Postponed | Postponed | |
| 4.1 | S2-2303980 | LS In | Action | LS from SA WG5: LS on 3GPP work on Energy Efficiency | SA WG5 (S5-232903) | Rel-18 | Noted | Alessio (Nokia) asks to note this LS (no identified for immediate action) Jungshin (Samsung) also proposes to note the LS | Noted |
| 4.1 | S2-2303981 | LS In | Information | LS from SA WG5: LS reply to Reply LS on Network federation interface for Telco edge consideration | SA WG5 (S5-233146) | Rel-18 | Noted | Laurent (Nokia): proposes to Note this LS for Info | Noted |
| 4.1 | S2-2303982 | LS In | Information | LS from SA WG5: LS reply to Reply LS cc: SA WG5 on Network federation interface for Telco edge consideration | SA WG5 (S5-233147) | Rel-18 | Noted | Laurent (Nokia): proposes to Note this LS for Info | Noted |
| 4.1 | S2-2303987 | LS In | Information | LS from SA WG6: LS reply to TSG SA on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future – identified gaps from 5G ACIA | SA WG6 (S6-231068) | Noted | Laurent (Nokia): proposes to Note this LS for Info | Noted | |
| 4.1 | S2-2303988 | LS In | Information | LS from SA WG6: LS on SA WG6 V2X service support | SA WG6 (S6-231091) | Rel-18 | Postponed | Shabnam (Ericsson) provides comments that there seems to be some misunderstanding of the work split between SA2 and SA6 described in this LS, SA2 should provide response indicating so, see details. Mehrdad (Mediatek Inc.) suggests this to be addressed at SA plenary. Shabnam (Ericsson) provides comments to postpone the LS so SA2 can respond with details, SA can respond on its own merit but SA2 needs to correct the understanding and architecture put forward in the LS with SA2 role. Mehrdad (Mediatek Inc.) agrees with Ericsson suggestion to postpone this. | Postponed |
| 4.1 | S2-2303990 | LS In | Action | LS from GSMA OPG: LS on publication of GSMA OPG and OPAG documents | GSMA OPG (OPG_128_Doc_03) | Noted | Noted | ||
| 4.1 | S2-2305394 | LS In | Information | LS from TSG SA: Reply LS on 5G capabilities exposure for factories of the future - identified gaps | TSG SA (SP-230384) | Rel-18 | Noted | Shabnam (Ericsson) proposes to NOTE the LS. | Noted |
| 4.1 | S2-2305395 | LS In | Information | LS from TSG SA: Alignment of activities on UE data collection reporting and event exposure | TSG SA (SP-230394) | Rel-19 | Noted | Shabnam (Ericsson) propose to NOTE the LS since there is no action for SA2, we wait for SA4 response if anything is needed in future. | Noted |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=0 | - | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=0 | - | |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=0 | - | |
| 5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | Docs:=0 | - | |
| 5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | Docs:=0 | - | |
| 6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Docs:=0 | - | |
| 6.1 | - | - | - | General aspects, concepts and reference models | - | - | Docs:=0 | - | |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=6 | - | |
| 6.2 | S2-2304246 | CR | Approval | 23.501 CR4251 (Rel-15, 'F'): Requested S-NSSAI status clarification | Samsung | Rel-15 | Noted | Stefano (Qualcomm) stage 3 assumes a 'reply' is provided for all S-NSSAIs, no need to remove before Release 18. Fei (OPPO) comments. Ashok (Samsung) clarifies. Ashok (Samsung) responds to Fei (OPPO) Fei (OPPO) replied to Ashok (Samsung) Alessio(Nokia) Comments that the stage two as is is correct. No need to do any changes. Whether stage 3 has decided to provide a IE to say neither rejected nor allowed that is fine and consistent. Ashok (Samsung) provides answers to Fei (OPPO) Alessio(Nokia) believes it is intentional that if a slice is not rejected it can be requested via MRU Ashok (Samsung) replies to Alessio Fei (OPPO) provides further clarification. Patrice (Huawei) supports Alessio's statement. Genadi (Lenovo) supports Alessio's comment and proposes to keep the existing description. Ashok ( Samsung) provides further comments Guillaume (MediaTek Inc.) comments - not FASMO. Ashok (Samsung) responds to Guillaume Peter Hedman (Ericsson) objects to the CR Ashok (Samsung) is OK to NOTE the CR and only Rel 18 can be considered Alessio(Nokia) thinks that even for rel-18 the text in spec is good. No need of CR. Ulises (InterDigital) provides comments - we also don't think the issue raised with this CR is FASMO ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2304248 | CR | Approval | 23.501 CR4252 (Rel-16, 'A'): Requested S-NSSAI status clarification | Samsung | Rel-16 | Noted | Stefano (Qualcomm) stage 3 assumes a 'reply' is provided for all S-NSSAIs, no need to remove before Release 18. Ashok (Samsung) clarifies. Patrice (Huawei) proposes to keep the discussion of the mirror CRs in 4246 for now. Peter Hedman (Ericsson) objects to the CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2304253 | CR | Approval | 23.501 CR4254 (Rel-17, 'A'): Requested S-NSSAI status clarification | Samsung | Rel-17 | Noted | Stefano (Qualcomm) stage 3 assumes a 'reply' is provided for all S-NSSAIs, no need to remove before Release 18. Ashok (Samsung) clarifies. Patrice (Huawei) proposes to keep the discussion of the mirror CRs in 4246 for now. Peter Hedman (Ericsson) objects to the CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2304256 | CR | Approval | 23.501 CR4256 (Rel-18, 'A'): Requested S-NSSAI status clarification | Samsung | Rel-18 | Noted | Stefano (Qualcomm) stage 3 assumes a 'reply' is provided for all S-NSSAIs, we are OK with this clarification for Release 18. Patrice (Huawei) proposes to keep the discussion of the mirror CRs in 4246 for now. Peter Hedman (Ericsson) provides comments Jinguo(ZTE) provides comments Iskren (NEC) provides comments. Ashok (Samsung) comments Fei (OPPO) comments and the CR is not needed. Ashok (Samsung) is OK to NOTE because same comment is repeated that the statement gives flexibility for UE to retry the S-NSSAI and hence not to remove it. But problem was not about UE retrying, rather AMF is not able to process the request once it receives from UE and this will repeat without leading to successful execution. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2304317 | CR | Approval | 23.502 CR3991 (Rel-17, 'F'): On correcting the clause number in SMS over NAS procedure | Huawei, HiSilicon | Rel-17 | Approved | Agreed | |
| 6.2 | S2-2304318 | CR | Approval | 23.502 CR3992 (Rel-18, 'A'): On correcting the clause number in SMS over NAS procedure | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=0 | - | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=0 | - | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=4 | - | |
| 6.6 | S2-2304529 | CR | Approval | 23.502 CR4028 (Rel-17, 'F'): PCRT during EPS interworking | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2306026. | Pallab (Nokia) provides comments Belen (Ericsson) provides r01 Belen (Ericsson) provides r02 Haiyang (Huawei) provides r03 based on r02 Pallab (Nokia) OK with r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.6 | S2-2306026 | CR | Approval | 23.502 CR4028R1 (Rel-17, 'F'): PCRT during EPS interworking | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2304529r03. Approved | Agreed | |
| 6.6 | S2-2304530 | CR | Approval | 23.502 CR4029 (Rel-18, 'A'): PCRT during EPS interworking | Huawei, HiSilicon | Rel-18 | r00 agreed. Revised to S2-2306027. | Pallab (Nokia): Please see comments/discussions in S2-2304529 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.6 | S2-2306027 | CR | Approval | 23.502 CR4029R1 (Rel-18, 'A'): PCRT during EPS interworking | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304530r00. Approved | Agreed | |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=2 | - | |
| 6.7 | S2-2305081 | CR | Approval | 23.501 CR4476 (Rel-18, 'F'): Clarification related to LADN PDU session. | Samsung | Rel-18 | r02 agreed. Revised to S2-2306028. | LiMeng (Huawei) comments. Lalith (Samsung) provides r01 Hannu (Nokia) provides r02 Guillaume (MediaTek Inc.) asks for clarification Lalith(Samsung) replies Hannu (Nokia) comments Guillaume (MediaTek Inc.) comments. OK with the CR. Lalith (Samsung) comments Lalith(Samsung) comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.7 | S2-2306028 | CR | Approval | 23.501 CR4476R1 (Rel-18, 'F'): Clarification related to LADN PDU session. | Samsung | Rel-18 | Revision of S2-2305081r02. Approved | Agreed | |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=0 | - | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=0 | - | |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=0 | - | |
| 7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Docs:=0 | - | |
| 7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | Docs:=0 | - | |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=12 | - | |
| 7.2 | S2-2304071 | CR | Approval | 23.316 CR2079 (Rel-16, 'F'): Clarification of URSP handling for 5G-RG | Qualcomm | Rel-16 | Postponed | Marco (Huawei) comments and disagree Yildirim (Charter) comments and disagrees applying proposed restrictions to 5G-RG. Sebastian (Qualcomm) replies to Yildrim and Marco Sriram(CableLabs) comments and disagrees applying proposed restrictions to 5G-RG. Marco (Huawei) answers to Sebastian Sebastian (Qualcomm) replies to Marco Sebastian (Qualcomm) provides r01 Laurent (Nokia): provides r02 Sebastian (Qualcomm) comments on r02 Yildirim (Charter) comments; don't see the need for putting URSP restrictions on 5G-RG. Sebastian (Qualcomm) provides r03 Yildirim (Charter) replies Sebastian (Qualcomm). ==== Revisions Deadline ==== Marco (Huawei) ok R03, object r00, r01, r02. OK also to send an LS Sebastian (Qualcomm) replies to Yildrim (Charter) Sebastian (Qualcomm) supports r03 and in addition sending an LS to BBF/CableLabs; only sending an LS does not make sense because we need to clarify the status of our (3GPP) specs since matching of URSP rules for traffic for devices behind 5G-RG is simply not specified in 3GPP specs for Rel-16/Rel-17 (matter of fact) Ojas (Comcast) has strong concerns and do not agree to the revisions proposed for Rel-16/17/18 specs without liasing with BBF and CableLabs and gathering their feedback. Yildirim (Charter) replies to Sebastian (Qualcomm) Sebastian (Qualcomm) responds Sebastian (Qualcomm) replies to Yildirim ==== Comments Deadline ==== | Postponed |
| 7.2 | S2-2304072 | CR | Approval | 23.316 CR2080 (Rel-17, 'A'): Clarification of URSP handling for 5G-RG | Qualcomm | Rel-17 | Postponed | Marco (Huawei) comments and disagree Yildirim (Charter) comments and disagrees applying proposed restrictions to 5G-RG. Sriram(CableLabs) comments and disagrees applying proposed restrictions to 5G-RG. Marco (Huawei) mirror version based on 4071 to be created ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.2 | S2-2304073 | CR | Approval | 23.316 CR2081 (Rel-18, 'A'): Clarification of URSP handling for 5G-RG | Qualcomm | Rel-18 | Postponed | Marco (Huawei) comment and disagree Yildirim (Charter) comments and disagrees applying proposed restrictions to 5G-RG. Sriram(CableLabs) comments and disagrees applying proposed restrictions to 5G-RG. Marco (Huawei) mirror version based on 4071 to be created., but it may be merged to R18 global CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.2 | S2-2304491 | CR | Approval | 23.502 CR3873R1 (Rel-16, 'F'): Clarification on roaming scenario of N5CW device | Huawei, HiSilicon | Rel-16 | Revision of S2-2302260 from S2#155. Approved | Agreed | |
| 7.2 | S2-2304492 | CR | Approval | 23.502 CR3874R1 (Rel-17, 'F'): Clarification on roaming scenario of N5CW device | Huawei, HiSilicon | Rel-17 | Revision of S2-2302261 from S2#155. Approved | Agreed | |
| 7.2 | S2-2304493 | CR | Approval | 23.502 CR3875R1 (Rel-18, 'A'): Clarification on roaming scenario of N5CW device | Huawei, HiSilicon | Rel-18 | Revision of S2-2302262 from S2#155. Approved | Agreed | |
| 7.2 | S2-2305095 | CR | Approval | 23.501 CR4481 (Rel-17, 'F'): User location when 5G-RG is a TNAP | Huawei, HiSilicon | Rel-17 | Noted | Laurent (Nokia): has concerns: Is the change needed? These changes are not needed as 5G-RG Id is not defined, the release is frozen and transfer of Other information is already specified. Stefan (Ericsson) has same concerns as Nokia Marco (Huawei) is ok to Note this doc ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc ==== Comments Deadline ==== | Noted |
| 7.2 | S2-2305096 | CR | Approval | 23.501 CR4482 (Rel-18, 'A'): User location when 5G-RG is a TNAP | Huawei, HiSilicon | Rel-18 | Noted | Laurent (Nokia): Similar comment/ concerns as for 5095: this CR is not needed or would interfere with 5WWC_Ph2 work Marco(Huawei) replay to Laurent (Nokia) on technical issue Stefan (Ericsson) has same concerns as Nokia, and provides comments Marci (Huawei) is ok to Note this doc ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc ==== Comments Deadline ==== | Noted |
| 7.2 | S2-2305097 | CR | Approval | 23.502 CR4107 (Rel-17, 'F'): User location when 5G-RG is a TNAP | Huawei, Hisilicon | Rel-17 | r03 agreed. Revised to S2-2306029. | Laurent (Nokia): has concerns: Is the change needed? : changes are not needed, as 5G-RG Id is not defined and the release is frozen and Other information are already specified Marco (Huawei) answer to Laurent (Nokia): on the technical issue Stefan (Ericsson) has same concerns as Nokia and provides comments and provides r01 Chunhui(Xiaomi) shares the same concerns as Nokia and Ericsson. Laurent (Nokia): the version from Stefan can make it BUT the cover sheet has to be dramatically simplified Marco (Huawei): comment r01 Yannick (Convenor): To record that r02 was provided by Marco (Huawei). Stefan (Ericsson) replies to Marco Stefan (Ericsson) provides r03 ==== Revisions Deadline ==== Marco (Huawei) OK to r03 Laurent (Nokia): objects to any version except R03 ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2306029 | CR | Approval | 23.502 CR4107R1 (Rel-17, 'F'): User location when 5G-RG is a TNAP | Huawei, HiSilicon | Rel-17 | Revision of S2-2305097r03. Approved | Agreed | |
| 7.2 | S2-2305098 | CR | Approval | 23.502 CR4108 (Rel-18, 'A'): User location when 5G-RG is a TNAP | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2306030. | Laurent (Nokia): similar comment / concerns as for 5097: this CR is not needed or would interfere with 5WWC_Ph2 work Stefan (Ericsson) has same concerns as Nokia Marco (Huawei) provide r01 aligned to 5097 as Mirror CR Laurent (Nokia): the cover sheet should be dramatically simplified (and aligned with the actual CR text) Marco (Huawei) provide r02 aligned to 5097 as Mirror CR Marco (Huawei) mirror to approved version of 5097 to be prepared ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2306030 | CR | Approval | 23.502 CR4108R1 (Rel-18, 'F'): User location when 5G-RG is a TNAP | Huawei, HiSilicon | Rel-18 | Revision of S2-2305098. Approved | Agreed | |
| 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:=3 | - | |
| 7.4 | S2-2303941 | LS In | Action | LS from CT WG4: LS on Network Triggered Service Request for a UE in Suspend State | CT WG4 (C4-230664) | Rel-17 | Response drafted in S2-2304193. Final response in S2-2306031 | Replied to | |
| 7.4 | S2-2304193 | LS OUT | Approval | [DRAFT] Reply LS on Network Triggered Service Request for UE in Suspend State | Ericsson Inc. | Rel-17 | Response to S2-2303941. r03 agreed. Revised to S2-2306031. | Hannu (Nokia) comments that instead of using N1N2MessageTransfer with dummy data, we should consider also the option of SMF sending Namf_MT_EnableUEReachability. Sebastian (Qualcomm) is not ok with with r00, suggests changes Sebastian (Qualcomm) provides r01 and objects to r00 Qian (Ericsson) provides comments and r02 Hannu (Nokia) thanks Qian for r02 but provides r03 ==== Revisions Deadline ==== Qian (Ericsson) is ok with r03 ==== Comments Deadline ==== | Revised |
| 7.4 | S2-2306031 | LS OUT | Approval | Reply LS on Network Triggered Service Request for a UE in Suspend State | SA WG2 | Rel-17 | Revision of S2-2304193r03. Approved | Approved | |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=0 | - | |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=1 | - | |
| 7.7 | S2-2304541 | CR | Approval | 23.501 CR4337 (Rel-16, 'F'): Provide port Identity to use for each supported time domain to DS-TT and NW-TT | Qualcomm | Rel-16 | Postponed | Shabnam (Ericsson) provides comments that overall we are ok with the CR and options selected, with some suggestions below Zhendong (ZTE) provides comments. Sebastian (Qualcomm) replies and provides r01 Shabnam (Ericsson) ok with changes, but would like to clarify if Rel-17/18 will have any additional protocol impacts (maybe the limit) or simply interoperability aspects for Rel-16 and may not be mirrors? Qianghua (Huawei) questions on the identified issue and proposes to postpone the CR Zhendong (ZTE) agree with huawei. It proposes to postpone the CR ==== Revisions Deadline ==== Sebastian (Qualcomm) replies to Zhendong and Qianghua Zhendong (ZTE) provides response. Qianghua (Huawei) replies Qianghua (Huawei) proposes to postpone or note this meeting. (object to all revs for chair's notes) Sebastian (Qualcomm) is ok to postpone to give others more time to check internally ==== Comments Deadline ==== | Postponed |
| 7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | Docs:=6 | - | |
| 7.8 | S2-2305192 | CR | Approval | 23.502 CR4123 (Rel-16, 'F'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell | Rel-16 | CR Cover sheet error! r02 agreed. Revised to S2-2306032. | Josep (Deutsche Telekom) comments, provides r01, co-signs. Thomas(Nokia), provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.8 | S2-2306032 | CR | Approval | 23.502 CR4123R1 (Rel-16, 'F'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell, Deutsche Telekom | Rel-16 | Revision of S2-2305192r02. Approved | Agreed | |
| 7.8 | S2-2305194 | CR | Approval | 23.502 CR4125 (Rel-17, 'A'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell | Rel-17 | CR Cover sheet error! r00 agreed. Revised to S2-2306033. | Revised | |
| 7.8 | S2-2306033 | CR | Approval | 23.502 CR4125R1 (Rel-17, 'A'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell, Deutsche Telekom | Rel-17 | Revision of S2-2305194r00. Approved | Agreed | |
| 7.8 | S2-2305197 | CR | Approval | 23.502 CR4126 (Rel-18, 'A'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! r00 agreed. Revised to S2-2306034. | Revised | |
| 7.8 | S2-2306034 | CR | Approval | 23.502 CR4126R1 (Rel-18, 'A'): Reinstating definition of Nnrf_NFManagement_NFStatusUnsubscribe service operation | Nokia, Nokia Shanghai-Bell, Deutsche Telekom | Rel-18 | Revision of S2-2305197r00. Approved | Agreed | |
| 7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | Docs:=10 | - | |
| 7.9 | S2-2303962 | LS In | Action | LS from RAN WG3: LS on IAB Authorization | RAN WG3 (R3-231010) | Rel-16 | Response drafted in S2-2304728. Postponed | Postponed | |
| 7.9 | S2-2304728 | LS OUT | Approval | [DRAFT] Reply LS on IAB Authorization | Huawei, HiSilicon | Rel-16 | Response to S2-2303962. Postponed | Alessio(nokia) Comments and suggests not sending LS reply till we are clear on what needs to be done. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304183 | CR | Approval | 23.501 CR4229 (Rel-18, 'F'): IAB node release handling | Ericsson | Rel-18 | r01 agreed. Revised to S2-2306035. | LiMeng (Huawei) comments. Judy (Ericsson) supports LiMeng (Huawei)'s proposal to use this thread for further discussion and comments. LiMeng (Huawei) withdrawn the comment below since it is on the wrong document. Judy (Ericsson) withdraws comment on this thread Qian (Ericsson) provides comments. Alessio(nokia) cannot agree with this CR and explains why Qian (Ericsson) provides comments and r01 Alessio(Nokia) comments this is going in the right direction but we still need to define that the IAB node shall do after this deregistration. Qian (Ericsson) provides further comments. Alessio(Nokia) comments that since we have a open legacy and future behavior discussion at same time at this meeting in this agenda item we should have a clear outcome for both once and for all. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.9 | S2-2306035 | CR | Approval | 23.501 CR4229R1 (Rel-18, 'F'): IAB node release handling | Ericsson | Rel-18 | Revision of S2-2304183r01. Approved | Agreed | |
| 7.9 | S2-2304729 | CR | Approval | 23.401 CR3728 (Rel-16, 'F'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-16 | Postponed | Alessio(nokia) suggests to focus discussion on 730 and then see how to proceed with 729 ==== Revisions Deadline ==== Alessio(nokia) 730 is still unstable we cannot produce a corresponding 729 ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304730 | CR | Approval | 23.501 CR4388 (Rel-16, 'F'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-16 | Postponed | Alessio(nokia) provides r01 Qian (Ericsson) provides comments and check if the update for legacy IAB is good enough for rel-18 LiMeng (Huawei) provides r02 and suggests to focusing on the RAN alignment. Alessio(Nokia) provides comments : how is the AMF aware of a IAB-UE (and in prospect VMR) if it tries to register at a ;location where the NG-RAN does not support VMR/IAB? Alessio(Nokia) comments that we have still issues as there is no well-defined state machine that says what the IAB-UE can do ... also the NAs level state machine is totally left implementation dependent. We would like to put this as a high priority discussion as people want to align MBSR behavior to this unspecified IAB-UE behaviour and this is not acceptable to us. Hence r01 is the basis of what we can consider acceptable. RAN3 is not expecting any reply LS from us so we can discuss this further if people need more time. LiMeng (Huawei) comments. NAS enhancement is not Cat F CR, and there is no chance to update as such. ==== Revisions Deadline ==== LiMeng (Huawei) responses to Alessio, clarifies this document is to align RAN's LS in, and suggests to go with r02. Qian (Ericsson) can only accept r02. Objects to all other revisions. Alessio(nokia) proposes to postpone this and have a comprehensive offline discussion till next meeting with interested companies ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304731 | CR | Approval | 23.401 CR3729 (Rel-17, 'A'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-17 | Postponed | Alessio(nokia) suggests to focus discussion on 730 and then see how to proceed ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304732 | CR | Approval | 23.501 CR4389 (Rel-17, 'A'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-17 | Postponed | Alessio(nokia) suggests to focus discussion on 730 and then see how to proceed ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304733 | CR | Approval | 23.401 CR3730 (Rel-18, 'A'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-18 | Postponed | Alessio(nokia) suggests to focus discussion on 730 and then see how to proceed ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.9 | S2-2304734 | CR | Approval | 23.501 CR4390 (Rel-18, 'A'): Clarification on IAB Authorization | Huawei, HiSilicon | Rel-18 | Postponed | Alessio(nokia) suggests to focus discussion on 730 and then see how to proceed ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | Docs:=0 | - | |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=0 | - | |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=0 | - | |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=0 | - | |
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=0 | - | |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=0 | - | |
| 7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | Docs:=0 | - | |
| 7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | Docs:=0 | - | |
| 8 | - | - | - | Rel-17 WIDs | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=18 | - | |
| 8.1 | - | - | - | Issues on anonymization rules | - | - | Docs:=9 | - | |
| 8.1 | S2-2303933 | LS In | Action | LS from CT WG3: LS on Issues on anonymization rules | CT WG3 (C3-230522) | Rel-17 | Response drafted in S2-2304779. Final response in S2-2305876 | Replied to | |
| 8.1 | S2-2304779 | LS OUT | Approval | [DRAFT] Reply LS on Issues on anonymization rules | Huawei, HiSilicon | Rel-17 | Response to S2-2303933. r01 agreed. Revised to S2-2305876. | Zhang (Ericsson) provides comments Susan (Huawei) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2305876 | LS OUT | Approval | Reply LS on Issues on anonymization rules | SA WG2 | Rel-17 | Revision of S2-2304779r01. Approved | Approved | |
| 8.1 | S2-2304780 | CR | Approval | 23.288 CR0784 (Rel-17, 'F'): Clarification for anonymization rules | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2305877. | Zhang (Ericsson) provides r01 Susan (Huawei) is ok with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2305877 | CR | Approval | 23.288 CR0784R1 (Rel-17, 'F'): Clarification for anonymization rules | Huawei, HiSilicon | Rel-17 | Revision of S2-2304780r01. Approved | Agreed | |
| 8.1 | S2-2304781 | CR | Approval | 23.288 CR0785 (Rel-18, 'A'): Clarification for anonymization rules | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305878. | Susan (Huawei) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2305878 | CR | Approval | 23.288 CR0785R1 (Rel-18, 'A'): Clarification for anonymization rules | Huawei, HiSilicon | Rel-18 | Revision of S2-2304781r01. Approved | Agreed | |
| 8.1 | S2-2304891 | CR | Approval | 23.288 CR0791 (Rel-17, 'F'): Clarifications on the Validity period | Huawei, HiSilicon | Rel-17 | Approved | Agreed | |
| 8.1 | S2-2304892 | CR | Approval | 23.288 CR0792 (Rel-18, 'A'): Clarifications on the Validity period | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 8.1 | - | - | - | Correlating UE data collection and NWDAF request | - | - | Docs:=4 | - | |
| 8.1 | S2-2304618 | CR | Approval | 23.502 CR3783R1 (Rel-17, 'F'): NEF service used in correlating UE data collection and NWDAF request | Samsung | Rel-17 | Revision of S2-2300743 from S2#154AHE. Approved | Agreed | |
| 8.1 | S2-2304620 | CR | Approval | 23.288 CR0650R1 (Rel-17, 'F'): Correction for NEF service for correlating UE data collection and NWDAF request | Samsung | Rel-17 | Revision of S2-2300730 from S2#154AHE. Approved | Agreed | |
| 8.1 | S2-2304622 | CR | Approval | 23.502 CR3794R1 (Rel-18, 'A'): NEF service used in correlating UE data collection and NWDAF request | Samsung | Rel-18 | Revision of S2-2300825 from S2#154AHE. CR Cover sheet error! Approved | Agreed | |
| 8.1 | S2-2304623 | CR | Approval | 23.288 CR0660R1 (Rel-18, 'A'): Correction for NEF service for correlating UE data collection and NWDAF request | Samsung | Rel-18 | Revision of S2-2300833 from S2#154AHE. CR Cover sheet error! Approved | Agreed | |
| 8.1 | - | - | - | Analytics Subscription transfer procedures | - | - | Docs:=2 | - | |
| 8.1 | S2-2305145 | CR | Approval | 23.288 CR0814 (Rel-17, 'F'): Clarification on Analytics Subscription transfer procedures | ZTE | Rel-17 | Postponed | Zhang (Ericsson) provides comments Jinguo(ZTE) replies to Zhang (Ericsson) and provides r01 Wang Yuan (Huawei) asks for clarification. Yannick (Nokia): Nokia requests for clarification. Jinguo(ZTE) replies to .Wangyuan(Huawei) Wang Yuan (Huawei) replies to Jinguo(ZTE). Zhang (Ericsson) response to Jinguo (ZTE) Wang Yuan (Huawei) replies to Jinguo(ZTE) and is still not convinced. Jinguo(ZTE) replies to Wang Yuan(Huawei) Yannick (Nokia): Nokia provides comments. Jinguo(ZTE) provides r02. Zhang (Ericsson) response to Jinguo () Jinguo(ZTE) replies to Zhang and propose to remove the change in clause 6.1B.2.1 Jinguo(ZTE) provides r03 ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 and object all other versions Yannick (Nokia): Nokia requests to postpone, r03 is not acceptable. Jinguo(ZTE) propose to approve r03+ the following changes: In clause 6.1b.2.2 1) change The Target NWDAF may also include the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' to The Target NWDAF also includes the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' 2) In clause 7.2.5 change: - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the analytics consumer about the successful analytics subscription transfer (see clause 6.1B.2.2) to - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the source NWDAF about the successful analytics subscription transfer (see clause 6.1B.2.2) Yannick (Nokia): Nokia asks again to postpone to next meeting. Jinguo(ZTE): Yannick can you check with your stage 3 colleague at Friday? Jinguo(ZTE) suggest to approve r03+ the following changes: In clause 6.1b.2.2 1) change The Target NWDAF may also include the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' to The Target NWDAF also includes the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' 2) In clause 7.2.5 change: - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the analytics consumer about the successful analytics subscription transfer (see clause 6.1B.2.2) to - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the source NWDAF about the successful analytics subscription transfer (see clause 6.1B.2.2) 3)remove the change in clause 7.2.2 Jinguo(ZTE) suggest to approve r03+ the following changes: In clause 6.1b.2.2 1) change The Target NWDAF may also include the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' to The Target NWDAF also includes the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' 2) In clause 7.2.5 change: - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the analytics consumer about the successful analytics subscription transfer (see clause 6.1B.2.2) to - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the source NWDAF about the successful analytics subscription transfer (see clause 6.1B.2.2) 3)remove the change in clause 7.2.2 Jinguo(ZTE) suggest to approve r03+ the following changes: In clause 6.1b.2.2 1) change The Target NWDAF may also include the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' to The Target NWDAF also includes the list of analytics identitifer(s) which are successfully transferred to the Target NWDAF.' 2) In clause 7.2.5 change: - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the analytics consumer about the successful analytics subscription transfer (see clause 6.1B.2.2) to - a list of transferred Analytics ID(s): this parameter shall be present when Target NWDAF informs the source NWDAF about the successful analytics subscription transfer (see clause 6.1B.2.2) 3)remove the change in clause 7.2.2 ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2305146 | CR | Approval | 23.288 CR0815 (Rel-18, 'A'): Clarification on Analytics Subscription transfer procedures | ZTE | Rel-18 | Postponed | Jinguo(ZTE) provides r01 which is mirro of 5145r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.1 | - | - | - | NWDAF discovery with overlapping Serving Areas | - | - | Docs:=3 | - | |
| 8.1 | S2-2305219 | CR | Approval | 23.288 CR0668R2 (Rel-18, 'F'): NWDAF discovery with overlapping Serving Areas | Orange | Rel-18 | Revision of S2-2302378 from S2#155. r04 agreed. Revised to S2-2305879. | Yannick (Nokia): Nokia provides questions for clarification. Antoine (Orange) provides r01. Yannick (Nokia): Nokia provides suggestion for additional revision. Antoine (Orange) provides r02, adopting Yannick's suggestion. Zhang (Ericsson) provides comments Antoine (Orange) replies to Zhang. Wang Yuan (Huawei) provides comments. Antoine (Orange) replies to Wang Yuan and provides r03. Yannick (Nokia): Nokia comments on r02 and r03. Antoine (Orange) provides r04 removing the leftover text spotted by Yannick. Wang Yuan (Huawei) provides comments and still has concern. ==== Revisions Deadline ==== Antoine (Orange) replies to Wang Yuan. Wang Yuan (Huawei) can agree with r04 + adding additional clarification texts 'If the analytics is related to UE(s) and' at the beginning of the sentence. Antoine (Orange) can agree with r04 + adding 'If the analytics are related to UE(s) and' at the beginning of the added sentence, as proposed by Yuan. ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2305879 | CR | Approval | 23.288 CR0668R3 (Rel-18, 'F'): NWDAF discovery with overlapping Serving Areas | Orange | Rel-18 | Revision of S2-2305219r04. Approved | Agreed | |
| 8.1 | S2-2305220 | CR | Approval | 23.501 CR4037R2 (Rel-18, 'F'): NWDAF discovery with overlapping Serving Areas | Orange | Rel-18 | Revision of S2-2302379 from S2#155. Approved | Agreed | |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=12 | - | |
| 8.2 | - | - | - | The number of PVS IP addresses and/or PVS FQDNs for remote provisioning in onboarding network | - | - | Docs:=12 | - | |
| 8.2 | S2-2303931 | LS In | Action | LS from CT WG1: LS on the number of PVS IP addresses and/or PVS FQDNs for remote provisioning in onboarding network | CT WG1 (C1-231184) | Rel-17 | Responses drafted in S2-2304099, S2-2304336. Final response in S2-2305880 | Replied to | |
| 8.2 | S2-2304099 | LS OUT | Approval | [DRAFT] Reply to LS on the number of PVS IP addresses and/or PVS FQDNs for remote provisioning in onboarding network | Ericsson | Rel-17 | Response to S2-2303931. Merged into S2-2305880 | Qianghua (Huawei) comments that this LS can be marked as noted or merged into 4336 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2304336 | LS OUT | Approval | [DRAFT] Reply on number of PVS IP addresses and/or PVS FQDNs for remote provisioning in onboarding network | vivo | Response to S2-2303931. r01 agreed. Revised to S2-2305880, merging S2-2304099 | Peter Hedman (Ericsson) provides comments Xiaowen Sun (vivo) provides S2-2304336r01. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r01 ==== Comments Deadline ==== | Revised | |
| 8.2 | S2-2305880 | LS OUT | Approval | Reply to LS on the number of PVS IP addresses and/or PVS FQDNs for remote provisioning in onboarding network | SA WG2 | - | Revision of S2-2304336r01, merging S2-2304099. Approved | Approved | |
| 8.2 | S2-2304097 | CR | Approval | 23.501 CR4206 (Rel-18, 'A'): Maximum number of PVS addresses allowed to be provided to the UE | Ericsson | Rel-18 | Merged into S2-2305881 | Peter Hedman (Ericsson) proposes to note and mark as merged into 05022 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2304098 | CR | Approval | 23.501 CR4207 (Rel-17, 'F'): Maximum number of PVS addresses allowed to be provided to the UE | Ericsson | Rel-17 | Merged into S2-2305882 | Peter Hedman (Ericsson) proposes to note and mark as merged into 05023 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2304227 | CR | Agreement | 23.501 CR4247 (Rel-17, 'F'): Correction related to maximum PVS addresses and PVS FQDNs | Samsung | Rel-17 | Merged into S2-2305881 | Peter Hedman (Ericsson) proposes to note and mark as merged into 05022 Naman (Samsung) is OK to mark this as merged to 5022 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2304228 | CR | Agreement | 23.501 CR4248 (Rel-18, 'A'): Correction related to maximum PVS addresses and PVS FQDNs | Samsung | Rel-18 | Merged into S2-2305882 | Peter Hedman (Ericsson) proposes to note and mark as merged into 05023 Naman (Samsung) is OK to mark this as merged to 5023 as they are targeting the same issue ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2305022 | CR | Approval | 23.501 CR4460 (Rel-17, 'F'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | vivo | Rel-17 | r02 agreed. Revised to S2-2305881, merging S2-2304227 and S2-2304097 | Peter Hedman (Ericsson) provides r01 Rainer (Nokia) agrees to use 5022, 5023. Xiaowen Sun (vivo) propose to use this CR as way forward Qianghua (Huawei) provides r02 Xiaowen (vivo) are ok with r02 provided by Huawei ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r02 ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2305881 | CR | Approval | 23.501 CR4460R1 (Rel-17, 'F'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | Vivo, Ericsson, Huawei, Samsung | Rel-17 | Revision of S2-2305022r02, merging S2-2304227 and S2-2304097. Approved | Agreed | |
| 8.2 | S2-2305023 | CR | Approval | 23.501 CR4461 (Rel-18, 'A'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | vivo | Rel-18 | r01 agreed. Revised to S2-2305882, merging S2-2304228 and S2-2304098 | Xiaowen Sun (vivo) propose to use this CR as way forward Xiaowen Sun (vivo) provides r01 based on the discussion in 5022. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r01 ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2305882 | CR | Approval | 23.501 CR4461R1 (Rel-18, 'A'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | Vivo, Ericsson, Huawei, Samsung | Rel-18 | Revision of S2-2305023r01, merging S2-2304228 and S2-2304098. Approved | Agreed | |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=9 | - | |
| 8.3 | S2-2303984 | LS In | Action | LS from SA WG6: LS on AFId parameter value in EES invocation of Nnef_UEId_Get service | SA WG6 (S6-230945) | Rel-17 | Response drafted in S2-2305250. Final response in S2-2305883 | Replied to | |
| 8.3 | S2-2305250 | LS OUT | Approval | [DRAFT] Reply to LS on AFId parameter value in EES invocation of Nnef_UEId_Get service | China Mobile | Rel-17 | Response to S2-2303984. r02 agreed. Revised to S2-2305883. | Dario (Qualcomm) asks clarification and suggests to focus on the SA2 part of the LS. Laurent (Nokia): provides r01 Dan (China Mobile): provides r02 to simplify the reply based on Dario's suggestion. ==== Revisions Deadline ==== Dario (Qualcomm) is OK with r02. ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2305883 | LS OUT | Approval | Reply to LS on AFId parameter value in EES invocation of Nnef_UEId_Get service | SA WG2 | Rel-17 | Revision of S2-2305250r02. Approved | Approved | |
| 8.3 | S2-2304160 | CR | Approval | 23.501 CR4126R1 (Rel-17, 'F'): Clarifying AF influence on traffic routing vs EDI | Ericsson | Rel-17 | Revision of S2-2302339 from S2#155. Postponed | Dario (Qualcomm) asks question for clarification. Josep (Deutsche Telekom) also finds the CR quite cryptic. Shubhranshu (Nokia) comments Magnus (Ericsson) provides comments ==== Revisions Deadline ==== Dario (Qualcomm) replies to Magnus H. The CR needs to be improved before being agreed. Josep (Deutsche Telekom) agrees with Dario (Qualcomm). Proposes to postpone. Shubhranshu (Nokia) agrees to postpone Magnus H (Ericsson) comment to Dario ==== Comments Deadline ==== | Postponed |
| 8.3 | S2-2304161 | CR | Approval | 23.501 CR4127R1 (Rel-18, 'A'): Clarifying AF influence on traffic routing vs EDI | Ericsson | Rel-18 | Revision of S2-2302340 from S2#155. Postponed | Shubhranshu (Nokia) comments ==== Revisions Deadline ==== Shubhranshu (Nokia) proposes to postpone ==== Comments Deadline ==== | Postponed |
| 8.3 | S2-2305305 | CR | Approval | 23.502 CR4143 (Rel-17, 'D'): Fixing an Incorrect Reference in the Application guidance for URSP determination Section | InterDigital Inc. | Rel-17 | Check Affected Clauses! r01 agreed. Revised to S2-2305884. | Shubhranshu (Nokia) comments Mike (InterDigital) provides r01 to fix the clauses affected on the cover page ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2305884 | CR | Approval | 23.502 CR4143R1 (Rel-17, 'D'): Fixing an Incorrect Reference in the Application guidance for URSP determination Section | InterDigital Inc. | Rel-17 | Revision of S2-2305305r01. Approved | Agreed | |
| 8.3 | S2-2305306 | CR | Approval | 23.502 CR4144 (Rel-18, 'A'): Fixing an Incorrect Reference in the Application guidance for URSP determination Section | InterDigital Inc. | Rel-18 | Check Affected Clauses! r01 agreed. Revised to S2-2305885. | Shubhranshu (Nokia) comments Mike (InterDigital) provides r01 to fix the clauses affected on the cover page ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2305885 | CR | Approval | 23.502 CR4144R1 (Rel-18, 'A'): Fixing an Incorrect Reference in the Application guidance for URSP determination Section | InterDigital Inc. | Rel-18 | Revision of S2-2305306r01. Approved | Agreed | |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=6 | - | |
| 8.4 | S2-2304273 | CR | Approval | 23.501 CR4258 (Rel-17, 'F'): Number of PDU session slice availability check during EPC IWK | Samsung | Rel-17 | r01 agreed. Revised to S2-2305886. | Jinguo(ZTE) provides comment Ashok (Samsung) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2305886 | CR | Approval | 23.501 CR4258R1 (Rel-17, 'F'): Number of PDU session slice availability check during EPC IWK | Samsung | Rel-17 | Revision of S2-2304273r01. Approved | Agreed | |
| 8.4 | S2-2304276 | CR | Approval | 23.501 CR4259 (Rel-18, 'F'): Number of PDU session slice availability check during EPC IWK | Samsung | Rel-18 | r01 agreed. Revised to S2-2305887. | Peter Hedman (Ericsson) provides comments Jinguo(ZTE) provides comment Ashok (Samsung) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2305887 | CR | Approval | 23.501 CR4259R1 (Rel-18, 'A'): Number of PDU session slice availability check during EPC IWK | Samsung | Rel-18 | Revision of S2-2304276r01. Approved | Agreed | |
| 8.4 | S2-2304531 | CR | Approval | 23.503 CR0980 (Rel-17, 'F'): Correction on UE-Slice-MBR | Huawei, HiSilicon | Rel-17 | Approved | Agreed | |
| 8.4 | S2-2304532 | CR | Approval | 23.503 CR0981 (Rel-18, 'A'): Correction on UE-Slice-MBR | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=2 | - | |
| 8.5 | S2-2304841 | CR | Approval | 23.502 CR4076 (Rel-17, 'F'): Clarification of invocation of TSCTSF | Huawei, HiSilicon | Rel-17 | Noted | Shabnam (Ericsson) provides comments that we do not believe it is FASMO, objects to this CR Mirko (Huawei) responds. Devaki (Nokia) objects to the CR as we also believe it is not a FASMO. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2304842 | CR | Approval | 23.502 CR4077 (Rel-18, 'A'): Clarification of invocation of TSCTSF | Huawei, HiSilicon | Rel-18 | Noted | Devaki (Nokia) comments that the CR can be noted. It is NOT FASMO for Rel-17, not a correction, just a re-formulation of existing text. Can be ok for Rel-18 later. Mirko (Huawei) responds. Shabnam (Ericsson) objects to this CR as explained in the response to document 04841, we do not see the need to change also in Rel-18 Devaki (Nokia) objects to the CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=0 | - | |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=1 | - | |
| 8.7 | S2-2303943 | LS In | Information | LS from CT WG4: LS on Removal of the uavAuthenticated IE from Create SM Context Request | CT WG4 (C4-230790) | Noted | Guanglei (Huawei) proposes to note this LS, as it is CC to SA2. | Noted | |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=11 | - | |
| 8.8 | S2-2304128 | CR | Approval | 23.304 CR0234 (Rel-17, 'F'): Correction to the way that security function is described | Ericsson | Rel-17 | r01 agreed. Revised to S2-2305888. | Fei (OPPO) comments and provides r01. Judy (Ericsson) is fine with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2305888 | CR | Approval | 23.304 CR0234R1 (Rel-17, 'F'): Correction to the way that security function is described | Ericsson | Rel-17 | Revision of S2-2304128r01. Approved | Agreed | |
| 8.8 | S2-2304129 | CR | Approval | 23.304 CR0235 (Rel-18, 'A'): Correction to the way that security function is described | Ericsson | Rel-18 | r00 agreed. Revised to S2-2305889. | Fei (OPPO) provides r01. ==== Revisions Deadline ==== Judy (Ericsson) comments that revision of mirror CR should not be provided per e-meeting process (S2-2303912), see detail below ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2305889 | CR | Approval | 23.304 CR0235R1 (Rel-18, 'A'): Correction to the way that security function is described | Ericsson | Rel-18 | Revision of S2-2304129r00. Approved | Agreed | |
| 8.8 | S2-2305425 | LS In | Action | LS from CT WG1: Reply on Reply LS on mandating the NR Tx Profiles in broadcast mode and groupcast mode communication | CT WG1 (C1-231201) | Rel-17 | Noted | Fei (OPPO) proposed to note this incoming LS from CT1 if the CR S2-2304804 (or its revision) can be agreed. | Noted |
| 8.8 | S2-2304803 | CR | Approval | 23.304 CR0266 (Rel-18, 'A'): Catch all entry for direct discovery | vivo | Rel-18 | CR Cover sheet error! r01 agreed. Revised to S2-2305890. | Wen (vivo) provides revision r01 which just corrects the code to 5G_ProSe in the cover page. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2305890 | CR | Approval | 23.304 CR0266R1 (Rel-18, 'A'): Catch all entry for discovery | Vivo | Rel-18 | Revision of S2-2304803r01. Approved | Agreed | |
| 8.8 | S2-2304804 | CR | Approval | 23.304 CR0267 (Rel-17, 'F'): Catch all entry for direct discovery | vivo | Rel-17 | CR Cover sheet error! r01 agreed. Revised to S2-2305891. | Wen (vivo) provides revision r01 which just corrects the code to 5G_ProSe in the cover page. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2305891 | CR | Approval | 23.304 CR0267R1 (Rel-17, 'F'): Catch all entry for discovery | Vivo | Rel-17 | Revision of S2-2304804r01. Approved | Agreed | |
| 8.8 | S2-2305208 | CR | Approval | 23.303 CR0331 (Rel-17, 'F'): Correction of Open Discovery procedures in TS 23.303 | Philips International B.V. | Rel-17 | r01 agreed. Revised to S2-2305892. | Hannu (Nokia) comments that the WI code on the cover page is not appropriate for EPS ProSe change in TS 23.303 Zhang (Ericsson) provides comment Mehrdad (Mediatek Inc.) agrees with Nokia and Ericsson. Walter Dees (Philips) responds to comments. Fei (OPPO) comments. Hong (Qualcomm) comments. Walter (Philips) provides revision r01. Hannu (Nokia) comments on r01. Walter (Philips) responds to Hannu. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2305892 | CR | Approval | 23.303 CR0331R1 (Rel-17, 'F'): Correction of Open Discovery procedures | Philips International B.V. | Rel-17 | Revision of S2-2305208r01. Approved | Agreed | |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=55 | - | |
| 8.9 | - | - | - | Incoming LSs for information | - | - | Docs:=3 | - | |
| 8.9 | S2-2303935 | LS In | Information | Reply LS on 5MBS User Services | CT WG3 (C3-230819) | Rel-17 | Noted | LiMeng (Huawei) propose to mark this document as NOTED. | Noted |
| 8.9 | S2-2303957 | LS In | Action | LS from RAN WG3: Reply LS on shared NG-U Termination among gNBs | RAN WG3 (R3-230824) | Rel-17 | Noted | LiMeng (Huawei) propose to mark this document as NOTED. Judy (Ericsson) also proposes to note this LS as it has already been taken into account when SA approved the related CRs. | Noted |
| 8.9 | S2-2303973 | LS In | Information | Reply LS on security architecture for 5G multicast-broadcast services | SA WG4 (S4-230346) | Rel-17 | Noted | LiMeng (Huawei) propose to mark this document as NOTED. Judy (Ericsson) support LiMeng (Huawei)'s proposal to note this LS | Noted |
| 8.9 | - | - | - | Packet loss during multicast MBS delivery | - | - | Docs:=8 | - | |
| 8.9 | S2-2303985 | LS In | Action | LS from SA WG6: LS on addressing packet loss during multicast MBS delivery | SA WG6 (S6-231018) | Rel-17 | Responses drafted in S2-2304136, S2-2304316, S2-2305206, S2-2305271. Postponed | LiMeng (Huawei) comments. Judy (Ericsson) supports LiMeng (Huawei)'s proposal to use this thread for further discussion and comments. Zhendong (ZTE) provides comments. Thomas(Nokia) agrees to use this thread and provides comments. Miguel (Qualcomm) provides views on this topic from Qualcomm side. Miguel (Qualcomm) provides further comments Judy (Ericsson) comments Miguel (Qualcomm) comments Zhendong (ZTE) agree to postpone this LS and all related CRs to next meeting. Judy (Ericsson) agree to postpone this topic to allow more time to check different options | Postponed |
| 8.9 | S2-2304331 | DISCUSSION | Discussion | Discussion on packet loss during multicast MBS delivery | Huawei, HiSilicon | Rel-17 | Noted | Noted | |
| 8.9 | S2-2304136 | LS OUT | Approval | [DRAFT] Reply to LS on addressing packet loss during multicast MBS delivery | Ericssson | Rel-17 | Response to S2-2303985. Postponed | Judy (Ericsson) comments that the discussion is in 3985 thread Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2304316 | LS OUT | Approval | [DRAFT] Reply LS on addressing packet loss during multicast MBS delivery | Huawei, HiSilicon | Rel-17 | Response to S2-2303985. Postponed | Judy (Ericsson) comments that the discussion is in 3985 thread Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2305206 | LS OUT | Approval | [DRAFT] Reply LS on addressing packet loss during multicast MBS delivery | Qualcomm Austria RFFE GmbH | Rel-17 | Response to S2-2303985. Postponed | Judy (Ericsson) comments that the discussion is in 3985 thread Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2305271 | LS OUT | Approval | [DRAFT] Reply LS on addressing packet loss during multicast MBS delivery | Nokia, Nokia Shanghai-Bell | Response to S2-2303985. Postponed | Judy (Ericsson) comments that the discussion is in 3985 thread Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed | |
| 8.9 | S2-2304329 | CR | Approval | 23.247 CR0221 (Rel-17, 'F'): Multicast MBS session subscription and notification | Huawei, HiSilicon | Rel-17 | Postponed | Thomas (Nokia) comments that this CR depends on discussion in S2-2303985 thread. Provides r01 to have a version for Option 2 in that thread. Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2304330 | CR | Approval | 23.247 CR0222 (Rel-18, 'A'): Multicast MBS session subscription and notification | Huawei, HiSilicon | Rel-18 | Postponed | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304329. Miguel (Qualcomm) suggests we postpone this until next meeting ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | - | - | - | General corrections of TS 23.247 | - | - | Docs:=29 | - | |
| 8.9 | S2-2305294 | DISCUSSION | Discussion | Avoiding PDU session modifications to transfer MBS assistance information during Xn handover | Nokia, Nokia Shanghai-Bell | Rel-17 | Noted | Xiaoyan (CATT) provides comments. Fenqin (Huawei) provides comments. Thomas (Nokia) replies to Xiaoyan. Judy (Ericsson) comments Zhendong (ZTE) provides comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2304139 | CR | Approval | 23.247 CR0200 (Rel-17, 'F'): Correction to PCC procedures for location dependent MBS service | Ericsson | Rel-17 | Postponed | LiMeng (Huawei) considers if it is a must to have the Area Session policy ID. Judy (Ericsson) responds to LiMeng (Huawei) that the need to have the Area Session policy ID is explained in cover sheet. Thomas (Nokia) raises concerns and provides r01. Judy (Ericsson) responds to Thomas (Nokia) and comment to r01 Thomas (Nokia) raises concerns and provides r01. Replies to Judie´s comments Thomas (Nokia) replies to Judy Judy (Ericsson) comments Thomas (Nokia)replies to Judy Fenqin (Huawei) comments Thomas (Nokia) replies to Fenqin ==== Revisions Deadline ==== Judy (Ericsson) objects to r01 as it is not clear how it can work Zhendong (ZTE) proposes to postpone this CR to next meeting. Judy (Ericsson) agrees to postpone if companies need more time to check Fenqin (Huawei) responds to Judy Judy (Ericsson) asks Fenqin (Huawei) a question Fenqin (Huawei) responds to Judy again Thomas (Nokia) objects to r00 as it will not yield the same QoS for all sub sessions as required and suggest to postpone the issue Thomas(Nokia) support postponing, replies to Fenqin ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2304140 | CR | Approval | 23.247 CR0201 (Rel-18, 'A'): Correction to PCC procedures for location dependent MBS service | Ericsson | Rel-18 | Postponed | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304139. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2304143 | CR | Approval | 23.247 CR0204 (Rel-17, 'F'): Alignment with RAN on Xn/N2 based handover for inactive MBS session | Ericsson | Rel-17 | r03 agreed. Revised to S2-2305893. | LiMeng (Huawei) provides some comments. Judy (Ericsson) responds to LiMeng (Huawei). Zhendong (ZTE) provides comments. Haris(Qualcomm) comments Xiaoyan (CATT) provides comments. Fenqin(Huawei) provides comments. Judy (Ericsson) responds and provide r01. Thomas(Nokia) provides r02. Judy (Ericsson) thanks Thomas(Nokia) and is fine with r02 Haris(Qualcomm) provides r03 ==== Revisions Deadline ==== Judy (Ericsson) is fine with r03 Zhendong (ZTE) r03 is fine. Fenqin (Huawei) r03 is also fine to us. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305893 | CR | Approval | 23.247 CR0204R1 (Rel-17, 'F'): Alignment with RAN on Xn/N2 based handover for inactive MBS session | Ericsson | Rel-17 | Revision of S2-2304143r03. Approved | Agreed | |
| 8.9 | S2-2304144 | CR | Approval | 23.247 CR0205 (Rel-18, 'A'): Alignment with RAN on Xn/N2 based handover for inactive MBS session | Ericsson | Rel-18 | r00 agreed. Revised to S2-2305894. | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304143. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305894 | CR | Approval | 23.247 CR0205R1 (Rel-18, 'A'): Alignment with RAN on Xn/N2 based handover for inactive MBS session | Ericsson | Rel-18 | Revision of S2-2304144r00. Approved | Agreed | |
| 8.9 | S2-2304577 | CR | Approval | 23.247 CR0190R1 (Rel-17, 'F'): Connection resume with local multicast session | CATT | Rel-17 | Revision of S2-2302787 from S2#155. r04 agreed. Revised to S2-2305895. | LiMeng (Huawei) asks if the second and third bullet are necessary. Zhendong (ZTE) shares similar view with limeng. Judy (Ericsson) comments Thomas (Nokia) provides r01 Zhendong (ZTE) provides r02. Thomas (Nokia) provides r03 Xiaoyan (CATT) is fine with r03 Xiaoyan (CATT) provides r04 to fix editorials ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305895 | CR | Approval | 23.247 CR0190R2 (Rel-17, 'F'): Connection resume with local multicast session | CATT, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2304577r04. Approved | Agreed | |
| 8.9 | S2-2304578 | CR | Approval | 23.247 CR0224 (Rel-18, 'A'): Connection resume with local multicast session | CATT | Rel-18 | r00 agreed. Revised to S2-2305896. | Xiaoyan (CATT) provides r01 to align with 4577 LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304577. ==== Revisions Deadline ==== Thomas(Nokia) request to agree a mirror of S2-2304577 and not discuss any revisions ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305896 | CR | Approval | 23.247 CR0224R1 (Rel-18, 'A'): Connection resume with local multicast session | CATT, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304578r00. Approved | Agreed | |
| 8.9 | S2-2304579 | CR | Approval | 23.247 CR0191R1 (Rel-17, 'F'): Connection resume with location dependent multicast session | CATT | Rel-17 | Revision of S2-2302788 from S2#155. r02 agreed. Revised to S2-2305897. | LiMeng (Huawei): same as the comments to 4577, whether we need the 2nd and 3rd bullet? Judy (Ericsson) comments Thomas (Nokia) provides r02, asks to ignore r01 Xiaoyan (CATT) provides r03. Thomas (Nokia) prefers r02. ==== Revisions Deadline ==== Thomas (Nokia) objects to r03. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305897 | CR | Approval | 23.247 CR0191R2 (Rel-17, 'F'): Connection resume with location dependent multicast session | CATT, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2304579r02. Approved | Agreed | |
| 8.9 | S2-2304580 | CR | Approval | 23.247 CR0225 (Rel-18, 'A'): Connection resume with location dependent multicast session | CATT | Rel-18 | r00 agreed. Revised to S2-2305898. | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304579. Xiaoyan (CATT) provides r01 and r02, aligned with S2-2304579 r02 and r03 respectively. ==== Revisions Deadline ==== Thomas(Nokia) suggest to simply agree an exact mirror of the corresponding Rel-17 CR. No Need to discuss Rel-18 mirrors.. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305898 | CR | Approval | 23.247 CR0225R1 (Rel-18, 'A'): Connection resume with location dependent multicast session | CATT, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304580r00. Approved | Agreed | |
| 8.9 | S2-2304868 | CR | Approval | 23.247 CR0229 (Rel-17, 'F'): Clarification on the RRC resume failure for inactive MBS session | ZTE | Rel-17 | CC#4: r08 + changes agreed. Revised to S2-2305899. | LiMeng (Huawei) asks question for clarification. Judy (Ericsson) comments Zhendong (ZTE) provides response. Zhendong (ZTE) provides r01. Haris(Qualcomm) provides r01 Xiaoyan (CATT) provides comments. Haris(Qualcomm) provides r02 LiMeng (Huawei) provides some considerations. Judy (Ericsson) provides r03 Thomas (Nokia) provides r04 Zhendong (ZTE) provides r05. Judy (Ericsson) responds to Zhendong (ZTE) Zhendong (ZTE) provides r06. Fenqin (Huawei) provides r07. Haris(Qualcomm) asks question on r07 Haris(Qualcomm) indicates that Zhendong is correct and is ok with r07 Thomas(Nokia) provides r08. ==== Revisions Deadline ==== Judy (Ericsson) asks question whether 'MBS Session in active state' is the condition for UE to activate associated PDU Session and if yes, how UE knows Thomas suggests agreeing r08 + Change 'If the MBS session is in active state' to 'If the UE is participating in an MBS session' Zhendong (ZTE) is fine with thomas propsoal. Haris(Qualcomm) supports agreeing r08+ Change 'If the MBS session is in active state' to 'If the UE is participating in an MBS session' Zhendong (ZTE) upload the r09 to cc#3 folder. Zhendong (ZTE), r09 is r08 + Change 'If the MBS session is in active state' to 'If the UE is participating in an MBS session'. Thomas(Nokia) replies to Judy Judy (Ericsson) makes a proposal Fenqin (Huawei) makes a proposal Thomas (Nokia) makes a proposal Fenqin (Huawei) give a feedback to Thomas and suggest to discuss it at CC#4. Thomas (Nokia) proposes R08 + Replace' 'If the UE context retrieval fails, the UE is moved into RRC IDLE state as per TS 38.300 [9]. The UE initiates the NAS signalling recovery (see TS 24.501 [x]). If the MBS session is in Active state, the UE requests to re-activate the associated PDU session(s) during registration procedure (see clause 4.2.2.2.2 of TS 23.502 [6]) and service request procedure (see clause 4.2.3.2 of TS 23.502 [6]) and clause 7.2.8 applies.' With ''The UE initiates the NAS signalling recovery including activating PDU Session(s) (see TS 24.501 [x]). The UE also requests to activate the associated PDU session(s) during registration procedure (see clause 4.2.2.2.2 of TS 23.502 [6]) and service request procedure (see clause 4.2.3.2 of TS 23.502 [6]) and clause 7.2.8 applies.' ==== Comments Deadline ==== Zhendong (ZTE) propsoes that, r08 + replace 'The UE initiates the NAS signalling recovery (see TS 24.501 [x]). If the MBS session is in Active state, the UE requests to re-activate the associated PDU session(s) during registration procedure (see clause 4.2.2.2.2 of TS 23.502 [6]) and service request procedure (see clause 4.2.3.2 of TS 23.502 [6]) and clause 7.2.8 applies.' with 'The UE initiates the NAS signalling recovery including activating PDU Session(s) (see TS 24.501 [x]). The UE also requests to activate the associated PDU session(s) during registration procedure (see clause 4.2.2.2.2 of TS 23.502 [6]) and service request procedure (see clause 4.2.3.2 of TS 23.502 [6]) and clause 7.2.8 applies.' | Revised |
| 8.9 | S2-2305899 | CR | Approval | 23.247 CR0229R1 (Rel-17, 'F'): Clarification on the RRC resume failure for inactive MBS session | ZTE, Nokia, Nokia Shanghai-Bell, Ericsson | Rel-17 | Revision of S2-2304868r08 + changes. CC#4: Approved | Agreed | |
| 8.9 | S2-2304869 | CR | Approval | 23.247 CR0230 (Rel-18, 'A'): Clarification on the RRC resume failure for inactive MBS session | ZTE | Rel-18 | r00 agreed. CC#4: r09 + changes agreed. Revised to S2-2305900. | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304868. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305900 | CR | Approval | 23.247 CR0230R1 (Rel-18, 'A'): Clarification on the RRC resume failure for inactive MBS session | ZTE, Nokia, Nokia Shanghai-Bell, Ericsson | Rel-18 | Revision of S2-2304869r09 + changes. CC#4: Approved | Agreed | |
| 8.9 | S2-2304954 | CR | Approval | 23.247 CR0238 (Rel-17, 'F'): Handover Procedure correction | Huawei, HiSilicon | Rel-17 | CC#4: r05 + changes agreed. Revised to S2-2306259. For CC#4. Offline ongoing | Judy (Ericsson) provides r01 Thomas (Nokia) provides r02, comments, objects against r00 and r01 Fenqin (Huawei) provides comments, objects against r02 Thomas (Nokia) replies to Fenqin. Suggest to check parallel discussions in RAN3 Fenqin (Huawei) replies to Thomas and provides r03. Thomas(Nokia) provides r04. Fenqin(Huawei) provides response to Thomas. Judy (Ericsson) comments Fenqin (Huawei) give feedback to Judy Thomas(Nokia) replies to Fenqin(Huawei). Fenqin (Huawei) provides r05. Thomas(Nokia) is fine with r05. ==== Revisions Deadline ==== Judy (Ericsson) cannot accept r05 as is and request a change explained below. Fenqin (Huawei) ask a question to Judy Judy (Ericsson) responds to Fenqin (Huawei) Fenqin (Huawei) give a response to Judy Judy (Ericsson) request a change to r05, replacing 'NG-RAN provides the response to PDU session modification when the 5GC Individual MBS traffic delivery is no longer required' with 'NG-RAN responds to PDU session modification request when the shared tunnel for shared delivery is available'. Thomas (Nokia) accepts r05 but objects changes requested by Judy. Judy (Ericsson) accepts r01/r03, cannot accept r05 as is (requesting to remove 'NG-RAN provides the response to PDU session modification when the 5GC Individual MBS traffic delivery is no longer required'), objects to other revisions. Fenqin (Huawei) Propose the change like: R05+ Replace 'when the 5GC Individual MBS traffic delivery is no longer required'--->' when the shared delivery of the MBS session data to the related UE is ready' Thomas (Nokia) can accept: R05+ Replace 'when the 5GC Individual MBS traffic delivery is no longer required'--->' when the shared delivery of the MBS session data to the related UE is established' Thomas(Nokia) objects against r00, r01, and r03. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2306259 | CR | Approval | 23.247 CR0238R1 (Rel-17, 'F'): Handover Procedure correction | Huawei, HiSilicon | Rel-17 | Revision of S2-2304954r05 + changes. CC#4: Approved | Agreed | |
| 8.9 | S2-2304955 | CR | Approval | 23.247 CR0239 (Rel-18, 'A'): Handover Procedure correction | Huawei, HiSilicon | Rel-18 | CC#4: Mirror CR. Revised to S2-2306260. For CC#4 | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2304954. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2306260 | CR | Approval | 23.247 CR0239R1 (Rel-18, 'A'): Handover Procedure correction | Huawei, HiSilicon | Rel-18 | Revision of S2-2304955. CC#4: Approved | Agreed | |
| 8.9 | S2-2305252 | CR | Approval | 23.247 CR0245 (Rel-17, 'F'): Corrections for unicast tunnel establishment for MBS broadcast | Nokia, Nokia Shanghai-bell | Rel-17 | r10 agreed. Revised to S2-2305901. | Judy (Ericsson) provides r01 LiMeng (Huawei) is fine with r01. Thomas (Nokia) provides r02 Thomas (Nokia) objects against r01. Judy (Ericsson) responds to Thomas (Nokia), and objects to r00, r02. Thomas (Nokia) responds to Judy and provides r03. Thomas (Nokia) provides r04. LiMeng (Huawei) is in general fine with r04 with some minor comments. Thomas (Nokia) provides r05 and replies to Limeng. Judy (Ericsson) provides r06 Thomas (Nokia) objects against r06 Thomas (Nokia) provides r07. Judy (Ericsson) provides r08 based on r06, propose not to expand CR scope as in r07 by adding changes from paper marked as 'unhandled' Thomas(Nokia) provides r09, object against r08 Judy (Ericsson) comments on r09 and provides r10 Thomas(Nokia) accepts r10 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305901 | CR | Approval | 23.247 CR0245R1 (Rel-17, 'F'): Corrections for unicast tunnel establishment for MBS broadcast | Nokia, Nokia Shanghai-Bell, Ericsson | Rel-17 | Revision of S2-2305252r10. Approved | Agreed | |
| 8.9 | S2-2305254 | CR | Approval | 23.247 CR0246 (Rel-18, 'A'): Corrections for unicast tunnel establishment for MBS broadcast | Nokia, Nokia Shanghai-bell | Rel-18 | r00 agreed. Revised to S2-2305902. | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2305252. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2305902 | CR | Approval | 23.247 CR0246R1 (Rel-18, 'A'): Corrections for unicast tunnel establishment for MBS broadcast | Nokia, Nokia Shanghai-Bell, Ericsson | Rel-18 | Revision of S2-2305254r00. Approved | Agreed | |
| 8.9 | S2-2305260 | CR | Approval | 23.247 CR0184R1 (Rel-17, 'F'): Corrections for MBS multicast session release | Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2302358 from S2#155. Postponed | Judy (Ericsson) provides r01 Thomas (Nokia) is fine with r01 Haris(Qualcomm) asks question for clarification Thomas(Nokia) replies to Harris Haris(Qualcomm) responds and indicates to keep the text as is Fenqin (Huawei) comments. Thomas (Nokia) provides r02 Fenqin (Huawei) suggest to postpone this paper Thomas(Nokia) asks Fenqin if he checked r02 Fenqin (Huawei) provide r03 Thomas (Nokia) provide r04 ==== Revisions Deadline ==== Fenqin (Huawei) is ok with r04 Judy (Ericsson) comments Fenqin (Huawei) response to Judy Thomas (Nokia) replies to Judy Haris(Qualcomm) proposes to postpone ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2305261 | CR | Approval | 23.247 CR0185R1 (Rel-18, 'A'): Corrections for MBS multicast session release | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2302360 from S2#155. Postponed | LiMeng (Huawei) comments that the outcome of this document should be aligned with S2-2305260. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | - | - | - | Documents exceeding TU budget | - | - | Docs:=15 | - | |
| 8.9 | S2-2304137 | CR | Approval | 23.247 CR0198 (Rel-17, 'F'): Suppressing MB-SMF/MB-UPF triggered MBS Session activation/deactivation | Ericsson | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2304138 | CR | Approval | 23.247 CR0199 (Rel-18, 'A'): Suppressing MB-SMF/MB-UPF triggered MBS Session activation/deactivation | Ericsson | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2304141 | CR | Approval | 23.247 CR0202 (Rel-17, 'F'): Inconsistency between text description and figure steps in broadcast procedures | Ericsson | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2304142 | CR | Approval | 23.247 CR0203 (Rel-18, 'A'): Inconsistency between text description and figure steps in broadcast procedures | Ericsson | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2305226 | CR | Approval | 23.247 CR0241 (Rel-17, 'F'): Connection Resume procedure for location-dependent MBS multicast service | Nokia, Nokia Shanghai-Bell | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2305228 | CR | Approval | 23.247 CR0242 (Rel-18, 'A'): Connection Resume procedure for location-dependent MBS multicast service | Nokia, Nokia Shanghai-Bell | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2305235 | CR | Approval | 23.247 CR0243 (Rel-17, 'F'): Connection Resume procedure for local MBS multicast service | Nokia, Nokia Shanghai-Bell | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2305249 | CR | Approval | 23.247 CR0244 (Rel-18, 'A'): Connection Resume procedure for local MBS multicast service | Nokia, Nokia Shanghai-Bell | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2305299 | CR | Approval | 23.247 CR0249 (Rel-17, 'F'): Avoiding PDU session modifications to transfer MBS assistance information during Xn handover | Nokia, Nokia Shanghai-Bell | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2305304 | CR | Approval | 23.247 CR0250 (Rel-18, 'A'): Avoiding PDU session modifications to transfer MBS assistance information during Xn handover | Nokia, Nokia Shanghai-Bell | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2305263 | CR | Approval | 23.247 CR0247 (Rel-17, 'F'): Avoiding packet loss during multicast MBS delivery due to deactivated MBS sessions | Nokia, Nokia Shanghai-Bell | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2305265 | CR | Approval | 23.247 CR0248 (Rel-18, 'A'): Avoiding packet loss during multicast MBS delivery due to deactivated MBS sessions | Nokia, Nokia Shanghai-Bell | Rel-18 | NOT HANDLED | ||
| 8.9 | S2-2305384 | CR | Approval | 23.247 CR0261 (Rel-17, 'F'): Corrections related to indicating failure of establishing MBS broadcast transmission resources | Nokia, Nokia Shanghai-Bell | Rel-17 | NOT HANDLED | ||
| 8.9 | S2-2305386 | CR | Approval | 23.247 CR0262 (Rel-18, 'A'): Corrections related to indicating failure of establishing MBS broadcast transmission resources | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! Revised to S2-2305387 | Revised | |
| 8.9 | S2-2305387 | CR | Approval | 23.247 CR0262R1 (Rel-18, 'A'): Corrections related to indicating failure of establishing MBS broadcast transmission resources | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305386 | NOT HANDLED | |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=0 | - | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=0 | - | |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=0 | - | |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=2 | - | |
| 8.14 | S2-2303940 | LS In | Information | LS from CT WG4: LS on GNSS integrity requirement parameters definition | CT WG4 (C4-230655) | Rel-17 | Noted | Noted | |
| 8.14 | S2-2304936 | CR | Approval | 23.271 CR0437 (Rel-17, 'F'): Corrections on EPC-NI-LR procedure for location verification of UE via NR satellite access | INSPUR | Rel-17 | CR Cover sheet error! Noted | Stephen (Qualcomm) provides comments ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note this CR ==== Comments Deadline ==== | Noted |
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=0 | - | |
| 8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | Docs:=0 | - | |
| 8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | Docs:=0 | - | |
| 8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | Docs:=0 | - | |
| 8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | Docs:=0 | - | |
| 8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | Docs:=0 | - | |
| 8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | Docs:=3 | - | |
| 8.21 | S2-2304020 | CR | Approval | 23.502 CR3949 (Rel-17, 'F'): Correction to procedures for AF-triggered dynamically changing AM policies | Ericsson | Rel-17 | Approved | Agreed | |
| 8.21 | S2-2304021 | CR | Approval | 23.502 CR3950 (Rel-18, 'A'): Correction to procedures for AF-triggered dynamically changing AM policies | Ericsson | Rel-18 | CR Cover sheet error! Revised to S2-2305236 | Revised | |
| 8.21 | S2-2305236 | CR | Approval | 23.502 CR3950R1 (Rel-18, 'A'): Correction to procedures for AF-triggered dynamically changing AM policies | Ericsson | Rel-18 | Revision of S2-2304021. Approved | 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:=0 | - | |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=0 | - | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=0 | - | |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=11 | - | |
| 8.27 | S2-2303960 | LS In | Action | LS from RAN WG3: LS on UE capability signalling for IoT-NTN | RAN WG3 (R3-230951) | Rel-17 | Noted | Noted | |
| 8.27 | S2-2304203 | CR | Approval | 23.502 CR3677R2 (Rel-17, 'F'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) | Qualcomm Incorporated | Rel-17 | Revision of S2-2302935 from S2#155. r03 agreed. Revised to S2-2305903. | Hannu (Nokia) provides r01 Steve (Huawei) comments. Haris(Qualcomm) responds Haris(Qualcomm) provides r02 Chris (Vodafone) provides r03 ==== Revisions Deadline ==== Haris(Qualcomm) is ok with r03 Chris (Vodafone) provides information and suggests using r03. Hannu (Nokia) can agree r03 ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2305903 | CR | Approval | 23.502 CR3677R3 (Rel-17, 'F'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) | Qualcomm Incorporated | Rel-17 | Revision of S2-2304203r03. Approved | Agreed | |
| 8.27 | S2-2304204 | CR | Approval | 23.502 CR3678R2 (Rel-18, 'A'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) | Qualcomm Incorporated | Rel-18 | Revision of S2-2302937 from S2#155. CR Cover sheet error! r00 agreed. Revised to S2-2305904. | Revised | |
| 8.27 | S2-2305904 | CR | Approval | 23.502 CR3678R3 (Rel-18, 'A'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) | Qualcomm Incorporated | Rel-18 | Revision of S2-2304204r00. Approved | Agreed | |
| 8.27 | S2-2304292 | CR | Approval | 23.401 CR3722R1 (Rel-17, 'F'): Removal of EN on handling of extended NAS timers | MediaTek Inc. | Rel-17 | Revision of S2-2302441 from S2#155. Approved | Agreed | |
| 8.27 | S2-2304293 | CR | Approval | 23.401 CR3723R1 (Rel-18, 'A'): Removal of EN on handling of extended NAS timers | MediaTek Inc. | Rel-18 | Revision of S2-2302442 from S2#155. Approved | Agreed | |
| 8.27 | S2-2304294 | CR | Approval | 23.401 CR3726 (Rel-17, 'F'): Correction to UE AS deactivation | MediaTek Inc., Deutsche Telekom | Rel-17 | r02 agreed. Revised to S2-2305905. | Haris(Qualcomm) provides r01 Guillaume (MediaTek Inc.): ok with Haris (Qualcomm) suggestion Hannu (Nokia) asks question from Haris on r01 Guillaume (MediaTek Inc.) replies to Hannu (Nokia) Hannu (Nokia) thanks Guillaume for the explanation and supports r01 from Haris. Guillaume (MediaTek Inc.) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2305905 | CR | Approval | 23.401 CR3726R1 (Rel-17, 'F'): Correction to UE AS deactivation | MediaTek Inc., Deutsche Telekom | Rel-17 | Revision of S2-2304294r02. Approved | Agreed | |
| 8.27 | S2-2304295 | CR | Approval | 23.401 CR3727 (Rel-18, 'A'): Correction to UE AS deactivation | MediaTek Inc., Deutsche Telekom | Rel-18 | r01 agreed. Revised to S2-2305906. | Guillaume (MediaTek Inc.) provides r01 (aligning with 4294 r02) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2305906 | CR | Approval | 23.401 CR3727R1 (Rel-18, 'A'): Correction to UE AS deactivation | MediaTek Inc., Deutsche Telekom | Rel-18 | Revision of S2-2304295r01. Approved | Agreed | |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=20 | - | |
| 8.28 | - | - | - | Use of PEI during an emergency PDU session | - | - | Docs:=8 | - | |
| 8.28 | S2-2303953 | LS In | Action | LS from RAN WG2: LS on the use of PEI during an emergency PDU session | RAN WG2 (R2-2302302) | Rel-17 | Responses drafted in S2-2304192, S2-2304278, S2-2304340, S2-2305229. Postponed | Hannu (Nokia) asks whether there has been any discussion on which one of the draft LS out to take as a template? Steve (Huawei) correcting the email subject to AI to 8.28. Chris (Vodafone) suggests using the thread of the CR in 4190 Chris (Vodafone) suggests to use a revision of 4192 to answer this LS Chris (Vodafone) provides a r1 of 4192 to answer this LS and will now move to 4192 thread Qian (Ericsson) proposes to postpone the LS based on the comment given at 4192 thread Qian (Ericsson) proposes to postpone the LS based on the comment given at 4190 thread (wrong reference tdoc in previous comment) | Postponed |
| 8.28 | S2-2304192 | LS OUT | Approval | [DRAFT] Reply LS on the use of PEI during an emergency PDU session | Ericsson Inc. | Rel-17 | Response to S2-2303953. Postponed | Qian (Ericsson) indicates that this will be handled together with 4190 and 3953 Chris (Vodafone) provides a r1 of 4192. The other draft o/g LSs can be merged to this one? Miguel (Qualcomm) provides r02 ==== Revisions Deadline ==== Qian (Ericsson) propose to postpone the paper as commented in 4190 thread Chris (Vodafone) does not want to postpone - we should at least warn CT1 about R17 change for them, and inform RAN 3. ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304278 | LS OUT | Approval | [DRAFT] Reply LS on the use of PEI during an emergency PDU session | OPPO | Rel-18 | Response to S2-2303953. Merged into S2-2304192 (Postponed) | Qian (Ericsson) indicates that this will be handled together with 4192 and other LS outs Chris (Vodafone) proposes to merge this into a revision of 4192. Peng (OPPO) is ok to merge this into a revision of 4192 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304340 | LS OUT | Approval | [DRAFT] LS reply on the use of PEI during an emergency PDU session | Huawei, HiSilicon | Rel-17 | Response to S2-2303953. Merged into S2-2304192 (Postponed) | Qian (Ericsson) indicates that this will be handled together with 4192 and other LS outs Chris (Vodafone) proposes to merge this into a revision of 4192. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2305229 | LS OUT | Approval | [DRAFT] Reply LS on the use of PEI during an emergency PDU session | Qualcomm Austria RFFE GmbH | Rel-17 | Response to S2-2303953. Merged into S2-2304192 (Postponed) | Qian (Ericsson) indicates that this will be handled together with 4192 and other LS outs Chris (Vodafone) proposes to merge this into a revision of 4192. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304190 | CR | Approval | 23.501 CR4232 (Rel-17, 'F'): Paging Early Indication with emergency | Ericsson, T-Mobile USA, AT&T, Deutsche Telekom | Rel-17 | Postponed | Chris (Vodafone) objects to rev 0 as it is likely to cause emergency call backs to fail, and it does not address high latency in call back. Chris (Vodafone) provides rev1. This adopts a failsafe approach; explains how to avoid the 50ms delay; and provides a solution for rel 15 issue of multiple seconds of delay. Qian (Ericsson) asks questions related to r01. Guillaume (MediaTek Inc.) provides r02 Chris (Vodafone) supports r02 and answers Ericsson's questions Chris (Vodafone) provides r03 based on his answers to Ericsson Miguel (Qualcomm) has concerns with all revisions so far Chris (Vodafone) replies to Qualcomm. Miguel (Qualcomm provides r04 and responds to Chris Chris (Vodafone) is OK with r04 provided CT1 align their stage 3. Peng (OPPO) is ok with r04, and be ok as co-signer Guillaume (MediaTek Inc.): ok with r04 Qian (Ericsson) provides comments ==== Revisions Deadline ==== Miguel (Qualcomm) provides clarification to Qian Qian (Ericsson) provides comments and propose the POSTPONE the paper Chris (Vodafone) does not want to postpone this topic as we need CT1 to CHANGE their R17 specification Michele (Huawei) objects to r04 as we believe there should be an explicit indication from the CN to RAN to disable PEI when the UE has an active PDU session in order for comply with current requirements. Chris (Vodafone) asks Huawei to provide the requirements that they mention. Qian (Ericsson) provides comments. Chris (Vodafone) replies. Qian (Ericsson) replies. ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304191 | CR | Approval | 23.501 CR4233 (Rel-18, 'A'): Paging Early Indication with emergency | Ericsson, T-Mobile USA, AT&T, Deutsche Telekom | Rel-18 | Postponed | Chris (Vodafone) says this is a mirror CR. Can align once release 17 CR is stable. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304282 | CR | Approval | 23.501 CR4260 (Rel-18, 'A'): The use of PEIPS during emergency PDU session | OPPO | Rel-18 | CR Cover sheet error! Merged into S2-2304190 (Postponed) | Qian (Ericsson) indicates that the handling on this paper shall be discussed together with 4190 and 3953 Chris (Vodafone) proposes to merge this into a revision of 4190. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | - | - | - | Different AF specific UE Identifier for different AFs | - | - | Docs:=12 | - | |
| 8.28 | S2-2303921 | LS In | Action | LS from SA WG3: LS on enforcement of AF specific identifier | SA WG3 (S3-230462) | Rel-18 | Revision of postponed S2-2302201 from S2#155. Response drafted in S2-2304403. Postponed | Postponed | |
| 8.28 | S2-2304403 | LS OUT | Approval | [DRAFT] Reply LS on enforcement of AF specific identifier | China Mobile | Rel-18 | Revision of S2-2303271 from S2#155. Response to S2-2303921. Postponed | Laurent (Nokia): Comments: need to fine tune the LS with proper CR number once agreement on CR has been reached ==== Revisions Deadline ==== Laurent (Nokia): once the CR is agreed this LS needs to be updated with reference to 23.501 CR4243 Sudeep (Apple) proposes to mark this LS as POSTPONED since we don't seem to have an agreeable version of CR. ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2304214 | DISCUSSION | Discussion | On uniqueness and policing of AF specific UE ID usage | Qualcomm Incorporated | Rel-17 | Noted | Dario (Qualcomm) triggers discussion on this topic, asks for companies' views and points out that 4219 could be taken as baseline for discussion. Laurent (Nokia): Comments: Suggests we decide which option to take on this thread, then fine tune CR wording in a second step. too late for option 1 and its complexity is not needed, option 2 is good enough. Sudeep (Apple) comments on option 2. Magnus H (Ericsson) support Apple and Nokia. We think option 2 is good enough. Dan (China Mobile) comment. Magnus H (Ericsson) proposes to go with 4542 ==== Revisions Deadline ==== Xinpeng(Huawei) proposes to note this discussion paper. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304544 | DISCUSSION | Agreement | Enforcing restrictions on AF specific UE Identifier | Apple | Noted | Dario (Qualcomm) points to 4214 for common discussion. Laurent (Nokia): suggests that we discuss the overall solution as part of 4214 (4214 option 2 is IMHO the way to go) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 8.28 | S2-2304215 | CR | Approval | 23.501 CR4241 (Rel-17, 'F'): Authorization of usage of AF specific UE ID - Option 1 | Qualcomm Incorporated | Rel-17 | Noted | Laurent (Nokia): Objects to any version of this Tdoc to have a single thread to discuss actual CR text = that of 4219 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304216 | CR | Approval | 23.501 CR4242 (Rel-18, 'A'): Authorization of usage of AF specific UE ID - Option 1 | Qualcomm Incorporated | Rel-18 | Noted | Sudeep (Apple) objects to the original version. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304217 | CR | Approval | 23.502 CR3977 (Rel-17, 'F'): Authorization of usage of AF specific UE ID - Option 1 | Qualcomm Incorporated | Rel-17 | Noted | Sudeep (Apple) objects to the original version. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304218 | CR | Approval | 23.502 CR3978 (Rel-18, 'A'): Authorization of usage of AF specific UE ID - Option 1 | Qualcomm Incorporated | Rel-18 | Noted | Sudeep (Apple) objects to the original version. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304219 | CR | Approval | 23.501 CR4243 (Rel-17, 'F'): Authorization of usage of AF specific UE ID - Option 2 | Qualcomm Incorporated | Rel-17 | Noted | Laurent (Nokia): provides r01 Xinpeng(Huawei) comments. Laurent (Nokia): Comments Xinpeng(Huawei) replies to Laurent (Nokia). Sudeep (Apple) replies to Xinpeng (Huawei) and Laurent (Nokia). Dario (Qualcomm) replies and provides r02 and r03. Sudeep (Apple) provides r04. Xinpeng(Huawei) is fine with r04, and provides r05 for a way forward. ==== Revisions Deadline ==== Sudeep (Apple) can accept only r04. Can live with R05, if it can indicate that seeding NFs with mapping information is one example of enforcement. Objects to r00 and all other revisions. Dario (Qualcomm) replies to Sudeep and objects to r04 and r05. Can accept r0, r03 and r05 if NOTE 3 changes as follows: A) delete first sentence; B) Delete words 'range' (twice) and 'or'; C) Replace word 'identifier' with 'identifiers' (twice). Sudeep (Apple) responds to Dario. Dario (Qualcomm) replies to Sudeep. Xinpeng(Huawei) replies to Dario (Qualcomm). Xinpeng(Huawei) can only accept r04 and r05, objects to any other version. Dan(China Mobile) think if we have to agree one version, r04 is prefer. Laurent (Nokia): objects to R00 and R04 Magnus H (Ericsson) can only accept r04 and objects to all other revisions ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304220 | CR | Approval | 23.501 CR4244 (Rel-18, 'A'): Authorization of usage of AF specific UE ID - Option 2 | Qualcomm Incorporated | Rel-18 | Noted | Dario (Qualcomm) provides r01 and r02. Sudeep (Apple) provides r03 corresponding to 4219r04. Xinpeng(Huawei) is fine with r03, and provides r04 for a way forward. ==== Revisions Deadline ==== Sudeep (Apple) can accept only r03. Can live with r04 if it can indicate that seeding NFs with mapping information is one example of enforcement. Objects to r00 and all other revisions. Xinpeng(Huawei) accepts r03 and r04, objects to any other version. Magnus (Ericsson) can only accept r03. Objects to all other revisions Dario (Qualcomm) replies to Sudeep and objects to r03 and r04. Can accept r0, r02 and r04 if NOTE 3 changes as follows: A) delete first sentence; B) Delete words 'range' (twice) and 'or'; C) Replace word 'identifier' with 'identifiers' (twice). ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2304542 | CR | Approval | 23.501 CR4155R2 (Rel-18, 'F'): Rewording of NOTE on AF Specific UE identifier | Apple | Rel-18 | Revision of S2-2303270 from S2#155. Merged into S2-2304219 (noted) | Laurent (Nokia): suggests that we discuss the overall solution as part of 4214 (4214 option 2 is IMHO the way to go) Dario (Qualcomm) supports Laurent's proposal. Laurent (Nokia): Objects to any version of this Tdoc to have a single thread to discuss actual CR text = that of 4219 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2305225 | CR | Approval | 23.501 CR4171R1 (Rel-18, 'F'): Clarify the NOTE2 in 5.20 | China moible | Rel-18 | Revision of S2-2303013 from S2#155. Merged into S2-2304219 (noted) | Dario (Qualcomm) points to 4214 for common discussion. Laurent (Nokia): suggests that we discuss the overall solution as part of 4214 (4214 option 2 is IMHO the way to go) Dario (Qualcomm) supports Laurent's proposal. Laurent (Nokia): Objects to any version of this Tdoc to have a single thread to discuss actual CR text = that of 4219 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9 | - | - | - | Rel-18 SIDs | - | - | Docs:=0 | - | |
| 9.1.1 | - | - | - | Study on 5G System with Satellite Backhaul (FS_5GSATB) | - | - | Docs:=0 | - | |
| 9.1.2 | - | - | - | 5G System with Satellite Backhaul (5GSATB) | - | - | Docs:=24 | - | |
| 9.1.2 | - | - | - | Dynamic satellite backhaul | - | - | Docs:=20 | - | |
| 9.1.2 | S2-2305087 | CR | Approval | 23.501 CR4478 (Rel-18, 'B'): Remove ENs for QoS monitoring on dynamic satellite backhaul | CATT, Samsung, NOKIA | Rel-18 | r01 agreed. Revised to S2-2305907. | Yuxin(Xiaomi) comments ==== Revisions Deadline ==== Hucheng (CATT) points out that r01 was provided by Xiaomi. DongYeon (Samsung) is OK with r01. Yuxin (Xiaomi) is OK with r01. Hannu (Nokia) supports r01. ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305907 | CR | Approval | 23.501 CR4478R1 (Rel-18, 'B'): Remove ENs for QoS monitoring on dynamic satellite backhaul | CATT, Samsung, NOKIA | Rel-18 | Revision of S2-2305087r01. Approved | Agreed | |
| 9.1.2 | S2-2304223 | CR | Approval | 23.501 CR4246 (Rel-18, 'B'): Optimization consideration for satellite backhaul QoS monitoring | China Mobile | Rel-18 | r04 agreed. Revised to S2-2305908. | Haris(Qualcomm) comments Hannu (Nokia) is concerned that this proposal might not be aligned with the conclusions Tianji (CMCC) reply to Harris(Qualcomm) Tianji (CMCC) reply to Hannu (Nokia) 's concern: that this proposal might not be aligned with the conclusions Tianji (CMCC) provides r01 Stefan (Ericsson) expresses concerns Haris(Qualcomm) comments on r01 Tianji (CMCC) provides reply to comments on r01 Tianji (CMCC) provides r02 Tianji (CMCC) replies to (Ericsson) concerns Heng (China Telecom) comments on the coverpage of revision Yuxin (Xiaomi) comments on r02 Tianji (CMCC) replies to (Xiaomi) comments: Tianji (CMCC) replies to (China Telecom) comments Hucheng (CATT) comments and proposes a way forward. Yuxin (Xiaomi) replies to Tianji Tianji (CMCC) replies to (Xiaomi, CATT)'s suggestion on way-forward proposal, and provides the revision #03: Haris(Qualcomm) comments that none of the revisions are inline with the assumptions that apply since rel.17 Hannu (Nokia) does not see that anything is broken but offers a note with reference to TS 23.503 to remind of the existing PCF option in r04 Magnus (Ericsson) agrees with CR Tianji (CMCC) OK with the rev#04 ==== Revisions Deadline ==== Yuxin (Xiaomi) comments and can live with r04 Haris(Qualcomm) can only accept r04. Objects to other revisions Stefan (Ericsson) objects to r00-r03. OK with r04. ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305908 | CR | Approval | 23.501 CR4246R1 (Rel-18, 'B'): Optimization consideration for satellite backhaul QoS monitoring | China Mobile | Rel-18 | Revision of S2-2304223r04. Approved | Agreed | |
| 9.1.2 | S2-2304647 | CR | Approval | 23.502 CR4044 (Rel-18, 'F'): Correction on Satellite Backhaul Category clause info | CMCC | Rel-18 | r00 agreed. Revised to S2-2305909. | Guanglei (Huawei) comments Junan Peng (CMCC) replies to Guanglei Heng (China Telecom) agrees with Guanglei (Huawei) Guanglei (Huawei) provides r01 ==== Revisions Deadline ==== Junan Peng (CMCC) agrees with referring to 5.43. Guanglei (Huawei) comments, please ignore r01, we propose to go with r00 + remove '.4' of '5.43.4.' Junan Peng (CMCC) comments, please ignore r01, go with r00 + remove '.4' of '5.43.4.' DongYeon (Samsung) objects to r01, and r00 + with following changes: change 'clause 5.43.4 of TS 23.501' to 'clause 5.43 of TS 23.501' in the coversheet, in the first change, and in the second change section. DongYeon (Samsung) corrects the previous comment: Samsung propose r00 + with following changes: change 'clause 5.43.4 of TS 23.501' to 'clause 5.43 of TS 23.501' in the coversheet, in the first change, and in the second change section, and objects r01. ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305909 | CR | Approval | 23.502 CR4044R1 (Rel-18, 'F'): Correction on Satellite Backhaul Category clause info | CMCC | Rel-18 | Revision of S2-2304647r00. Approved | Agreed | |
| 9.1.2 | S2-2304673 | CR | Approval | 23.503 CR0986 (Rel-18, 'F'): Clarification on Satellite backhaul category change of Policy Control Request Triggers | LG Electronics | Rel-18 | r01 agreed. Revised to S2-2305910, merging S2-2305198 | Junan Peng(CMCC) suggests merging 5198 with 4673. Hucheng (CATT) supports Junan Peng(CMCC)'s suggestion. Hyunsook (LGE) asks to mark this CR as the baseline based on rapporteur's comment. Yuxin (Xiaomi) agrees 5198 can be merged into 4673 . Mirko (Huawei) provides r01. ==== Revisions Deadline ==== Hyunsook (LGE) can accept r01. Yuxin (Xiaomi) agrees with r01 DongYeon (Samsung) would like to co-sign. Please add 'Samsung' in the source in the final version. ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305910 | CR | Approval | 23.503 CR0986R1 (Rel-18, 'F'): Clarification on Satellite backhaul category change of Policy Control Request Triggers | LG Electronics, Xiaomi, Samsung | Rel-18 | Revision of S2-2304673r01, merging S2-2305198. Approved | Agreed | |
| 9.1.2 | S2-2305198 | CR | Approval | 23.503 CR1026 (Rel-18, 'F'): Satellite backhaul category change report from AMF to PCF | Xiaomi | Rel-18 | Merged into S2-2305910 | Hyunsook (LGE) asks to mark this CR as 'merged into 4673' based on rapporteur's comment. Yuxin (Xiaomi) agrees this CR is merged into 4673 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.1.2 | S2-2304822 | CR | Approval | 23.502 CR4071 (Rel-18, 'B'): Update SMF events exposure service to support dynamic satellite backhaul | CMCC | Rel-18 | r00 agreed. Revised to S2-2305911. | Guanglei (Huawei) askes questions Junan Peng (CMCC) replies to questions from Guanglei ==== Revisions Deadline ==== DongYeon (Samsung) would like to co-sign. Please add 'Samsung' in the source in the final version. Junan Peng( CMCC ) is ok to add 'Samsung' in the source in the final version. ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305911 | CR | Approval | 23.502 CR4071R1 (Rel-18, 'B'): Update SMF events exposure service to support dynamic satellite backhaul | CMCC , Samsung | Rel-18 | Revision of S2-2304822r00. Approved | Agreed | |
| 9.1.2 | S2-2305268 | CR | Approval | 23.502 CR4137 (Rel-18, 'B'): Update to support reporting of satellite backhaul category change | China Telecom | Rel-18 | r03 agreed. Revised to S2-2305912, merging S2-2304828 and S2-2304823 | Heng(China Telcom) suggests to merge 5268 with 4823 and 4828. Haris(Qualcomm) comments Heng(China Telecom) reply to Harris(Qualcomm) Haris(Qualcomm) responds Hucheng (CATT) clarifies and comments Junan Peng (CMCC) clarifies and comments Hucheng (CATT) clarifies to Junan Peng (CMCC) Junan Peng (CMCC) clarified to Hucheng (CATT) Hucheng (CATT) replies to Junan Peng (CMCC) Heng(China Telecom) provide r01 Hannu (Nokia) proposes more changes in r02 Haris(Qualcomm) asks further question for clarification Hucheng (CATT) clarifies to the question from Haris. Heng (China Telecom) agrees with Hucheng (CATT) Stefan (Ericsson) provides r03 Haris(Qualcomm) is ok with r02 and to postpone the N2 handover to next meeting Haris(Qualcomm) is also ok with r03 Hannu (Nokia) supports r03 as the best way forward in this meeting ==== Revisions Deadline ==== Junan Peng(CMCC) is also ok with r03 Yuxin (Xiaomi) is ok with r03 ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305912 | CR | Approval | 23.502 CR4137R1 (Rel-18, 'B'): Update to support reporting of satellite backhaul category change | China Telecom, CMCC | Rel-18 | Revision of S2-2305268r03, merging S2-2304828 and S2-2304823. Approved | Agreed | |
| 9.1.2 | S2-2304823 | CR | Approval | 23.502 CR4072 (Rel-18, 'B'): Update PDU Session Modification procedure to support dynamic satellite backhaul | CMCC | Rel-18 | Merged into S2-2305912 | Heng(China Telecom) suggests to merge 4823 with 5268. Haris(Qualcomm) comments Hucheng (CATT) supports Heng(China Telcom) to merge 4823 and 4828 into 5268 . Junan Peng (CMCC) is ok to merge 4823 and 4828 into 5268. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.1.2 | S2-2304828 | CR | Approval | 23.502 CR4073 (Rel-18, 'B'): Add satellite backhaul category ID into PDU session update procedure | CMCC | Rel-18 | Merged into S2-2305912 | Heng(China Telecom) suggests to merge 4828 with 5268. Hucheng (CATT) agrees with Heng(China Telcom) to merge 4823 and 4828 into 5268 . ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.1.2 | S2-2304843 | CR | Approval | 23.503 CR1005 (Rel-18, 'F'): Clarification of QoS monitoring for satellite backhaul | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305913, merging S2-2305117 | Hannu (Nokia) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305913 | CR | Approval | 23.503 CR1005R1 (Rel-18, 'F'): Clarification of QoS monitoring for satellite backhaul | Huawei, HiSilicon | Rel-18 | Revision of S2-2304843r01, merging S2-2305117. Approved | Agreed | |
| 9.1.2 | S2-2305117 | CR | Approval | 23.503 CR1022 (Rel-18, 'F'): Clarify the usage of QoS monitoring for dynamic satellite backhaul | CATT | Rel-18 | Merged into S2-2305913 Merge into S2-2304843, or not handle | Hucheng (CATT) proposes to merge this paper into S2-2304843. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.1.2 | S2-2304921 | CR | Approval | 23.501 CR4434 (Rel-18, 'B'): QoS monitoring trigger conditions update | Xiaomi | Rel-18 | Postponed | Mirko (Huawei) provides r01. Hucheng (CATT) provides r02. Stefan (Ericsson) provides r03 Yuxin (Xiaomi) comments Hannu (Nokia) provides r04 to align the cover page with the CR contents. Mirko (Huawei) comments and can only accept r01. ==== Revisions Deadline ==== Yuxin (Xiaomi) comments and can accept r01, but can also accept r02-r04. Hannu (Nokia) proposes to postpone. ==== Comments Deadline ==== Mirko (Huawei) proposes to agree on r01. | Postponed |
| 9.1.2 | S2-2305269 | CR | Approval | 23.503 CR1032 (Rel-18, 'F'): Correction in 6.1.3.5 to align with 23.501 | China Telecom | Rel-18 | Approved | Hannu (Nokia) provides r01 Heng (China Telecom) comment on r01 Hucheng (CATT) supports r00 and thinks r01 is incorrect. Hannu (Nokia) can live with r00 if the encoding has already been decided to add new dynamic categories instead of indicating multiple categories? ==== Revisions Deadline ==== Heng(China Telecom)reply to Hannu. Hannu (Nokia) thanks Heng for the answer. No objections from me. ==== Comments Deadline ==== | Agreed |
| 9.1.2 | - | - | - | Satellite edge computing | - | - | Docs:=3 | - | |
| 9.1.2 | S2-2304388 | CR | Approval | 23.501 CR4293 (Rel-18, 'B'): Update the descriptions for supporting Edge Computing on satellite | China Mobile, CATT | Rel-18 | r02 agreed. Revised to S2-2305914. | Haris(Qualcomm) comments Stefan (Ericsson) provides comments Dan (China Mobile) reply and provide r01 Hannu (Nokia) proposes that 'and/or' should be left for arithmetic formulas. Dan (China Mobile) provide r02 to reflect Hannu's comment. Hannu (Nokia) agrees with r02 ==== Revisions Deadline ==== Haris(Qualcomm) is ok with r02 only ==== Comments Deadline ==== | Revised |
| 9.1.2 | S2-2305914 | CR | Approval | 23.501 CR4293R1 (Rel-18, 'B'): Update the descriptions for supporting Edge Computing on satellite | China Mobile, CATT | Rel-18 | Revision of S2-2304388r02. Approved | Agreed | |
| 9.1.2 | S2-2305373 | CR | Approval | 23.501 CR4563 (Rel-18, 'B'): Enable Satellite EAS re-discovery and re-allocation by means of local DNS on-board satellite | TNO | Rel-18 | CR Cover sheet error! Noted | Haris(Qualcomm) comments and asks question Hannu (Nokia) asks follow-up question triggered by the comment from Haris Stefan (Ericsson) provides comments and questions Hannu (Nokia) replies to Stefan and repeats his concern that the CR seems to be trying to specify things that are outside of the scope of the CN NFs. Relja (TNO) replies to Harris, Hannu and Stefan and proposes to NOTE this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.2 | - | - | - | Local data switching | - | - | Docs:=1 | - | |
| 9.1.2 | S2-2304856 | CR | Approval | 23.501 CR4422 (Rel-18, 'F'): Clarification of local switch via UPF on GEO satellites | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.2.1 | - | - | - | Study on satellite access Phase 2 (FS_5GSAT_Ph2) | - | - | Docs:=0 | - | |
| 9.2.2 | - | - | - | Satellite access Phase 2 (5GSAT_Ph2) | - | - | Docs:=32 | - | |
| 9.2.2 | - | - | - | LS OUT | - | - | Docs:=5 | - | |
| 9.2.2 | S2-2303998 | LS OUT | Approval | [DRAFT] LS on Provisioning of Satellite Coverage Availability information | Intel | Rel-18 | Revision of S2-2303089 from S2#155. Noted | Steve (Huawei) What happens to this LS? ==== Revisions Deadline ==== Jean-Yves (Thales) propose to decide after CC#3 SoH Steve (Huawei) should be noted Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304341 | LS OUT | Approval | [DRAFT] LS on Satellite Coverage Availability Information (SCAI) provisioning to the UE | Qualcomm | Rel-18 | Noted | Lalith(Samsung) provides r01 Guillaume (MediaTek Inc.): not ok with either the original or r01. Suggests to keep this open until we have a firm decision. ==== Revisions Deadline ==== Stephen (Qualcomm) is okay with the r01 - and agrees that another CC may be needed to resolve LS sending Stefan (Ericsson) proposes to NOTE the LS given the CC#3 outcome ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304361 | LS OUT | Approval | [DRAFT] LS on Overload Control in Support of Discontinuous Network Coverage. | China Mobile | Rel-18 | r00 agreed. Revised to S2-2305576, merging S2-2305300 | Revised | |
| 9.2.2 | S2-2305576 | LS OUT | Approval | LS on Overload Control in Support of Discontinuous Network Coverage | SA WG2 | Rel-18 | Revision of S2-2304361r00, merging S2-2305300. Approved | Approved | |
| 9.2.2 | S2-2305300 | LS OUT | Approval | [DRAFT] LS on discontinuous coverage wait range | Samsung | Rel-18 | Merged into S2-2305576 | Jean-Yves (Thales) propose to keep a single LS out (4361) in between this S2-2305300 and S2-2304361 Lalith(Samsung) is OK to mark this tdoc merged into S2-2304361 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.2.2 | - | - | - | DP for Discussion | - | - | Docs:=1 | - | |
| 9.2.2 | S2-2304920 | DISCUSSION | Information | Discussion on power saving parameters determination and related EN resolution | Xiaomi | Rel-18 | Noted | Noted | |
| 9.2.2 | - | - | - | DP for Agreement / Approval | - | - | Docs:=5 | - | |
| 9.2.2 | S2-2303993 | DISCUSSION | Information | Standardization of Satellite Coverage Availability (SCA) information | Intel, THALES | Rel-18 | Noted | Stephen (Qualcomm) agrees with the proposals and provides comments Guillaume (MediaTek Inc.) comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304121 | DISCUSSION | Discussion | Analysis of topics related to timers for availability gaps | Ericsson | Rel-18 | Noted | Stephen (Qualcomm) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304342 | DISCUSSION | Information | Resolution of open issues for out-of-coverage reporting for Discontinuous Coverage | Qualcomm Incorporated | Rel-18 | Noted | Noted | |
| 9.2.2 | S2-2304431 | DISCUSSION | Discussion | 5GSAT EN Resolutions | Huawei, HiSilicon | Rel-18 | Noted | Stephen (Qualcomm) provides comments ==== Revisions Deadline ==== Jean-Yves (Thales) this document should be noted ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2305383 | DISCUSSION | Information | Satellite Coverage Availability Information (SCAI) | Qualcomm CDMA Technologies | Rel-18 | Noted | Noted | |
| 9.2.2 | - | - | - | CRs on TS 23.501 | - | - | Docs:=11 | - | |
| 9.2.2 | S2-2303994 | CR | Approval | 23.501 CR4123R2 (Rel-18, 'B'): Satellite Coverage Availability Function (SCAF) services | Intel, THALES | Rel-18 | Revision of S2-2302296 from S2#155. CR Cover sheet error! Noted | Stephen (Qualcomm) supports the CR and provides comments Hannu (Nokia) does not believe that SCAF is needed. Proposes to note the CR. ==== Revisions Deadline ==== Steve (Huawei) should be noted Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2303997 | CR | Approval | 23.682 CR0491R1 (Rel-18, 'B'): Introduction of Satellite Coverage Availability Function (SCAF) | Intel, THALES | Rel-18 | Revision of S2-2302877 from S2#155. Confirm Spec version used - CR states 17.3.0! Noted | Laurent (Nokia): Objects to any version of this Tdoc to have a single thread to discuss actual CR text = that of 4219 Stefan (Ericsson) proposes to note the CR ==== Revisions Deadline ==== Steve (Huawei) should be noted Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304407 | CR | Approval | 23.501 CR4302 (Rel-18, 'B'): Provisioning Satellite Coverage Availability to the AMF | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | r03 agreed. Revised to S2-2305577. Provisioning Satellite Coverage Availability to the AMF via O&M. Concurrent solution to S2-2303994 (provisioning via SCAF) | Jean-Yves (Thales) comments Hannu (Nokia) replies Jean-Yves Jean-Yves (Thales) replies Hannu Hannu (Nokia) replies to Jean-Yves Saso (Intel) provides r01 Stephen (Qualcomm) provides r02 Yuxin (Xiaomi) comments Hannu (Nokia) provides r03 ==== Revisions Deadline ==== Stephen (Qualcomm) can agree the r03; the r00 and r01 are not acceptable Yuxin (Xiaomi) can accept the r03 Steve (Huawei) is ok with r03. Jean-Yves (Thales) is ok with r03 ==== Comments Deadline ==== | Revised |
| 9.2.2 | S2-2305577 | CR | Approval | 23.501 CR4302R1 (Rel-18, 'B'): Provisioning Satellite Coverage Availability to the AMF | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304407r03. Approved | Agreed | |
| 9.2.2 | S2-2304122 | CR | Approval | 23.501 CR4214 (Rel-18, 'C'): Removal of editor s notes related to UE-AMF timer exchanges | Ericsson | Rel-18 | Noted | Saso (Intel) seeks clarifications and provides comments Yuxin (Xiaomi) comments Stefan (Ericsson) replies to Yuxin and Saso Yuxin (Xiaomi) replies to Stefan Stephen (Qualcomm) provides comments Lalith (Samsung) provides comments Steve (Huawei) comments to concentrate on 401 ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note the CR Stefan (Ericsson) ok to NOTE Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304208 | CR | Approval | 23.501 CR4240 (Rel-18, 'C'): Closing ENs for the procedures for discontinuous coverage reporting | Qualcomm Incorporated | Rel-18 | Noted | Lalith (Samsung) comments. Steve (Huawei) comments. Guillaume (MediaTek Inc.) comments Jean-Yves (Thales) responds to Guillaume and proposes a SoH for CC#2 on (at least) the 2 questions Saso (Intel) asks clarification from QC (and also supports Rapporteur's proposal for SoH). Stephen (Qualcomm) provides an r01 and comments Jean-Yves (Thales) comments in between 4208 & 4432 and propose to use 4208 as baseline Steve (Huawei) we should take 4432, 4208 cannot be copied over the 401. Yingying(CATT) provides comments. Stefan (Ericsson) provides comments and questions Yuxin(Xiaomi) provides comments. Jean-Yves(Thales) provides comments. Yingying(CATT) replies to Jean-Yves (Thales). Stephen (Qualcomm) provides more comments Lalith(Samsung) provides r02 Jean-Yves (Thales) note SoH requested between 4208 and 4432, and will prepare slide for CC#3 Stephen (Qualcomm) provides an r03 and comments Steve (Huawei) comments to concentrate on 401 Yuxin (Xiaomi) askes a question and provides r04 Stefan (Ericsson) provides r05 Hannu (Nokia) provides r06 to replace 'Maximum Wait Time' by 'NAS signalling wait time' in alignment with 4406. ==== Revisions Deadline ==== Stephen (Qualcomm) can agree the r06; the r03, r04, r05 are also agreeable; r02 is less preferred but okay too Guillaume (MediaTek Inc.) suggests to postpone the CR Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 Stefan (Ericsson) ok to postpone ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304432 | CR | Approval | 23.501 CR4307 (Rel-18, 'F'): Discontinuous Coverage EN Resolution | Huawei, HiSilicon | Rel-18 | Noted | Lalith (Samsung) comments. Saso (Intel) seeks clarification. Guillaume (MediaTek Inc.) provides r01 Steve (Huawei) comments. Guillaume (MediaTek Inc.) replies to Steve (Huawei) Steve (Huawei) comments, provides r02 Yingying(CATT) provides comments. Stephen (Qualcomm) provides comments Jean-Yves (Thales) comments in between 4208 & 4432 and propose to use 4208 as baseline Yingying(CATT) provides comments and r04, please ignore r03. Steve (Huawei) we should take 4432, 4208 cannot be copied over the 401. Jean-Yves (Thales) comments. Hannu (Nokia) shares r05 Saso (Intel) provides r06 Stephen (Qualcomm) provides more comments Jean-Yves (Thales) note SoH requested between 4208 and 4432, and will prepare slide for CC#3 Steve (Huawei) comments to concentrate on 401 Stefan (Ericsson) is not sure about the status of 4432 but provides r07 Jean-Yves (Thales) comments on 4432 versus 4208 ==== Revisions Deadline ==== Stephen (Qualcomm) disagrees all versions of the CR Guillaume (MediaTek Inc.) suggests to postpone this CR Lalith(Samsung) proposes to postpone this CR. Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 Stefan (Ericsson) supports to note/postpone ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304919 | CR | Approval | 23.501 CR4433 (Rel-18, 'C'): Power saving parameters determination and EN resolution | Xiaomi | Rel-18 | Noted | Steve (Huawei) comments to concentrate on 401 Lalith(Samsung) proposes to merge this in 4208 ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to merge this CR into S2-2304208 Yuxin (Xiaomi) is fine to merge this CR into S2-2304208 Yuxin (Xiaomi) propose to note this CR Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304365 | CR | Approval | 23.501 CR4286 (Rel-18, 'B'): Update about the support of discontinuous network coverage for satellite access | China Mobile, CATT | Rel-18 | Noted | Lalith(Samsung) comments Steve (Huawei) comments to concentrate on 401 Dan (China Mobile) ok to postponed this paper in next meeting ==== Revisions Deadline ==== Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304613 | CR | Approval | 23.501 CR4360 (Rel-18, 'B'): Resolve EN for capability negotiation | LG Electronics | Rel-18 | CR Cover sheet error! Noted | Lalith(Samsung) proposes to merge this in 4208 Steve (Huawei) comments to concentrate on 401 Jaewoo (LGE) replies to Lalith (Samsung) and this paper cannot be considered to be merge in 4208. Lalith(Samsung) replies to Jaewoo (LGE). ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to merge this CR into S2-2304208 Jaewoo (LGE) replies to Stephen (Qualcomm). Jaewoo (LGE) proposes to note this CR. Steve (Huawei) should be noted. Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2305089 | CR | Approval | 23.501 CR4479 (Rel-18, 'B'): Remove ENs for Coverage availability information provisioning to the AMF | CATT | Rel-18 | Noted | Stefan (Ericsson) proposes to note the CR Yingying(CATT) agrees with Stefan (Ericsson). ==== Revisions Deadline ==== Steve (Huawei) should be noted Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | - | - | - | CRs on TS 23.401 | - | - | Docs:=3 | - | |
| 9.2.2 | S2-2305295 | CR | Approval | 23.401 CR3732 (Rel-18, 'B'): Wait timer for Discontinuous coverage | Samsung | Rel-18 | Merge into S2-2304434 (withdrawn). Postponed Merge into (revision of) S2-2304434 | Steve (Huawei) merge to 4434? Lalith (Samsung) is OK to mark it merged to 4434 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.2.2 | S2-2303996 | CR | Approval | 23.401 CR3725R1 (Rel-18, 'B'): Introduction of Satellite Coverage Availability Function (SCAF) | Intel, THALES | Rel-18 | Revision of S2-2302875 from S2#155. Noted | Stefan (Ericsson) proposes to note the CR based on the CC#2 outcome ==== Revisions Deadline ==== Steve (Huawei) should be noted Jean-Yves (Thales) agrees to note, given balanced results of SoH in CC#2 and CC#3 ==== Comments Deadline ==== | Noted |
| 9.2.2 | S2-2304434 | CR | Approval | 23.401 CR3721R4 (Rel-18, 'B'): Support of mobility management and power saving with discontinuous coverage | Huawei, HiSilicon, [Thales], [Novamint] | Rel-18 | Revision of S2-2303428 from S2#155. CC#4: Postponed For CC#4 | Guillaume (MediaTek Inc.) provides r01 Steve (Huawei) comments. Steve (Huawei) comments, provides r02 Lalith (Samsung) provides r03 Stefan (Ericsson) provides r04 Saso (Intel) provides r04 Lalith (Samsung) provides r05 over r04. Hannu (Nokia) provides r06 to replace 'maximum waiting time' by 'NAS signalling wait time' in alignment with S2-2304406 Guillaume (MediaTek Inc.) provides r07 Steve (Huawei) provides r08 Guillaume (MediaTek Inc.) provides r09 ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to postpone this CR as it contains changes under discussion and not yet agreed in SA2 and is not fully aligned with at least one major CR to TS 23.501 Guillaume (MediaTek Inc.) ok to postpone Steve (Huawei) would prefer to agree it (with modifications if needed) Jean-Yves (Thales) as rapporteur, strongly prefer to agree (with modifications if needed) Lalith(Samsung) proposes to agree r09 with below changes: In clause 4.13.x.2 Remove below text: In case the UE indicated, as described above, an out-of-coverage period to the network and this out-of-coverage period has not started yet, if the UE determines that it no longer applies or determines a new Start of Unavailability Period, the UE restarts the procedure as described above Add this: If the UE previously sent a TAU Request procedure indicating an Unavailability Period Duration and included a Start of Unavailability Period and if the new TAU request occurs before the out-of-coverage period has started and if the out-of-coverage period will still occur, the UE shall indicate recalculated new Unavailability Period Duration and/or Start of Unavailability Period. If new Start of Unavailability Period and/or Unavailability Period Duration is included then the MME assumes the any previous out-of-coverage period will no longer occurs or has completed and the MME deletes this from UE context Guillaume (MediaTek Inc.) supports Jean-Yves (Thales) in agreeing the CR Lalith(Samsung) comments Jean-Yves (Thales) ok to agree r09 with proposed changes Guillaume (MediaTek Inc.) responds. Steve (Huawei) provides possible EN. Lalith (Samsung) replies to Guillaume (MediaTek Inc.) Guillaume (MediaTek Inc.) replies to Lalith (Samsung) Lalith (Samsung) based on further discussion, propose to agree r09. With below changes: In clause 4.13.x.2 Remove below text: In case the UE indicated, as described above, an out-of-coverage period to the network and this out-of-coverage period has not started yet, if the UE determines that it no longer applies or determines a new Start of Unavailability Period, the UE restarts the procedure as described above And Add below editor notes Editor's note: The MME and UE behaviour when UE triggers new TAU, subsequent to setting of Unavailability Period Duration with Start time at MME and before start of out of coverage period is FFS. Stefan (Ericsson) comments Jean-Yves (Thales) ok to agree r09 with proposed below changes Steve (Huawei) comments on the EN Lalith(Samsung) is OK with proposal of Steve (Huawei) Guillaume (MediaTek Inc.): ok so the end result is agree r09 with the following changes: In clause 4.13.x.2: 1) Remove this text: 'In case the UE indicated, as described above, an out-of-coverage period to the network and this out-of-coverage period has not started yet, if the UE determines that it no longer applies or determines a new Start of Unavailability Period, the UE restarts the procedure as described above' 2) And add this editor's note instead: 'Editor's note: The MME and UE behaviour when a UE triggers a new TAU, subsequent to providing Unavailability Period Duration with Start time to the MME and before start of out of coverage period is FFS.' Steve (Huawei) agrees with the proposal for r09 with replacement EN from Guillaume (MediaTek Inc.) Lalith(Samsung) agrees with the proposal for r09 with replacement EN from Guillaume (MediaTek Inc.) Hannu (Nokia) supports r09 with the edits proposed by Guillaume and the EN cleanup proposed by Steve. Haris(Qualcomm) comments that does not understand what the new EN means ==== Comments Deadline ==== Guillaume (MediaTeK Inc.) replies to Haris (Qualcomm) | Postponed |
| 9.2.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=7 | - | |
| 9.2.2 | S2-2303995 | CR | Approval | 23.502 CR3879R1 (Rel-18, 'B'): Satellite Coverage Availability Function (SCAF) services | Intel, THALES | Rel-18 | Revision of S2-2302297 from S2#155. CR Cover sheet error! Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2304433 | CR | Approval | 23.502 CR3823R3 (Rel-18, 'B'): Procedures for support of discontinuous coverage | Huawei, HiSilicon, [Thales], [Intel], [Xiaomi] | Rel-18 | Revision of S2-2302880 from S2#155 Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2305155 | CR | Approval | 23.502 CR4115 (Rel-18, 'B'): Satellite coverage availability information exposure to AMF from the AF | CATT | Rel-18 | Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2305174 | CR | Approval | 23.502 CR4119 (Rel-18, 'B'): Add the discontinuous coverage support indication to the registration procedure | CATT | Rel-18 | Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2305298 | CR | Approval | 23.502 CR4141 (Rel-18, 'B'): Wait range during discontinuous coverage. | Samsung | Rel-18 | Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2305382 | CR | Approval | 23.502 CR4159 (Rel-18, 'B'): Support of discontinuous satellite coverage | Qualcomm Incorporated | Rel-18 | Priority to 23.501 & 23.401 | NOT HANDLED | |
| 9.2.2 | S2-2304406 | CR | Approval | 23.501 CR4301 (Rel-18, 'D'): Terminology correction to avoid (almost) duplicate definition | Nokia, Nokia Shanghai Bell | Rel-18 | Not too big impact if not approved (naming) | NOT HANDLED | |
| 9.3.1 | - | - | - | Study on Personal IoT Networks (FS_5G_PIN) | - | - | Docs:=0 | - | |
| 9.3.2 | - | - | - | Personal IoT Networks (PIN) | - | - | Docs:=62 | - | |
| 9.3.2 | - | - | - | Discussions and Way forward proposal | - | - | Docs:=7 | - | |
| 9.3.2 | S2-2304643 | DISCUSSION | Agreement | Mapping relation of PIN with PDU Session for PEGC | Qualcomm Incorporated | Rel-18 | Noted | Noted | |
| 9.3.2 | S2-2304928 | DISCUSSION | Agreement | Discussion on support of local switching | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.3.2 | S2-2304993 | DISCUSSION | Information | Way forward proposal for PIN | vivo | Rel-18 | Noted | Zhenhua (vivo) propose sync general procedure before next meeting. ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2305293 | DISCUSSION | Agreement | Way forward proposal for Session Management for PIN | Rel-18 | Noted | Noted | ||
| 9.3.2 | S2-2305303 | DISCUSSION | Decision | Which PIN IDs? | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.3.2 | S2-2305307 | DISCUSSION | Agreement | Multiple PINs sharing the same PDU Session in a PEGC | InterDigital Inc. | Rel-18 | Noted | Devaki (Nokia) comments that this CR seems to have been written under a wrong assumption?! In our understanding, subscription shall not be modified, only AMF handling is adjusted. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2305309 | DISCUSSION | Agreement | One PIN Served by more than one PDU Session in a PEGC | InterDigital Inc. | Rel-18 | Noted | Noted | |
| 9.3.2 | - | - | - | LS In/Out | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2303983 | LS In | Information | LS from SA WG6: LS on Alignment of SA WG3 security aspects for Personal IoT Networks | SA WG6 (S6-230792) | Rel-18 | Noted | Noted | |
| 9.3.2 | S2-2305160 | LS OUT | Approval | [DRAFT] LS on Information about PEGC not being able to serve PIN | LG Electronics | Rel-18 | Noted | Kenny (Qualcomm) provides comments and propose to note this contribution. Pallab (Nokia) supports Qualcomm and proposes to NOTE the LS. LaeYoung (LGE) provides r01 and replies to Kenny (Qualcomm) and Pallab (Nokia). Marco (Huawei) agree to note the LS Saad(Interdigital) supports to send the LS out to SA6 Pallab (Nokia) responds to LaeYoung (LGE) Jianning (Xiaomi) provide comment LaeYoung (LGE) is fine to NOTE this LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.3.2 | - | - | - | 23.501 CRs | - | - | Docs:=16 | - | |
| 9.3.2 | - | - | - | Mapping issues | - | - | Docs:=6 | - | |
| 9.3.2 | S2-2304175 | CR | Approval | 23.501 CR4224 (Rel-18, 'F'): PDU session sharing among PINs | Ericsson | Rel-18 | r13 agreed. Revised to S2-2306176, merging S2-2305297, S2-2304850 and S2-2305310 | Zhenhua (vivo) provides r01. Kenny (Qualcomm) provides r02. Marco (Huawei) ask clarification on SoH and provide r03 Ellen (Google) ask clarification on this CR and r03 Saad (Interdigital) asks a question for clarification Qian (Ericsson) provides comments and r04. Zhenhua (vivo) replies to Saad (Interdigital) Zhenhua (vivo) comments and provides r05. Qian (Ericsson) provides comments. Marco (Ericsson) comments on Non-PIN traffic and to r05 Zhenhua (vivo) replies to Marco (Huawei) Ellen (Google) asks questions about IPv6 prefix delegation example from Zhenhua (vivo) Kenny (Qualcomm) provides comments and r06. Susan (Huawei) provides r07. Zhenhua (vivo) replies to Ellen (Google) and provides r08 Ellen (Google) thanks Zhenhua (vivo) classification and provides r09 Ellen (Google) fixed r9 link Susan (Huawei) provides r10. Jichel (Samsung) provides r11 with small clarification. Zhenhua (vivo) provides r12 Ellen (Google) provides r13 that restored an Editor's note that is not resolved in this paper Ellen (Google) provides r14 to merge 5297 ==== Revisions Deadline ==== Ellen (Google) is fine with r13 or r14 LaeYoung (LGE): r14 NOT Acceptable, r12 Preferred and can live with r13. Jianning (Xiaomi) asks questions for clarification on r14 Kenny (Qualcomm) is OK with r13, r12, r11, not OK with other revisions. Qian (Ericsson) prefers r12, but can live with r13. Objects r14. Huawei (Susan) is OK with r10 to r14. Pallab (Nokia) proposes to approve r12. Can live with r13. Objects to r14 Ellen (Google) proposes to approve r13 which is only for multiple PINs using shared PDU Session via PEGC (based on SoH CC#1). r12 deleted another Editor's note which hadn't had consensus in this meeting. ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306176 | CR | Approval | 23.501 CR4224R1 (Rel-18, 'F'): PDU session sharing among PINs | Ericsson | Rel-18 | Revision of S2-2304175r13, merging S2-2305297, S2-2304850 and S2-2305310. Approved | Agreed | |
| 9.3.2 | S2-2304489 | CR | Approval | 23.501 CR4328 (Rel-18, 'F'): Solve the EN about PINs sharing a PDU session | Huawei, HiSilicon | Rel-18 | Noted | Marco (Huawei) considered to be noted per SoH CC#1 (part for NON-PIN traffic to be further considered) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2305297 | CR | Approval | 23.501 CR4544 (Rel-18, 'B'): Clarification on Session Management Associations with multiple PINs | Rel-18 | Merged into S2-2306176 | Marco (Huawei) the revision to clause 5.44.3.1 to be considered supersede by SoH in CC#1 Pallab (Nokia) provides comments. Proposes to consider this as merged to 4175 Qian (Ericsson) provides comments Kenny (Qualcomm) provides comments Ellen (Google) provides feedback and r01 Ellen (Google) provides r02 that focus on one Editor's note and clean up the cover page LaeYoung (LGE) proposes to NOTE this CR Kenny (Qualcomm) proposes to NOTE this CR or merge into 4175 Ellen (Google) agreed to merge this paper into 4175 to clarify the second Editor's note in the same clause. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged | |
| 9.3.2 | S2-2304850 | CR | Approval | 23.501 CR4417 (Rel-18, 'F'): Clarification on PDU Session for PIN | LG Electronics | Rel-18 | Merged into S2-2306176 Merge into S2-2306176? | Marco (Huawei) propose to consider noted for SoH CC#1 LaeYoung (LGE) is fine to NOTE this CR or to MERGE into S2-2304175. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.3.2 | S2-2305310 | CR | Approval | 23.501 CR4546 (Rel-18, 'C'): Update to remove the EN about one PIN using more than one PDU Session | InterDigital Inc. | Rel-18 | Merged into S2-2306176 Merge into S2-2306176? | Marco (Huawei) proposes to considered merged to 4175 and supersede by SoH CC#1 Kenny (Qualcomm) proposes to merged into 4175 or note this CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.3.2 | - | - | - | Non-3GPP QoS | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2304359 | CR | Approval | 23.501 CR4284 (Rel-18, 'C'): Clarifying SMF behaviour for non-3GPP delay budget | Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | r02 agreed. Revised to S2-2306177. | Marco (Huawei) comments and provides r01 Kenny (Qualcomm) replies Marco (Huawei) comments and provides r02 Jicheol (Samsung) asks clarification questions. Kenny (Qualcomm) replies Jicheol (Samsung) questions. ==== Revisions Deadline ==== Kenny (Qualcomm) proposes to take r02 for approval. Qian (Ericsson) is ok with r02. Marco (Huawei) prefers r01 ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306177 | CR | Approval | 23.501 CR4284R1 (Rel-18, 'C'): Clarifying SMF behaviour for non-3GPP delay budget | Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304359r02. Approved | Agreed | |
| 9.3.2 | - | - | - | Identifier | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2304373 | CR | Approval | 23.501 CR4287 (Rel-18, 'B'): PIN identifiers | Nokia, Nokia Shanghai Bell | Rel-18 | r08 agreed. Revised to S2-2306178. | Zhenhua (vivo) provides r01. LaeYoung (LGE) asks some questions. Pallab (Nokia) cannot accept r01. Responds to LaeYoung (LGE) and Zhenhua (vivo) Sudeep (Apple) comments. Pallab (Nokia) Responds to Sudeep (Apple) Zhenhua (vivo) provides r02 Sudeep (Apple) comments on r02. Susan (Huawei) raises questions for clarification. Zhenhua (vivo) share the same view as Susan (Huawei) and provides r03 Pallab (Nokia) Responds Sudeep (Apple), Susan (Huawei) and provides r04 based on r02 LaeYoung (LGE) provides comment on r04. Marco (Huawei) disagree with r03 and part of r04. Provide r05 Sudeep (Apple) provides r06. Jianning (Xiaomi) replies to Sudeep (Apple) Pallab (Nokia) provides r08. Jianning (Xiaomi) provide comment on r06 and provide r07 on top of r05 Jianning (Xiaomi) comments on r08 Pallab (Nokia) responds to Jianning (Xiaomi) ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r08 and let's improve the contents in the next meeting. Kenny (Qualcomm) is OK with r08. Qian (Ericsson) is OK with r08. Marco (Huawei) ok with r08 NOK r07 objects r03, r04. Jianning (Xiaomi) replies to Pallab (Nokia) Jianning (Xiaomi) propose to postpone or only accept r08 with an EN ' Editor's Note: whether need three identifiers (i.e. PIN ID, external Group Identifier, internal Group Identifier) for PIN is FFS', Pallab (Nokia) objects to adding EN on top of r08 Qian (Ericsson) comments Marco (Huawei) comment ==== Comments Deadline ==== Jianning (Xiaomi) provide comments | Revised |
| 9.3.2 | S2-2306178 | CR | Approval | 23.501 CR4287R1 (Rel-18, 'B'): PIN identifiers | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304373r08. CC#4: Approved | Agreed | |
| 9.3.2 | - | - | - | Traffic routing | - | - | Docs:=5 | - | |
| 9.3.2 | S2-2304487 | CR | Approval | 23.501 CR4326 (Rel-18, 'F'): Solve the EN about handling of the PEMC in 5GC in relation with PIN | Huawei, HiSilicon | Rel-18 | Approved | Jianning (Xiaomi) propose to NOTE this CR, or for CC#4 ==== Comments Deadline ==== | Agreed |
| 9.3.2 | S2-2304998 | CR | Approval | 23.501 CR4452 (Rel-18, 'B'): UP management for PIN | vivo | Rel-18 | Merged into S2-2306180 Merge into S2-2306180? | Pallab (Nokia) provides comments Zhenhua (vivo) clarifies to Pallab (Nokia) Pallab (Nokia) responds to Zhenhua (vivo) Kenny (Qualcomm) provides comments Zhenhua (vivo) provides r01 Marco (Huawei) comments Zhenhua (vivo) replies to Marco (Huawei) and provide r02 Pallab (Nokia) responds to Zhenhua (vivo) and provide r03 Zhenhua (vivo) provide r04 Qian (Ericsson) provides comments and suggests to merge this one into 4996 Zhenhua (vivo) replies to Qian (Ericsson) Susan (Huawei) asks questions to Pallab (Nokia) for clarification. Pallab (Nokia) responds to Susan (Huawei) Susan (Huawei) replies to Pallab (Nokia). Marco (Huawei) comment to Pallab (Nokia) Jicheol (Samsung) comments on r04 and propose to consider postponing this paper. Zhenhua (vivo) replies to Jicheol (Samsung) Kenny (Qualcomm) comment to Marco (Huawei) Marco (Huawei) answer to Kenny (Qualcomm) ==== Revisions Deadline ==== Zhenhua (vivo) share some view with Marco (Huawei) Kenny (Qualcomm) replies Marco (Huawei) question. ==== Comments Deadline ==== | Merged |
| 9.3.2 | S2-2304547 | CR | Approval | 23.501 CR4340 (Rel-18, 'C'): Support for local routing of PIN traffic | Apple | Rel-18 | Merged into S2-2306180 Merged into (revision of) S2-2304998? | Zhenhua (vivo) provides comments Kenny (Qualcomm) provides comments Pallab (Nokia) provides comments Qian (Ericsson) share similar views from previous comment and it's not clear what extra is needed for PIN Sudeep (Apple) responds to comments. OK to proceed with S2-2304998r04. Marco (Huawei) this CR need to be considered merged to S2-2304998 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.3.2 | S2-2304929 | CR | Approval | 23.501 CR4438 (Rel-18, 'B'): Traffic routing within PIN | Huawei, HiSilicon | Rel-18 | Postponed | Zhenhua (vivo) clarifies to Kefeng (Qualcomm). Jianning (Xiaomi) provide comment Susan (Huawei) replies to Jianning (Xiaomi). Susan (Huawei) replies to Zhenhua (Vivo). Kenny (Qualcomm) provides comments. Susan (Huawei) replies to Kenny (Qualcomm). Kenny (Qualcomm) replies to Susan (Huawei). Zhenhua (vivo) comments. Pallab (Nokia) comments. Kenny (Qualcomm) replies Susan (Huawei) comments. Qian (Ericsson) provides comments. Susan (Huawei) replies and asks questions how the existing 5G VN group mechanism can be reused. ==== Revisions Deadline ==== Kenny (Qualcomm) objects the CR and suggests to reuse the existing 5G group mechanism. Susan (Huawei) replies to Kenny (Qualcomm) and asks for discussion at CC#3. Pallab (Nokia) proposes to POSTPONE. Jianning (Xiaomi) provide questions for clarification Jianning (Xiaomi) replies to Pallab (Nokia) Pallab (Nokia) responds to Jianning (Xiaomi). Qian (Ericsson) proposes to Postpone and provides comments. Susan (Huawei) replies to Qian (Ericsson). Qian (Ericsson) comments. ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2305296 | CR | Approval | 23.501 CR4543 (Rel-18, 'B'): Clarification on PEMC role in a PIN | Rel-18 | Covered by S2-2304487 | Marco (Huawei) ask clarification Ellen (Google) replies to Marco (Huawei) Qian (Ericsson) provides comments Ellen (Google) replies to Qian (Ericsson) and provided r01 Kenny (Qualcomm) provides comments. Pallab (Nokia) provides comments. Sudeep (Apple) agrees with Pallab's (Nokia) suggestion. Marco (Huawei) commented that a revision r02 is required to capture the other comments. Ellen (Google) provides revision r02 to capture the other comments. Ellen (Google) provides revision r03 to unticked ME impacts and remove changes in 5.44.3.2 ==== Revisions Deadline ==== LaeYoung (LGE) proposes to NOTE this CR because the same change in r03 is proposed in S2-2304487 already approved. Qian (Ericsson) indicates this can be considered as merged as well ??. ==== Comments Deadline ==== | Noted | |
| 9.3.2 | - | - | - | PIN Activation/deactivation | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2304488 | CR | Approval | 23.501 CR4327 (Rel-18, 'F'): Solve the EN about PIN deletion, activation and deactivation | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2306179. | Zhenhua (vivo) provides r01 and co-sign. ==== Revisions Deadline ==== Jianning (Xiaomi) can live with r01 without additional clarification text (i.e. the management of PIN network creation, deletion and update), just remove the Editor's note. ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306179 | CR | Approval | 23.501 CR4327R1 (Rel-18, 'F'): Solve the EN about PIN deletion, activation and deactivation | Huawei, HiSilicon, vivo | Rel-18 | Revision of S2-2304488r01. Approved | Agreed | |
| 9.3.2 | - | - | - | UE policy related | - | - | Docs:=3 | - | |
| 9.3.2 | S2-2305243 | CR | Approval | 23.501 CR4537 (Rel-18, 'B'): Remove the EN for handling the PEMC and PINE (UE) in PIN | Xiaomi | Rel-18 | Noted | Zhenhua (vivo) provides r01. LaeYoung (LGE) cannot accept r00 and r01. Jianning (Xiaomi) responses to LaeYoung (LGE) LaeYoung (LGE) replies to Jianning (Xiaomi). Jianning (Xiaomi) replies to LaeYoung (LGE) Pallab (Nokia) provides comments and also shares concerns from LGE with r00, r01 Jianning (Xiaomi) responses to Pallab (Nokia) Serge (T-Mobile USA) provides comments and also agrees with LGE and Nokia and has concerns with r00, r01 Marco (Huawei) objects r00 and r01 Pallab (Nokia) responds to Jianning (Xiaomi) Qian (Ericsson) provides comments and asks questions Jianning (Xiaomi) replies to Serge (T-Mobile) Jianning (Xiaomi) replies to Marco(Huawei) and provides r02 Jianning (Xiaomi) replies to Pallab (Nokia) Jianning (Xiaomi) replies to Qian (Ericsson) Kenny (Qualcomm) provides comments. ==== Revisions Deadline ==== LaeYoung (LGE) proposes to NOTE this CR because all versions are NOT acceptable. Qian (Ericsson) supports the proposal to NOTE the paper. ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2304490 | CR | Approval | 23.501 CR4329 (Rel-18, 'B'): Update PIN policy delivery for PIN | Huawei, HiSilicon | Rel-18 | Noted | Kenny (Qualcomm) provides comments. Pallab (Nokia) has exactly the same question as raised by Kenny (Qualcomm). Jianning (Xiaomi) provide comments Marco (Huawei) answers to comments Pallab (Nokia) replies to Marco (Huawei) and proposes to NOTE the CR Qian (Ericsson) provides comments Marco (Huawei ) answers to comments Jicheol (Samsung) comments. Marco (Huawei) answer to Jicheol (Samsung) Ellen (Google) comments. ==== Revisions Deadline ==== Kenny (Qualcomm) proposed to note the CR Qian (Ericsson) proposed also to note the CR ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2304999 | CR | Approval | 23.501 CR4453 (Rel-18, 'B'): Update UE policy delivery for PIN | vivo | Rel-18 | CC#4: Postponed Approve 08? For CC#4 | Zhenhua (vivo) provides r01. Kenny (Qualcomm) provide comments and proposed to note this CR. Zhenhua (vivo) clarifies to Kefeng (Qualcomm). Kenny (Qualcomm) replies Zhenhua (vivo) comments. Zhenhua (vivo) provides r02. Jianning (Xiaomi) provide comments Jianning (Xiaomi) provides comment LaeYoung (LGE) asks a Q. Zhenhua (vivo) replies to LaeYoung (LGE) and Jianning (Xiaomi). Zhenhua (vivo) replies to Jianning (Xiaomi) Jianning (Xiaomi) asks question for clarification Jianning (Xiaomi) replies to Zhenhua (vivo) Pallab (Nokia) provides comments on r02. Proposes to NOTE the CR Zhenhua (vivo) replies to Pallab (Nokia) Pallab (Nokia) responds to Zhenhua (vivo) Zhenhua (vivo) replies to Pallab (Nokia) and provides r03 Jianning (Xiaomi) provide comments and r04 Marco (Huawei) all this discussion depends by PDU session decision. Marco (Huawei) provides comments to r04 Zhenhua (vivo) clarifies the NOTE to Marco (Huawei) Susan (Huawei) replies to Zhenhua (vivo) and proposes to note this CR. LaeYoung (LGE) comments. LaeYoung (LGE) replies to Zhenhua (vivo). Pallab (Nokia) responds to Zhenhua (vivo) and Jianning (Xiaomi) Marco (Huawei) comments Qian (Ericsson) provides comments Saad (Interdigital) provides comments on r04 Marco (Huawei) comments that a PDU session dedicated to PIN shall not be shared with non-PIN traffic Zhenhua (vivo) provides r05 Pallab (Nokia) provides comments on r05 Zhenhua (vivo) provides r06 Jicheol (Samsung) provides r08 (skipping r07 due to type). Pallab (Nokia) responds to Jicheol (Samsung) Marco (Huawei) ask to Pallab (Nokia) clarification ==== Revisions Deadline ==== Kenny (Qualcomm) is OK with r08, r07, r05, not OK with other revisions. Susan (Huawei) can accept r06, and object to any other versions, including the original one r00. Jianning (Xiaomi) prefers r06 Pallab (Nokia) OK to go with r06 or r08. If we take r08 prefer to change to NOTE as below: NOTE: The operator can configure URSP rules in the PEGC in a way that PDU Session associated with PIN(s) is not use for routing non-PIN traffic from the PEGC UE. ==== Comments Deadline ==== Zhenhua (vivo) suggest we go r06, we have May meeting to revise it, if it still not acceptable, companies can object it in May meeting Kenny (Qualcomm) can accept r06 as a compromise. LaeYoung (LGE) is fine to go with r06. Qian (Ericsson) is also ok to go with r06. | Postponed |
| 9.3.2 | - | - | - | Others | - | - | Docs:=10 | - | |
| 9.3.2 | S2-2304177 | CR | Approval | 23.501 CR4226 (Rel-18, 'B'): PIN related subscription for PEGC and PIN realization in 5GC | Ericsson | Rel-18 | Postponed | Zhenhua (vivo) comments and provides r01 ==== Revisions Deadline ==== Susan (Huawei) cannot accept both versions, i.e. r00 and r01, and asks to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2304852 | CR | Approval | 23.501 CR4419 (Rel-18, 'B'): PEGC operation related to PDU Session for PIN | LG Electronics | Rel-18 | Noted | Kenny (Qualcomm) provides comments. Pallab (Nokia) provides comments. LaeYoung (LGE) replies to Kenny (Qualcomm) and Pallab (Nokia). Jianning (Xiaomi) provides comment Marco (Huawei) comments LaeYoung (LGE) provides r01 and responds to Jianning (Xiaomi) and Marco (Huawei). Kenny (Qualcomm) provides comments to r01. Pallab (Nokia) comments or r01 ==== Revisions Deadline ==== LaeYoung (LGE) thinks that this CR can be NOTED. Pallab (Nokia) proposes to NOTE the CR ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2304996 | CR | Approval | 23.501 CR4450 (Rel-18, 'B'): Support QoS management for PIN | vivo | Rel-18 | r06 agreed. Revised to S2-2306180, merging S2-2304998 and S2-2304547. | Zhenhua (vivo) provides r01. Jianning (Xiaomi) provide comments Zhenhua (vivo) replies to Jianning (Xiaomi) Pallab (Nokia) comments and provides r02 Jianning (Xiaomi) provides comments Marco (Huawei) concern on the 'PEGC provide QOS parameter to 5GC'; merging with S2-2305131 to be considered; provide r03 Zhenhua (vivo) clarifies that no clash between 4996 and 5131, and provides r04 LaeYoung (LGE) has concern on using clause 4.15.6.3e of TS 23.502. Qian (Ericsson) provides comments. Zhenhua (vivo) provides r05. Kenny (Qualcomm) provides r06 based on r05. LaeYoung (LGE) comments. ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r06, but comments that some update is needed in the next meeting. Qian (Ericsson) can live with r06. Marco (Huawei) ok R06, objects r00,r01, r04 ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306180 | CR | Approval | 23.501 CR4450R1 (Rel-18, 'B'): Support QoS management for PIN | Vivo | Rel-18 | Revision of S2-2304996r06, merging S2-2304998 and S2-2304547. Approved | Agreed | |
| 9.3.2 | S2-2304997 | CR | Approval | 23.501 CR4451 (Rel-18, 'B'): UE 5GSM Core Network Capability handling for PIN | vivo | Rel-18 | Noted | Kenny (Qualcomm) provides comments. Pallab (Nokia) also thinks that the new indication from UE as proposed in the CR is not needed. Jianning (Xiaomi) provide comments Kenny (Qualcomm) provides comments . Marco (Huawei) agrees with NOK & QC Jianning (Xiaomi) response Kenny (Qualcomm) Pallab (Nokia) responds to Jianning (Xiaomi) Qian (Ericsson) also shares the view from Huawei, Nokia, Qualcomm. ==== Revisions Deadline ==== Kenny (Qualcomm) objects this CR . Pallab (Nokia) also proposes to NOTE the CR. Jianning (Xiaomi) replies to Qian (Ericsson) Marco (Huawei) objects this CR ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2305131 | CR | Approval | 23.501 CR4492 (Rel-18, 'B'): PIN communication definition | Huawei, Hisilicon | Rel-18 | CR Cover sheet error! r06 agreed. Revised to S2-2306181. | Zhenhua (vivo) comments and provides r01. Pallab (Nokia) provides r02. Marco (Huawei) comments and provide r03 LaeYoung (LGE) thinks that updating and adding terms can be progressed later if needed. Pallab (Nokia) comments on r03 Sudeep (Apple) comments on r03. Marco (Huawei) answer to questions and provide r04 Qian (Ericsson) comments on r04 LaeYoung (LGE) comments. Pallab (Nokia) provides r05 Kenny (Qualcomm) comments in indirect communication Marco (Huawei) replay to Kenny (Qualcomm) on indirect communication Marco (Huawei) provide r06 and ask to Pallab (Nokia) clarification in r05 Pallab (Nokia) responds to Marco (Huawei) ==== Revisions Deadline ==== Jianning (Xiaomi) provdes r07 LaeYoung (LGE) prefers to POSTPONE this CR or ENDORSING r06 is also fine for further work in May meeting. Jianning (Xiaomi) replies to LaeYoung (LGE), suggest to go with r07 LaeYoung (LGE) still prefers to POSTPONE this CR or ENDORSING r06 is also fine for further work in May meeting. Pallab (Nokia) is OK with r06. Objects to r07 Marco (Huawei) ok r06, object r07. And clearly we need to improve any CRs approved under PIN Jianning (Xiaomi) comments Jianning (Xiaomi) provide questions for clarification to Marco (Huawei) and Pallab (Nokia) Marco (Huawei) answers to Jianning (Xiaomi) Jianning (Xiaomi) provides further questions to Marco (Huawei) ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306181 | CR | Approval | 23.501 CR4492R1 (Rel-18, 'F'): PIN communication definition | Huawei, Hisilicon | Rel-18 | Revision of S2-2305131r06. Endorsed | Endorsed | |
| 9.3.2 | S2-2305241 | CR | Approval | 23.501 CR4535 (Rel-18, 'F'): Editorial change for the PIN | xiaomi | Rel-18 | r02 agreed. Revised to S2-2306182. | Zhenhua (vivo) provides r01. Qian (Ericsson) provides comments on r01. Zhenhua (vivo) provides r02. Jianning (Xiaomi) is ok with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.3.2 | S2-2306182 | CR | Approval | 23.501 CR4535R1 (Rel-18, 'F'): Editorial change for the PIN | Xiaomi | Rel-18 | Revision of S2-2305241r02. Approved | Agreed | |
| 9.3.2 | S2-2305347 | CR | Approval | 23.501 CR4557 (Rel-18, 'B'): PDU Session Establishment for PIN | Intel | Rel-18 | No revision marks shown! Noted | Kenny (Qualcomm) provides comments. Pallab (Nokia) provides comments and thinks the CR is not needed Marco (Huawei) agree with NOK , this CR is not needed. Qian (Ericsson) agrees with the previous comments that content in the CR is not related to SA2 . Kenny (Qualcomm) agrees with the previous comments that the changes are not needed. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.3.2 | - | - | - | 23.502 CRs | - | - | Docs:=0 | - | |
| 9.3.2 | - | - | - | Subscription and procedure related | - | - | Docs:=5 | - | |
| 9.3.2 | S2-2304178 | CR | Approval | 23.502 CR3881R1 (Rel-18, 'B'): PDU session control related PIN service support | Ericsson | Rel-18 | Revision of S2-2302316 from S2#155. Postponed | Zhenhua (vivo) comments. Pallab (Nokia) comments. Qian (Ericsson) responds to Pallab(Nokia) and Zhenhua (vivo). Zhenhua (vivo) replies to Qian (Ericsson). Qian (Ericsson) provides comments. Susan (Huawei) provides comments. Kenny (Qualcomm) comments. Susan (Huawei) doesn't agree to introduce an indication in the subscription data. Susan (Huawei) replies to Qian (Ericsson). Qian (Ericsson) replies to Zhenhua (vivo) Zhenhua (vivo) answers to Qian (Ericsson) Pallab (Nokia) supports views from Qian (Ericsson) and Kenny (Qualcomm) Zhenhua (vivo) replies to Pallab (Nokia) Pallab (Nokia) responds to Zhenhua (vivo) Susan (Huawei) asks questions to Pallab (Nokia) for clarification and objects to all versions of this CR, including r00. ==== Revisions Deadline ==== Kenny (Qualcomm) replies Susan (Huawei) question. Susan (Huawei) replies to Pallab (Nokia). Susan (Huawei) replies to Kenny (Qualcomm). Zhenhua (vivo) propose to note or postponed this CR for we need more discussion on the procedures and then determine how data structure serving the procedures Kenny (Qualcomm) replies to Susan (Huawei). ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2305004 | CR | Approval | 23.502 CR4093 (Rel-18, 'B'): Subscription data modification for PIN | vivo | Rel-18 | CR Cover sheet error! Postponed | Kenny (Qualcomm) provides comments. Pallab (Nokia) provides comments. Zhenhua (vivo) clarifies Pallab (Nokia) responds Zhenhua (vivo) and objects to the CR. Qian (Ericsson) provides comments. Marco (Huawei) comments Kenny (Qualcomm) comments Pallab (Nokia) shares exactly the same view as mentioned by Kenny (Qualcomm). Marco (huawei) furher comments Marco (Huawei) answers to Pallab (Nokia) ==== Revisions Deadline ==== Kenny (Qualcomm) replies Marco (Huawei) question. Zhenhua (vivo) ask clarification to Kenny (Qualcomm) Kenny (Qualcomm) replies Zhenhua (vivo) questions Kenny (Qualcomm) objects the CR, more discussion is required on the impact of subscription data. Zhenhua (vivo) replies to Kenny (Qualcomm) Zhenhua (vivo) propose to postponed this CR ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2305100 | CR | Approval | 23.502 CR4109 (Rel-18, 'B'): Definition of services for PIN support | Huawei, HiSilicon | Rel-18 | Postponed | Kenny (Qualcomm) provides comments. Pallab (Nokia) provides comments. Marco (Huawei) answer. Qian (Ericsson) provides comments. Pallab (Nokia) responds. Zhenhua (vivo) ask questions to Pallab (Nokia). Pallab (Nokia) responds to Zhenhua (vivo) Zhenhua (vivo) asks further question to Pallab (Nokia) marco (Huawei) answer to Pallab (Nokia). Zhenhua (vivo) kindly ask Pallab (Nokia) to provide concreate solution next meeting. Pallab (Nokia) responds to marco (Huawei) Pallab (Nokia) responds to Zhenhua (vivo). Zhenhua (vivo) replies to Pallab (Nokia) ==== Revisions Deadline ==== Kenny (Qualcomm) objects the CR, We have no agreement on the modification of 5G VN & GMC for PIN, whether a new NEF service is required. Zhenhua (vivo) propose to postponed the CR, ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2305005 | CR | Approval | 23.502 CR4094 (Rel-18, 'B'): UE Policy Association update for PIN | vivo | Rel-18 | CR Cover sheet error! Noted | Pallab (Nokia) provides comments. Kenny (Qualcomm) provides comments. Zhenhua (vivo) clarifies Pallab (Nokia) provides comments and objects to this CR. Marco (Huawei) provides comments. Qian (Ericsson) provides comments. Pallab (Nokia) responds to Marco (Huawei). Zhenhua (vivo) responds to Pallab (Nokia) Pallab (Nokia) responds to Zhenhua (vivo) ==== Revisions Deadline ==== Kenny (Qualcomm) comments the changes are not needed, object this CR Zhenhua (vivo) proposed to postponed this CR Marco (Huawei) proposes to postpone this CR ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2305003 | CR | Approval | 23.502 CR4092 (Rel-18, 'B'): PIN parameters configuration procedure | vivo | Rel-18 | CR Cover sheet error! Postponed | Pallab (Nokia) provides comments. Kenny (Qualcomm) provides comments. Zhenhua (vivo) clarifies and provides r01. Pallab (Nokia) comments on r01. Qian (Ericsson) provides comments. Marco (Huawei) comment Marco (Huawei) prefers to use a new NEW NEF dedicated services for PIN as in 5100, but the information exchange should be the same. ==== Revisions Deadline ==== Zhenhua (vivo) propose to postponed this CR Pallab (Nokia) also proposes to postpone this CR Marco (huawei) propose to postone this CR. We have no agreement on the modification of 5G VN & GMC for PIN, whether a new NEF service is required. ==== Comments Deadline ==== | Postponed |
| 9.3.2 | - | - | - | Others | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2305244 | CR | Approval | 23.502 CR4134 (Rel-18, 'B'): PIN capability exchange between UE and 5GC | xiaomi | Rel-18 | Postponed | Pallab (Nokia) provides comments Marco (Huawei) asks clarifications Kenny (Qualcomm) provides comments Jianning (Xiaomi) replies to Pallab (Nokia) Jianning (Xiaomi) replies to Marco (Huawei) and provides r01 Jianning (Xiaomi) replies to Kenny (Qualcomm) Pallab (Nokia) responds to Jianning (Xiaomi) Kenny (Qualcomm) provides comments and object the CR. Jianning (Xiaomi) response to Kenny (Qualcomm), the object reason doesn't make sense, because 1) it mixes UE application capability (e.g., installed PEGC app) with UE communication capability (e.g., handle the URSP with PIN ID). We can install the PEGC app on any smartphone, but we cannot make sure all the smartphone can handle the URSP with PIN ID. 2) 5GC cannot trust/use the UE application capabilities information provided by AF to replace the UE communication capability excahnge between UE and 5GC. ==== Revisions Deadline ==== Jianning (Xiaomi) request for CC#3 or CC#4 Qian (Ericsson) propose to postpone Jianning (Xiaomi) is ok to postpone this CR for further discussion. ==== Comments Deadline ==== | Postponed |
| 9.3.2 | S2-2305245 | CR | Approval | 23.502 CR4135 (Rel-18, 'B'): PIN policy delivery requested by UE | Xiaomi | Rel-18 | CR Cover sheet error!. Confirm Specification Number - CR states 23.501! Postponed | Pallab (Nokia) comments and provides r01 Marco (Huawei) shares Pallab(Nokia) comments Kenny (Qualcomm) provides comments and not OK with the original version and r01. Jianning (Xiaomi) responses to Kenny (Qualcomm) Jianning (Xiaomi) replies to Pallab (Nokia) and Marco (Huawei) Pallab (Nokia) responds to Jianning (Xiaomi) Kenny (Qualcomm) provides comments and object the CR. Jianning (Xiaomi) response to Kenny (Qualcomm), the object reason doesn't make sense, because 1) it mixes UE application capability (e.g., installed PEGC app) with UE communication capability (e.g., handle the URSP with PIN ID). We can install the PEGC app on any smartphone, but we cannot make sure all the smartphone can handle the URSP with PIN ID. 2) 5GC cannot trust/use the UE application capabilities information provided by AF to replace the UE communication capability excahnge between UE and 5GC. ==== Revisions Deadline ==== Jianning (Xiaomi) request for CC#3 or CC#4 if possible Marco (Huawei) propose to postpone CR Qian (Huawei) proposes also to postpone as commented on 5244 thread Jianning (Xiaomi) replies to Marco (Huawei), and ok to postpone to next meeting ==== Comments Deadline ==== | Postponed |
| 9.3.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=16 | - | |
| 9.3.2 | S2-2304176 | CR | Approval | 23.501 CR4225 (Rel-18, 'F'): PIN communication via different PEGCs | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305001 | CR | Approval | 23.501 CR4455 (Rel-18, 'B'): Way for multiple PINs share one PDU Session | vivo | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2304645 | CR | Approval | 23.501 CR4368 (Rel-18, 'C'): Clarification on the mapping between PIN and PDU session | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305000 | CR | Approval | 23.501 CR4454 (Rel-18, 'B'): Way for handling of one PIN multiple PDU Sessions | vivo | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305308 | CR | Approval | 23.501 CR4545 (Rel-18, 'C'): Update to remove the EN about PINs Sharing a PDU Session | InterDigital Inc. | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.3.2 | S2-2305242 | CR | Approval | 23.501 CR4536 (Rel-18, 'C'): Remove the EN for Non-3GPP delay budget | xiaomi | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2304994 | CR | Approval | 23.501 CR4448 (Rel-18, 'B'): PIN identifier | vivo | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305246 | CR | Approval | 23.501 CR4538 (Rel-18, 'B'): PIN identifier | Xiaomi | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2304995 | CR | Approval | 23.501 CR4449 (Rel-18, 'B'): Remove EN for PIN activation/deactivation | vivo | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2304360 | CR | Approval | 23.502 CR3993 (Rel-18, 'C'): Clarifying SMF behaviour for non-3GPP delay budget and non-3GPP QoS Assistance Information | Qualcomm | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305002 | CR | Approval | 23.502 CR4091 (Rel-18, 'B'): PDU Session Release for PIN | vivo | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.3.2 | S2-2305301 | CR | Approval | 23.502 CR4142 (Rel-18, 'B'): Clarification on Session Management Procedures for multiple PINs | Rel-18 | NOT HANDLED | |||
| 9.3.2 | S2-2304840 | CR | Approval | 23.503 CR1004 (Rel-18, 'F'): Clarification on URSP for PIN | LG Electronics | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2304930 | CR | Approval | 23.503 CR1011 (Rel-18, 'B'): URSP extension for PIN | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.3.2 | S2-2305302 | CR | Approval | 23.503 CR1034 (Rel-18, 'B'): Clarification on URSP rules for PIN and PDU Session association | Rel-18 | NOT HANDLED | |||
| 9.3.2 | S2-2305311 | CR | Approval | 23.503 CR1035 (Rel-18, 'C'): URSP Rule Update so that one PIN can use more than one PDU Session | InterDigital Inc. | Rel-18 | NOT HANDLED | ||
| 9.4.1 | - | - | - | Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) | - | - | Docs:=0 | - | |
| 9.4.2 | - | - | - | Phase 2 for UAS, UAV and UAM (UAS_Ph2) | - | - | Docs:=32 | - | |
| 9.4.2 | - | - | - | Incoming LS’s | - | - | Docs:=2 | - | |
| 9.4.2 | S2-2303950 | LS In | Action | LS from RAN WG2: Reply LS on PC5 based Detect and Avoid mechanism | RAN WG2 (R2-2302262) | Rel-18 | Noted | LaeYoung (LGE) thinks that this LS can be NOTED. | Noted |
| 9.4.2 | S2-2303992 | LS In | Information | LS from TSG RAN: Reply to LS to 3GPP on ECC request for standardisation support related to ECC Decision (22)07 on “harmonised framework on aerial UE usage in MFCN harmonised bands” | TSG RAN (RP-230804) | Rel-18 | Noted | LaeYoung (LGE) thinks that this LS can be NOTED. | Noted |
| 9.4.2 | - | - | - | Others | - | - | Docs:=30 | - | |
| 9.4.2 | S2-2304062 | CR | Approval | 23.256 CR0083 (Rel-18, 'F'): Corrections to definition of A2X versus direct C2 communications | QUALCOMM Europe Inc. - Italy | Rel-18 | Noted | LaeYoung (LGE) provides comments. Shabnam (Ericsson) provides comments that have concerns with the proposal, trying to better understand with additional questions Guanzhou (InterDigital) questions whether the proposed change is necessary. Stefano (Qualcomm) given the comments and disagreements, proposes to withdraw the paper. LaeYoung (LGE) supports to NOTE this CR. :) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.4.2 | S2-2304063 | CR | Approval | 23.256 CR0084 (Rel-18, 'F'): Corrections to Direct C2 authorization via UUAA procedure | QUALCOMM Europe Inc. - Italy | Rel-18 | r01 agreed. Revised to S2-2305578, merging S2-2304566 | Shabnam (Ericsson) provides comments that it is in conflict with document 04566 updating same clause and needs to be merged for easier handling Stefano (Qualcomm) is OK with a merger and provides R01 Ashok (Samsung) provides comments Stefano (Qualcomm) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305578 | CR | Approval | 23.256 CR0084R1 (Rel-18, 'F'): Corrections to Direct C2 authorization via UUAA procedure | Qualcomm Incorporated, Ericsson | Rel-18 | Revision of S2-2304063r01, merging S2-2304566. Approved | Agreed | |
| 9.4.2 | S2-2304064 | CR | Approval | 23.256 CR0085 (Rel-18, 'F'): Direct C2 authorization exceptions | QUALCOMM Europe Inc. - Italy | Rel-18 | r02 agreed. Revised to S2-2305579. | Shabnam (Ericsson) provides comments that will require update of the CR Guanzhou (InterDigital) asks questions for clarification. Stefano (Qualcomm) responds and provides R01. Guanzhou (InterDigital) provides R02. Stefano (Qualcomm) responds and has concerns on R02. Guanzhou (InterDigital) responds to Stefano (Qualcomm). Stefano (Qualcomm) responds and maintain concerns. Guanzhou (InterDigital) responds to Stefano (Qualcomm) and maintain concerns on r00/r01. Stefano (Qualcomm) replies and suggests looking at r03 in other thread. Stefano (Qualcomm) replies that this is the last meeting for the WID. We need strong technical justification to impose the limitations Interdigital is implying. ==== Revisions Deadline ==== Stefano (Qualcomm) comments. Guanzhou (InterDigital) responds to Stefano (Qualcomm).//resent to include the latest comment Stefano (Qualcomm) replies. Guanzhou (InterDigital) can only accept r02 and objects to all other versions. Stefano (Qualcomm) comments if 4347 cannot be accepted with changes of CC#3 we can accept r02 but would strongly prefer r01. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305579 | CR | Approval | 23.256 CR0085R1 (Rel-18, 'F'): Direct C2 authorization exceptions | Qualcomm Incorporated | Rel-18 | Revision of S2-2304064r02. Approved | Agreed | |
| 9.4.2 | S2-2304347 | CR | Approval | 23.256 CR0093 (Rel-18, 'F'): Clarification on UAV authorization by USS via Uu interface | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Shabnam (Ericsson) provides comments whether the change of the Clause title really needed, prefer to remove that change. Saubhagya (Nokia) asks questions on the possibility of a merger of 4064 into 4347 ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that since status of 04064 is unclear and for this I would prefer a revision that removes second change completely. Maybe we can take it to CC#3 as r01 and approve? Approving original version is not ok. Saubhagya (Nokia) requests to open the CR in CC#3, and proposes to approve r00 with the below changes; the link to the paper with the proposed change is provided in the email body 1. Revert the change in clause title for clause 5.4.3. 2. Added condition for 'UE not capable of 3gpp connection' at the beginning of clause 5.4.3 ('If the UAV is not capable of 3GPP network connection or is not in coverage of a PLMN, or if the PLMN does not support UUAA, Direct C2 Communication is authorized based on pre-configured policies in the UAV (e.g. at the application layer') 3. Moved paragraph 3 as a continuation of paragraph 2 in clause 5.4.3 Guanzhou (InterDigital) can't accept the proposed merge and don't think it should be brought to CC#3. Shabnam (Ericsson) provides comments that it should be r01 and not r00 and we can accept the revision. Stefano (Qualcomm) comments the changes proposed at CC#3 are acceptable. Saubhagya (Nokia) asks to consider the provided draft as r01 LaeYoung (LGE) thinks the newly added part to 5.4.3 looks overlap with S2-2304064. Stefano (Qualcomm) if 4064 r02 is approved, we do not need 4347r01. If 4347r01 is approved, we will consider 4064r02 merged into it. LaeYoung (LGE) asks how about the change in 5.4.1 in this CR? Guanzhou (InterDigital) repeats that we can't accept this draft or revision. Saubhagya (Nokia) Agrees with the proposal from Stefano (Qualcomm), if 4064 r02 is approved, mark 4347r00+draft changes. If 4347r00+draft changes is approved, consider 4064r02 to be merged. Saubhagya (Nokia) correcting the previous comment: Agrees with the proposal from Stefano (Qualcomm), if 4064 r02 is approved, mark 4347 as noted. If 4347r00+draft changes is approved, consider 4064r02 to be merged. ==== Comments Deadline ==== | Noted |
| 9.4.2 | S2-2304566 | CR | Approval | 23.256 CR0096 (Rel-18, 'B'): EPC based C2 authorization of direct C2 communication | Ericsson, LG Electronics | Rel-18 | Merged into S2-2305578 | Shabnam (Ericsson) provides comments that this CR is merged with 04063. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.4.2 | S2-2304065 | CR | Approval | 23.256 CR0086 (Rel-18, 'F'): Clarification of EN on inter-PLMN A2X | QUALCOMM Europe Inc. - Italy | Rel-18 | r01 agreed. Revised to S2-2305580. | Shabnam (Ericsson) provides comments as per offline Ericsson supports & co-sign this paper, asks one clarification to be made if same understanding Stefano (Qualcomm) provides R01 and adds Ericsson ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305580 | CR | Approval | 23.256 CR0086R1 (Rel-18, 'F'): Clarification of EN on inter-PLMN A2X | Qualcomm Incorporated, LG Electronics, Ericsson | Rel-18 | Revision of S2-2304065r01. Approved | Agreed | |
| 9.4.2 | S2-2305124 | CR | Approval | 23.256 CR0100 (Rel-18, 'F'): Clarification of support of A2X capability of UAV UE | Huawei, HiSilicon | Rel-18 | Postponed | Shabnam (Ericsson) provides comments on if the principle is fully correct? LaeYoung (LGE) provides comment regarding comment from Shabnam (Ericsson). Shabnam (Ericsson) comments about potentially restructuring A2X aspects better and further clarification LaeYoung (LGE) thinks that this CR can be POSTPONED at this stage. Runze (Huawei) replies to LaeYoung (LGE) and Shabnam (Ericsson). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.4.2 | S2-2304066 | CR | Approval | 23.256 CR0087 (Rel-18, 'F'): Corrections to authorization of A2X | QUALCOMM Europe Inc. - Italy | Rel-18 | r03 agreed. Revised to S2-2305581. | Shabnam (Ericsson) provides comments and requests clarification. Stefano (Qualcomm) provides comments. Guanzhou (InterDigital) provides r01. Stefano (Qualcomm) responds and has concerns on R01. Shabnam (Ericsson) provides r02 removing requirements for UUAA so it is consistent with what Stefano (QC) states and removes need to have specific PLMN requirements. Stefano (Qualcomm) provides r03. Could be OK with r02 but it is incomplete. ==== Revisions Deadline ==== Shabnam (Ericsson) ok with r03 Guanzhou (InterDigital) can live with r03. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305581 | CR | Approval | 23.256 CR0087R1 (Rel-18, 'F'): Corrections to authorization of A2X | Qualcomm Incorporated | Rel-18 | Revision of S2-2304066r03. Approved | Agreed | |
| 9.4.2 | S2-2304231 | CR | Approval | 23.256 CR0088 (Rel-18, 'F'): Clarification on differences when referring to TS 23.287 | LG Electronics | Rel-18 | Approved | Agreed | |
| 9.4.2 | S2-2304232 | CR | Approval | 23.501 CR4249 (Rel-18, 'B'): 5QI for A2X message delivery via MBS | LG Electronics | Rel-18 | Approved | Agreed | |
| 9.4.2 | S2-2304233 | CR | Approval | 23.256 CR0089 (Rel-18, 'B'): MBS support for Broadcast Remote ID | LG Electronics | Rel-18 | r02 agreed. Revised to S2-2305582, merging S2-2305123 | Shabnam (Ericsson) provides comments that we should significantly reduce the content and not repeat V2X MBS details and use references more. Also need to merge or use one to capture as other CR in 05123 proposes same function. Stefano (Qualcomm) agrees on using 4233 as basis but reducing the content. LaeYoung (LGE) responds to Shabnam (Ericsson) and Stefano (Qualcomm). LaeYoung (LGE) provides r01. Shabnam (Ericsson) is ok with r01, thanks Runze (Huawei) thanks LaeYoung (LGE) for merging 5123 in r01 and co-signs in r02. LaeYoung (LGE) thanks to Runze (Huawei) for co-sign and (of course) is OK with r02. ^__^ ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305582 | CR | Approval | 23.256 CR0089R1 (Rel-18, 'B'): MBS support for Broadcast Remote ID | LG Electronics, Huawei | Rel-18 | Revision of S2-2304233r02, merging S2-2305123. Approved | Agreed | |
| 9.4.2 | S2-2305123 | CR | Approval | 23.256 CR0099 (Rel-18, 'F'): Solution of MBS-based broadcast remote ID | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! Merged into S2-2305582 | Stefano (Qualcomm) questions for clarification Shabnam (Ericsson) provides comments that we have two sets of CRs for same and we need to use one moving forward, 04233 has too much and this one has too little. LaeYoung (LGE) proposes to use S2-2304233 and will update it per comments provided in that thread (i.e. reducing the contents). Amanda Xiang ( Futurewei ) supports to use S2-2304233 as baseline for MBS-based broadcast remote ID solution Shabnam (Ericsson) proposes this CR to be considered merged with 04233. Runze (Huawei) agreed this CR to be considered merged with 04233. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.4.2 | S2-2304242 | CR | Approval | 23.256 CR0090 (Rel-18, 'F'): Clarification on general concept related to PC5 based functionalities | LG Electronics | Rel-18 | Approved | Shabnam (Ericsson) provides comments that the functions are not complete such as use on MBS, is it intentional? Or should we add that as well? LaeYoung (LGE) answers to Shabnam (Ericsson) that other CR (S2-2304233: MBS support for Broadcast Remote ID) covers MBS in clause 4.1. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.4.2 | S2-2304345 | CR | Approval | 23.256 CR0091 (Rel-18, 'F'): Clarification on A2X Communication modes | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Shabnam (Ericsson) provides comments that the CR is going in the opposite direction than what is in 04062. This CR is our understanding of the original intent on the relation between Direct C2 and A2X. LaeYoung (LGE) has same understanding as Shabnam (Ericsson). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.4.2 | S2-2304346 | CR | Approval | 23.256 CR0092 (Rel-18, 'F'): Clarification on A2X Policy | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Shabnam (Ericsson) provides comments if this is really removing redundant texts or removing parameters? Saubhagya (Nokia) answers a question from Shabnam (Ericsson) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.4.2 | S2-2304348 | CR | Approval | 23.256 CR0094 (Rel-18, 'F'): Removal of cross-rat authorization | Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2305583. | LaeYoung (LGE) provides r01. Saubhagya (Nokia) responds to LaeYoung (LGE), provides r02. LaeYoung (LGE) is fine with r02. Shabnam (Ericsson) unclear if we are not going to keep aligned with V2X and my vague recollection was that cross RAT aspects were also related to dual connectivity support in EPS where NR as PC5 without being Uu possible and same here. Saubhagya (Nokia) provides clarification Ashok (Samsung) comments Saubhagya (Nokia) provides r03. LaeYoung (LGE) is fine with r03 and provide comments. ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that ok with r03, but believes the impact to RAN from CR cover sheet should be removed. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305583 | CR | Approval | 23.256 CR0094R1 (Rel-18, 'F'): Removal of cross-rat authorization | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304348r03. Approved | Agreed | |
| 9.4.2 | S2-2304349 | CR | Approval | 23.501 CR4277 (Rel-18, 'F'): A2X NF profile selection | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Ashok (Samsung) feels this CR is not needed Saubhagya (Nokia) clarifies the need for this CR to Ashok (Samsung) Shabnam (Ericsson) shares same view as this CR is not needed and currently A2X is part of UAS service as updated by other Nokia CR. Propose to NOTE the CR. Saubhagya (Nokia) provides clarification ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.4.2 | S2-2304565 | CR | Approval | 23.256 CR0095 (Rel-18, 'C'): Removal of UE requesting UE policies from PCF in REGISTRATION REQUEST | Ericsson, Qualcomm Inc., LG Electronics | Rel-18 | Approved | Agreed | |
| 9.4.2 | S2-2304567 | CR | Approval | 23.256 CR0097 (Rel-18, 'C'): Ground-based DAA for an area enhancements | Ericsson | Rel-18 | r04 agreed. Revised to S2-2305584. | Stefano (Qualcomm) questions for clarification LaeYoung (LGE) provides comments. Guanzhou (InterDigital) asks questions for clarification. Shabnam (Ericsson) provides comments and checking, will come back with revision. Shabnam (Ericsson) provides r01 rebasing to correct baseline and addressing the comments LaeYoung (LGE) provides comment on r01. Shabnam (Ericsson) thanks for the comments, r02 addresses them LaeYoung (LGE) is fine with r02. Guanzhou (InterDigital) provides r03. Shabnam (Ericsson) can't seem to find r03, can you please check? Guanzhou (InterDigital) confirms that r03 is uploaded. Shabnam (Ericsson) provides r04, correcting the steps and procedure figure to align with step 7 removal and converted that in a NOTE. Guanzhou (InterDigital) is OK with r04 ==== Revisions Deadline ==== LaeYoung (LGE) comments on r04 that the figure is not aligned with the step description. Guanzhou (InterDigital) suggests to use r03 as agreeable version + .Note 1 in r04. Shabnam (Ericsson) comments that r04 is fine, step 9 is not shown in the figure due to that it is out of scope of 3GPP, that is how it was from the beginning. If it is an issue for you, we take r04+ remove the number 9 from that description. Shabnam (Ericsson) r05 uploaded in CC#3 removing step number from the text, '9'. Shabnam (Ericsson) r06 uploaded in CC#3 ,the following editorial things: 1) remove 7 2) modify 8 and 9 to 7 and 8 respectively. 3) remove t on current step 9. LaeYoung (LGE) is OK with r04 (latest version before deadline) + the editorial changes listed by Shabnam (Ericsson) and thinks that we can approve r04, then these editorial changes can be made when cleaning-up. Guanzhou (InterDigital) OK to approve r04 as LaeYoung suggested.. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305584 | CR | Approval | 23.256 CR0097R1 (Rel-18, 'C'): Ground-based DAA for an area enhancements | Ericsson | Rel-18 | Revision of S2-2304567r04. Approved | Agreed | |
| 9.4.2 | S2-2304931 | CR | Approval | 23.503 CR1012 (Rel-18, 'B'): Provisioning of A2X policy to UE | Samsung, LG Electronics | Rel-18 | r03 agreed. Revised to S2-2305585. | Stefano (Qualcomm) provides comments Ashok (Samsung) provides r01 LaeYoung (LGE) provides r02 and comments. Mirko (Huawei) provides r03. ==== Revisions Deadline ==== LaeYoung (LGE) is OK with r03. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305585 | CR | Approval | 23.503 CR1012R1 (Rel-18, 'B'): Provisioning of A2X policy to UE | Samsung, LG Electronics | Rel-18 | Revision of S2-2304931r03. Approved | Agreed | |
| 9.4.2 | S2-2304934 | CR | Approval | 23.256 CR0098 (Rel-18, 'B'): N2 and Xn based HO for UAV | Samsung, LG Electronics | Rel-18 | r00 agreed. Revised to S2-2305586. | Saubhagya (Nokia) is not OK with r00, and provides comments Ashok (Samsung) responds to Saubhagya LaeYoung (LGE) supports the suggestion from Andy (VC) because the change is simple and straightforward. Ashok (Samsung) agrees with proposal from Andy (VC) Saubhagya (Nokia) agrees with the proposal from Andy (VC) György (Ericsson) comments that AI is wrong in the subject line. ==== Comments Deadline ==== | Revised |
| 9.4.2 | S2-2305586 | CR | Approval | 23.256 CR0098R1 (Rel-18, 'B'): N2 and Xn based HO for UAV | Samsung, LG Electronics | Rel-18 | Revision of S2-2304934r00. Approved | Agreed | |
| 9.5.1 | - | - | - | Study on Ranging based services and sidelink positioning (FS_Ranging_SL) | - | - | Docs:=0 | - | |
| 9.5.2 | - | - | - | Ranging based services and sidelink positioning (Ranging_SL) | - | - | Docs:=114 | - | |
| 9.5.2 | - | - | - | LS In & LS Out | - | - | Docs:=13 | - | |
| 9.5.2 | S2-2303949 | LS In | Action | LS from RAN WG2: Reply LS on RAN dependency for Ranging & Sidelink Positioning | RAN WG2 (R2-2302255) | Rel-18 | Noted | Noted | |
| 9.5.2 | S2-2303920 | LS In | Action | LS from SA WG3: Reply LS to LS on SL positioning groupcast and broadcast | SA WG3 (S3-230430) | Rel-18 | Revision of postponed S2-2302200 from S2#155. Response drafted in S2-2305281. Final response in S2-2305726 | Replied to | |
| 9.5.2 | S2-2305281 | LS OUT | Approval | [DRAFT] Reply LS to Reply LS to LS on SL positioning groupcast and broadcast | Xiaomi | Rel-18 | Response to S2-2303920. r00 agreed. Revised to S2-2305726. | Revised | |
| 9.5.2 | S2-2305726 | LS OUT | Approval | Reply LS to Reply LS to LS on SL positioning groupcast and broadcast | SA WG2 | Rel-18 | Revision of S2-2305281r00. Approved | Approved | |
| 9.5.2 | S2-2303952 | LS In | Action | LS from RAN WG2: LS to SA2 on Sidelink positioning procedure | RAN WG2 (R2-2302285) | Rel-18 | Responses drafted in S2-2304985, S2-2305287, S2-2305354. Final response in S2-2305735 | LiMeng (Huawei) asks for clarification. Lars (Sony) comments. Sherry (Xiaomi) comments. | Replied to |
| 9.5.2 | S2-2304985 | LS OUT | Approval | [DRAFT] Reply LS to SA WG2 on Sidelink positioning procedure | OPPO | Rel-18 | Response to S2-2303952. Merged into S2-2305735 | Hong (Qualcomm) comments and proposes to merge it with S2-2305287. Jingran(OPPO) replies to Hong (Qualcomm) and agree to merge S2-2304985 into S2-2305287 . ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305287 | LS OUT | Approval | [DRAFT] Reply LS to LS to SA WG2 on Sidelink positioning procedure | Xiaomi | Rel-18 | Response to S2-2303952. r00 agreed. CC#4: r11 agreed. Revised to S2-2305735, merging S2-2305354 and S2-2304985 | Sherry (Xiaomi) provides r01. Walter Dees (Philips) provides revision r02. Cai Simon (Nokia) provides r03 Sherry (Xiaomi) comments. Sherry (Xiaomi) provides r04. Sherry (Xiaomi) provides r05. Richard (Ericsson) provides question Sherry (Xiaomi) provides r06. ==== Revisions Deadline ==== Xiaoyan Shi (Intel) comments. Hong (Qualcomm) comments. Walter Dees (Philips) proposes revision r07 in DRAFTS folder. Sherry (Xiaomi) provides r08. Lars (Sony) provides r09. Hong (Qualcomm) provide r10. Lars (Sony) is ok with r10. Sherry (Xiaomi) provides r11. ==== Comments Deadline ==== Lars (Sony) is ok with r11. | Revised |
| 9.5.2 | S2-2305735 | LS OUT | Approval | Reply LS to LS to SA WG2 on Sidelink positioning procedure | SA WG2 | Rel-18 | Revision of S2-2305287r00, merging S2-2305354 and S2-2304985. CC#4: Use revision of S2-2305287r11. Approved | Approved | |
| 9.5.2 | S2-2305354 | LS OUT | Approval | [DRAFT] Reply LS of R2-2302285 | Nokia, Nokia Shanghai Bell | Rel-18 | Response to S2-2303952. Merged into S2-2305735 | Sherry (Xiaomi) proposes to merge this paper into 5287. Cai Simon (Nokia) agrees merge ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305276 | LS OUT | Approval | [DRAFT] LS on security aspects for Ranging/Sidelink Positioning | Xiaomi | Rel-18 | r00 agreed. Revised to S2-2305727. | Revised | |
| 9.5.2 | S2-2305727 | LS OUT | Approval | LS on security aspects for Ranging/Sidelink Positioning | SA WG2 | Rel-18 | Revision of S2-2305276r00. Approved | Approved | |
| 9.5.2 | S2-2305282 | LS OUT | Approval | [DRAFT] Reply LS on Authorization and Provisioning for Ranging/SL positioning service | Xiaomi | Rel-18 | Cannot find incoming LS! r00 agreed. Revised to S2-2305734. | Sherry (Xiaomi) clarifies that this is not a reply LS and requests to have a TDoc number for revision. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305734 | LS OUT | Approval | LS on Authorization and Provisioning for Ranging/SL positioning service | SA WG2 | Rel-18 | Revision of S2-2305282r00. Approved | Approved | |
| 9.5.2 | - | - | - | DP | - | - | Docs:=1 | - | |
| 9.5.2 | S2-2305125 | DISCUSSION | Agreement | Solution of ranging using assistant UE | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.5.2 | - | - | - | Editorial | - | - | Docs:=2 | - | |
| 9.5.2 | S2-2305275 | P-CR | Approval | 23.586: Editorial corrections and alignments | Xiaomi | Rel-18 | r00 agreed. Revised to S2-2305736. | Lars (Sony) comments. David (Samsung) comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305736 | P-CR | Approval | 23.586: Editorial corrections and alignments. | Xiaomi | Rel-18 | Revision of S2-2305275r00. Approved | Approved | |
| 9.5.2 | - | - | - | CR / pCR for Procedures and information flows | - | - | Docs:=47 | - | |
| 9.5.2 | S2-2304239 | P-CR | Approval | 23.586: Procedures for Service Authorization and Provisioning to UE | CATT | Rel-18 | r01 agreed. Revised to S2-2305737. Baseline | LiMeng (Huawei) provides r01. ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r01. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305737 | P-CR | Approval | 23.586: Procedures for Service Authorization and Provisioning to UE. | CATT, Huawei, HiSilicon | Rel-18 | Revision of S2-2304239r01. Approved | Approved | |
| 9.5.2 | S2-2305339 | P-CR | Approval | 23.586: TS23.586 Procedures for Service Authorization to NG-RAN | Intel | Rel-18 | r03 agreed. Revised to S2-2305738. Baseline | Deng Qiang (CATT) provides r01. LiMeng (Huawei) provides r02. Xiaoyan Shi (Intel) provides r03. ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r03. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305738 | P-CR | Approval | 23.586: TS 23.586: Procedures for Service Authorization to NG-RAN . | Intel, CATT, Huawei, HiSilicon | Rel-18 | Revision of S2-2305339r03. Approved | Approved | |
| 9.5.2 | S2-2304805 | P-CR | Approval | 23.586: Procedures for UE discovery | vivo | Rel-18 | r06 agreed. Revised to S2-2305739. Baseline | Zhang (Ericsson) provides comments Hong (Qualcomm) comments. Wen (vivo) replies and provides r01. Xiaoyan Shi (Intel) provides r01 and adds Intel as co-sign company. LiMeng (Huawei) comments to r02 that Application Code/Query Code are not needed. Walter Dees (Philips) provides r03. Guillaume (MediaTek Inc.) provides r04 Wen (vivo) provides r05. Deng Qiang (CATT) comments. Wen (vivo) replies and provide r06. Guillaume (MediaTek Inc.) comments ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r06 and requests co-source. Wen (vivo) replies. Zhang (Ericsson) provides comment for r06 Wen (vivo) replies to Zhang and suggests to delete the 'Role required info' from the group member discovery and replace 'mAssage by mEssage' in the figure on top of r06 ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305739 | P-CR | Approval | 23.586: TS 23.586: Procedures for UE discovery and selection. | Vivo, Intel, CATT, Ericsson | Rel-18 | Revision of S2-2304805r06. Approved | Approved | |
| 9.5.2 | S2-2304369 | P-CR | Approval | 23.586: Procedure MT-LR NW based UE positioning using SL positioning. | Sony | Rel-18 | r01 agreed. Revised to S2-2305740, merging S2-2304808. | Sherry (Xiaomi) provides r01. Lars (Sony) comments on r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305740 | P-CR | Approval | 23.586: Procedure MT-LR NW based UE positioning using SL positioning. | Sony | Rel-18 | Revision of S2-2304369r01, merging S2-2304808. Approved | Approved | |
| 9.5.2 | S2-2304808 | P-CR | Approval | 23.586: Procedures for NW triggered NW assisted SL Positioning of UE with NAS | vivo | Rel-18 | Merged into S2-2305740 Merge into S2-2305740? | Sherry (Xiaomi) proposes to merge this paper into 4369. Richard (Ericsson) provides comments Wen (vivo) replies to Richard ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304370 | P-CR | Approval | 23.586: Procedure MO-LR NW based UE positioning using SL positioning. | Sony | Rel-18 | r02 agreed. Revised to S2-2305742, merging S2-2305178 and S2-2304809 | Sherry (Xiaomi) provides r01. JungJe(Interdigital) comments and uploaded r02 Lars (Sony) ask for clarification JungJe(Interdigital) responses to Lars(Sony) Lars (Sony) responds to JungJe JungJe(Interdigital) responds to Lars (Sony) ==== Revisions Deadline ==== Hong (Qualcomm) asks for the clarification of the agreements. JungJe(Interdigital) propose to postpone to next meeting. Lars (Sony) is ok to postpone, but can live with r02 also. Sherry (Xiaomi) propose to agree r02 + updating the title to be 'Procedures for 5GC-MO-LR Network based SL Positioning for UE with NAS connection'. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305742 | P-CR | Approval | 23.586: Procedure MO-LR NW based UE positioning using SL positioning. | Sony | Rel-18 | Revision of S2-2304370r02, merging S2-2305178 and S2-2304809. Approved | Approved | |
| 9.5.2 | S2-2304809 | P-CR | Approval | 23.586: Procedures for UE triggered Network assisted SL Positioning with NAS | vivo | Rel-18 | Merged into S2-2305742 | Sherry (Xiaomi) proposes to merge this paper into 4370. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305178 | P-CR | Approval | 23.586: TS 23.586: Procedures for SL positioning for target UE with NAS connection involving 5GC NF | Interdigital | Rel-18 | Merged into S2-2305742 | Sherry (Xiaomi) proposes to merge this paper into 4370. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304371 | P-CR | Approval | 23.586: Procedure Deferred MT-LR UE positioning using SL positioning. | Sony | Rel-18 | Merged into S2-2305741 Merge into S2-2305741? | Richard (Ericsson) provides comments Lars (Sony) responds Richard (Ericsson) answers to Lars (Sony) Lars (Sony) responds to Richard with a question. Lars (Sony) responds to Richard (Ericsson) Hong (Qualcomm) comments. Xiaoyan Shi (Intel) provides comments and propose to use this contribution as baseline for deferred MT-LR Procedure Jung Je (Interdigital) responds to Hong and Richard Hong (Qualcomm) replies to JungJe. Jung Je (Interdigital) replies to Hong (Qualcomm) Wen (vivo) comments. Sherry (Xiaomi) proposes to merge this paper into S2-2304810 referring details to TS 23.273. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305008 | P-CR | Approval | 23.586: Updates and procedure for Network assisted SL positioning without NAS connection | Samsung | Rel-18 | Merged into S2-2305741 Merge into S2-2305741? | Richard (Ericsson) provides comments David (Samsung) provides r01, replies to comments. Lars (Sony) comments on r01 and r00. Xiaoyan Shi (Intel) comments. Hong (Qualcomm) commented and ask for one paper to consolidate on all the related proposals for TS 23.586. LiMeng (Huawei) suggests to consider the relationship with S2-2304813. David (Samsung) is OK to merge with the baseline papers for no NAS connection. Sherry (Xiaomi) proposes to merge this paper into 4810. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304810 | P-CR | Approval | 23.586: Procedures for SL positioning without NAS under NF involvement | vivo | Rel-18 | r07 agreed. Revised to S2-2305741, merging S2-2305179, S2-2304371 and S2-2305008 | Wen (vivo) provides r01. Sherry (Xiaomi) provides r02. Walter (Philips) provides r03. Wen (vivo) comments and provides r04. LiMeng (Huawei) provides r05. Lars (Sony) comments on r03, r04 and r05. Walter (Philips) responds to Lars (Sony). Wen (vivo) provides r06. Wen (vivo) responds to Lars (Sony) and Walter (Philips). Walter (Philips) provides r07. Wen (vivo) replies to Walter. Wen (vivo) provides r08 and states that r07 is based on 4635 and r08 is based on 5172 for final selection. Hong (Qualcomm) comments. Walter (Philips) provides r09. Wen(Philips) provides r10. ==== Revisions Deadline ==== Wen(vivo) suggests to add the following 2 ENs on top of r10: Editor's note: It is FFS if the SL positioning request is sent to each Located UE and what this request includes. Editor's note: It is FFS if the SL-MO-LR is sent by each Located UE. Richard(Ericsson) provides comment on r10, numbering is wrong in the text Wen(vivo) replies and further suggests to delete the first sep3the step number change: second 2->3;second 3->4, the 4->5, add the following 2 ENs mentioned before on top of 10: Editor's note: It is FFS if the SL positioning request is sent to each Located UE and what this request includes. Editor's note: It is FFS if the SL-MO-LR is sent by each Located UE. Walter (Philips) objects r08-r10. Now that we seem to have an agreement to move forward with using 4635 as a basis, we need to go with r07 which is the last one based on 4635. r08-r10 are based on 5172 which was not agreed. Wen (vivo) replies and is ok with r07. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305741 | P-CR | Approval | 23.586: TS 23.586: Procedures for SL positioning without NAS under 5GC NF involvement. | Vivo | Rel-18 | Revision of S2-2304810r07, merging S2-2305179, S2-2304371 and S2-2305008. Approved | Approved | |
| 9.5.2 | S2-2304812 | P-CR | Approval | 23.586: Procedures for SL positioning without NAS under no NF involvement | vivo | Rel-18 | Merged into S2-2305743. Merge into S2-2305743? | Richard (Ericsson) provides comments Wen (vivo) replies to Richard Sherry (Xiaomi) propose to merge this paper into 4510. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305179 | P-CR | Approval | 23.586: TS 23.586: Procedures for SL positioning for target UE without NAS connection involving 5GC NF | Interdigital | Rel-18 | Merged into S2-2305741 | Sherry (Xiaomi) proposes to merge this paper into 4810. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304510 | P-CR | Approval | 23.586: 23.586 Procedure of UE Positioning using Sidelink Positioning | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2305743, merging S2-2304812. | Sherry (Xiaomi) provides r01. LiMeng (Huawei) provides r02. Walter (Philips) provides r03. ==== Revisions Deadline ==== Hong (Qualcomm) comments regarding the title of the clause to be aligned with that in S2-2304505. Sherry (Xiaomi) proposes to agree r03+change the title of 6.X into 'Procedure of UE only Sidelink Positioning for Target UE'. Hong (Qualcomm) propose to agree r03+change the title of 6.X into 'Procedure of UE only Sidelink Positioning for Target UE using Located UE'. Sherry (Xiaomi) agrees with Hong's proposal. LiMeng (Huawei) agrees with Hong's proposal. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305743 | P-CR | Approval | 23.586: Procedure of UE Positioning using Sidelink Positioning. | Huawei, HiSilicon | Rel-18 | Revision of S2-2304510r03, merging S2-2304812. Approved | Approved | |
| 9.5.2 | S2-2304386 | P-CR | Approval | 23.586: Procedure for Ranging/SL Positioning service exposure though 5GC network. | Sony | Rel-18 | r06 agreed. Revised to S2-2305744, merging S2-2304819. | Sherry (Xiaomi) provides r01. Lars (Sony) provides r02. Sherry (Xiaomi) provides r02. Lars (Sony) Sherry the r02 you refer to is my r02. Hong (Qualcomm) comments on r02. Lars (Sony) responds to Hong (Qualcomm) Hong (Qualcomm) replies to Lars. Lars (Sony) responds to Hong. Lars (Sony) provides r03. Sherry (Xiaomi) provides r04. Lars (Sony) comments and provides r05. Wen (vivo) comments and provides r06. LiMeng (Huawei) confirms the co-signer, is fine with r05 and r06. ==== Revisions Deadline ==== Lars (Sony) is ok with both r05 and r06. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305744 | P-CR | Approval | 23.586: Procedure for Ranging/SL Positioning service exposure though 5GC network. | Sony, Huawei, HiSilicon, vivo | Rel-18 | Revision of S2-2304386r06, merging S2-2304819. Approved | Approved | |
| 9.5.2 | S2-2305177 | P-CR | Approval | 23.586: TS 23.586: Procedures for Service exposure to SL Positioning Client UE | Interdigital | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304819 | P-CR | Approval | 23.586: Procedures for Ranging service exposure to UE via 5GC | vivo | Rel-18 | Merged into S2-2305744 Merge into S2-2305744? | Wen (vivo) provides r01 based on the progress of the S2- S2-2304634 for the SL-MT-LR. Sherry (Xiaomi) proposes to merge this paper into 4386. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304549 | P-CR | Approval | 23.586: Procedure for service exposure to AF | Samsung | Rel-18 | r02 agreed. Revised to S2-2305745, merging S2-2304519 | Lars (Sony) comments. David (Samsung) replies to Sony. Lars (Sony) Is this tdoc merged into S2-2304634? Sherry (Xiaomi) comments. Sherry (Xiaomi) provides r01. LiMeng (Huawei) provides r02. David (Samsung) is OK with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305745 | P-CR | Approval | 23.586: Procedure for service exposure to AF. | Samsung | Rel-18 | Revision of S2-2304549r02, merging S2-2304519. Approved | Approved | |
| 9.5.2 | S2-2304509 | P-CR | Approval | 23.586: 23.586 Procedure for Ranging SL Positioning | Huawei, HiSilicon | Rel-18 | Merged into S2-2305747 | Sherry (Xiaomi) proposes to merge this paper into 5285. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304814 | P-CR | Approval | 23.586: Procedures for UE only operation | vivo | Rel-18 | Merged into S2-2305747 | Sherry (Xiaomi) proposes to merge this paper into 5285. Richard (Ericsson) provides r01 JungJe(Interdigital) comments ==== Revisions Deadline ==== Lars (Sony) is this merged into S2-2305285? Sherry (Xiaomi) proposes to merge this paper into S2-2305285. Wen (vivo) confirms that this paper is merged to 5285. ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305092 | P-CR | Approval | 23.586: Updates related to SL Positioning Server | Philips International B.V. | Rel-18 | r01 agreed. Revised to S2-2305746. | Walter Dees (Philips) provides r01 which removes change 2, since that change was merged with S2-2305289. Jung Je (Interdigital) comments Walter Dees (Philips) responds to Jung Je (Interdigital). Richard (Ericsson) provides comment Richard (Ericsson) provides more comments Walter Dees (Philips) responds to Richard (Ericsson). Richard (Ericsson) replays to Walter (Philips) Xiaoyan Shi (Intel) comments. Sherry (Xiaomi) proposes to merge the fourth change into 5285. Walter Dees (Philips) provides r02 which removes change 4, since that change was merged with S2-2305285. Richard (Ericsson) comments on r02 and providing r03 Walter (Philips) provides r04 ==== Revisions Deadline ==== Richard (Ericsson) fine with r04 ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305746 | P-CR | Approval | 23.586: Updates related to SL Positioning Server. | Philips International B.V. | Rel-18 | Revision of S2-2305078r04. Approved | Approved | |
| 9.5.2 | S2-2305190 | P-CR | Approval | 23.586: TS 23.586: Procedures for UE only operation and NW assisted operation | Interdigital | Rel-18 | Merged into S2-2305747 | Sherry (Xiaomi) proposes to merge this paper into 5285. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305285 | P-CR | Approval | 23.586: Procedures on UE-only Operation and Network-assisted Operation | Xiaomi | Rel-18 | r10 agreed. Revised to S2-2305747, merging S2-2305190, S2-2304814 and S2-2304509 | JungJe(Interdigital) comments. Hong (Qualcomm) comments. Lars (Sony) comments. Xiaoyan Shi (Intel) comments. Sherry (Xiaomi) provides r01&r02. Walter (Philips) provides r03. Sherry (Xiaomi) provides r04. LiMeng (Huawei) provides r05. Wen (vivo) provides r06. Walter (Philips) provides r07. Sherry (Xiaomi) provides r08. Walter (Philips) provides r09. Hong (Qualcomm) comments on r08. JungJe(Interdigital) provides r10. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305747 | P-CR | Approval | 23.586: Procedures on UE-only Operation and Network-assisted Operation. | Xiaomi, Philips International B.V., Interdigital | Rel-18 | Revision of S2-2305285r10, merging S2-2305190, S2-2304814 and S2-2304509. Approved | Approved | |
| 9.5.2 | S2-2304049 | CR | Approval | 23.273 CR0330 (Rel-18, 'B'): Introduce Sidelink Based positioning procedure | Ericsson | Rel-18 | Postponed | Sherry (Xiaomi) proposes to note this paper. Richard (Ericsson) disagrees with noting, this paper is not related to SL-MO-LR or SL-MT-LR Walter (Philips) proposes revision r01. Richard (Ericsson) fine with r01. ==== Revisions Deadline ==== Sherry (Xiaomi) comments. Hong (Qualcomm) proposes to POSTPONE the CR. Richard (Ericsson) answers to Hong Richard (Ericsson) answers to Sherry and explains concern related to ask noting Hong (Qualcomm) replies to Richard. Richard (replies) replies to Hong. ==== Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2304511 | CR | Approval | 23.273 CR0331 (Rel-18, 'B'): Procedure of Network based Sidelink Positioning | Huawei, HiSilicon | Rel-18 | Noted | Sherry (Xiaomi) proposes to note this paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.5.2 | S2-2304515 | CR | Approval | 23.273 CR0332 (Rel-18, 'B'): Procedure for MO-LR Ranging and Sidelink Positioning service exposure to UE | Huawei, HiSilicon | Rel-18 | Noted | Sherry (Xiaomi) proposes to note this paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.5.2 | S2-2304516 | CR | Approval | 23.273 CR0333 (Rel-18, 'B'): Procedure for MT-LR Ranging and sidelink positioning service exposure to Application server | Huawei, HiSilicon | Rel-18 | Merged into S2-2305748 | Sherry (Xiaomi) proposes to merge this paper into 4634. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304634 | CR | Approval | 23.273 CR0321R1 (Rel-18, 'B'): Support of MT-LR for Ranging and Sidelink Positioning | Qualcomm Incorporated | Rel-18 | Revision of S2-2303026 from S2#155. r12 agreed. Revised to S2-2305748, merging S2-2305173, S2-2304806 and S2-2304516 | Jung Je (Interdigital) provides comments Hong (Qualcomm) replies to JungJe. JungJe(Interdigital) replies to Hong(Qualcomm) Lars (Sony) provides some comments Sherry (Xiaomi) provides r01. David (Samsung) provides r02. Guillaume (MediaTek Inc.) provides r03 Xiaoyan Shi (Intel) comments. Walter (Philips) provides r04. Hong (Qualcomm) provides r05 and answers some questions/comments. Xiaoyan Shi (Intel) would request clarification on the concept 'Network assisted Ranging/SL Positioning procedures' before moving with any existing version. Hong (Qualcomm) replies to Xiaoyan. Xiaoyan Shi (Intel) replies to Hong. LiMeng (Huawei) comments to r00-r05. Hong (Qualcomm) replies to Xiaoyan and provides r06. Hong (Qualcomm) replies to LiMeng and provides r07. Richard (Ericsson) provides questions Cai Simon (Nokia) provides r08 Richard (Ericsson) replies to Richard. Richard (Ericsson) replies to Hong (Qualcomm) LiMeng (Huawei) provides r09 with including the EN proposed by Richard. David (Samsung) provides r10 restoring absolute location from the request description. Hong (Qualcomm) comments. Richard (Ericsson) provides r11 JungJe(Interdigital) provides r12. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305748 | CR | Approval | 23.273 CR0321R2 (Rel-18, 'B'): Support of MT-LR for Ranging and Sidelink Positioning | Qualcomm Incorporated | Rel-18 | Revision of S2-2304634r12, merging S2-2305173, S2-2304806 and S2-2304516. Approved | Agreed | |
| 9.5.2 | S2-2304806 | CR | Approval | 23.273 CR0342 (Rel-18, 'B'): SL-MO-LR procedure | vivo | Rel-18 | Merged into S2-2305748 MT-LR | Sherry (Xiaomi) proposes to merge this paper into 4634. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305173 | CR | Approval | 23.273 CR0371 (Rel-18, 'B'): SL-MT-LR Procedure | Interdigital | Rel-18 | Merged into S2-2305748 | Lars (Sony) comments. Jung Je (Interdigital) uploaded r01. Sherry (Xiaomi) proposes to merge this paper into 4634. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305353 | CR | Approval | 23.273 CR0375 (Rel-18, 'B'): Procedures of SL-MT-LR involving LMF | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Sherry (Xiaomi) proposes to note this paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.5.2 | S2-2304635 | CR | Approval | 23.273 CR0322R1 (Rel-18, 'B'): Ranging and Sidelink Positioning MO-LR procedure | Qualcomm Incorporated | Rel-18 | Revision of S2-2303028 from S2#155. r05 agreed. Revised to S2-2305749, merging S2-2304807 | Richard (Ericsson) provides comments Jung Je (Interdigital) provides comments Sherry (Xiaomi) provides r01. Lars (Sony) provides comments Lars (Sony) comments on new step 16. Walter Dees (Philips) provides revision r02. JungJe(Interdigital) provides revision r03. Xiaoyan Shi (Intel) provides comments. Hong (Qualcomm) provides r04. LiMeng (Huawei) has concerns on r00-r04. Hong (Qualcomm) comments. Lars (Sony) comments and objects to all revisions r00-r04. JungJe (Interdigital) comments LiMeng (Huawei) agrees Jung Je: using S2-2305172 could be a possible way forward. Richard (Ericsson) agrees Interdigital proposal Lars (Sony) comments on this way forward JungJe(Interdigital) responds Lars(Sony) Lars (Sony) responds to JungJe Lars (Sony) responds to Hong (Qualcomm). Hong (Qualcomm) provide r05 and replies to Lars. Lars (Sony) objects to r05. ==== Revisions Deadline ==== JungJe(Interdigital) comments r05. Hong (Qualcomm) replies to JungJe and Lars. Sherry (Xiaomi) comments. Lars (Sony) comments. Sherry (Xiaomi) comments and propose to postpone this paper. Lars (Sony) Propose way forward. Wen (vivo) suggests to take the Lars (Sony) Proposed way forward into account. Sherry (Xiaomi) agrees with the way fwd proposed by Lars. Sherry (Xiaomi) proposes to agree r05+ Add a general EN that states: Editor's Note: The solution needs to be updated to cover the following case: when the Target UE (UE1) has NAS connection and can communicate with the LMF and absolute positioning of UE1 is requested and location estimation is performed the LMF. The LMF can either retrieve the location of the Located UEs (UE2-n) from locally stored location, from the Located UE, or by requesting a new location estimation using the service offered by the GMLC. The solution could also include the options where the UE1 location estimation is performed by the UE1 with assistance by the LMF. And the following EN after step 10, 11, 13, 14 Editor's note: More details on how the LMF retrieve information and communicate with UE2-n is needed. ==== Comments Deadline ==== JungJe(Interdigital) ask to add Interdigital as cosource. Hong (Qualcomm) replies to JungJe. | Revised |
| 9.5.2 | S2-2305749 | CR | Approval | 23.273 CR0322R2 (Rel-18, 'B'): Ranging and Sidelink Positioning MO-LR procedure | Qualcomm Incorporated | Rel-18 | Revision of S2-2304635r05, merging S2-2304807. Approved | Agreed | |
| 9.5.2 | S2-2304807 | CR | Approval | 23.273 CR0343 (Rel-18, 'B'): SL-MO-LR procedure | vivo | Rel-18 | Merged into S2-2305749 | Sherry (Xiaomi) proposes to merge this paper into 4635. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305172 | CR | Approval | 23.273 CR0370 (Rel-18, 'B'): SL-MO-LR Procedure | Interdigital | Rel-18 | Noted | Lars (Sony) comments. Walter Dees (Philips) asks rapporteur to decide in which TS to document the detailed procedures involving the LMF, and provides comments on S2-2305172. Hong (Qualcomm) comments and request to decide a merging of all the MO-LR related contributions for TS 23.273. Jung Je (interdigital) responded to Walter(Philips) and Lars(Sony) and uploaded r01 Richard (Ericsson) proposes to consider this as baseline for SL-MO-LR Guillaume (MediaTek Inc.) comments Sherry (Xiaomi) proposes to merge this paper into 4635. Lars (Sony) provides r03. Richard (Ericsson) fine with r03 Walter (Philips) provides r04. Sherry (Xiaomi) comments. ==== Revisions Deadline ==== Hong (Qualcomm) OBJECTs all revision of the CR. ==== Comments Deadline ==== | Noted |
| 9.5.2 | - | - | - | CR / pCR for Terminology, Architecture model and concepts | - | - | Docs:=7 | - | |
| 9.5.2 | S2-2304048 | P-CR | Approval | 23.586: Defining LMF and DDNMF interaction | Ericsson | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304636 | P-CR | Approval | 23.586: Definition of Location Results in TS 23.586 | Qualcomm Incorporated | Rel-18 | r01 agreed. Revised to S2-2305750. | Lars (Sony) comments. Hong (Qualcomm) replies to Lars, and provides r01. Lars (Sony) responds to Hong. Hong (Qualcomm) replies to Lars. ==== Revisions Deadline ==== Lars (Sony) If we add a question in LSout to RAN, then I can live with r01. Hong (Qualcomm) agrees to add a question to the LS Out. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305750 | P-CR | Approval | 23.586: Definition of Location Results in TS 23.586. | Qualcomm Incorporated | Rel-18 | Revision of S2-2304636r01. Approved | Approved | |
| 9.5.2 | S2-2304952 | P-CR | Approval | 23.586: The capability of SL Positioning Server UE | INSPUR | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304637 | CR | Approval | 23.032 CR0022 (Rel-18, 'B'): New GAD Shapes for Ranging and Sidelink Positioning Location Results | Qualcomm Incorporated | Rel-18 | r01 agreed. Revised to S2-2305751. | Lars (Sony) comments. Hong (Qualcomm) provides r01. ==== Revisions Deadline ==== Lars (Sony) If we add a question in LSout to RAN, then I can live with r01. Hong (Qualcomm) agrees that we can add the question to the LS out. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305751 | CR | Approval | 23.032 CR0022R1 (Rel-18, 'B'): New GAD Shapes for Ranging and Sidelink Positioning Location Results | Qualcomm Incorporated | Rel-18 | Revision of S2-2304637r01. Approved | Agreed | |
| 9.5.2 | S2-2304517 | P-CR | Approval | 23.586: 23.586 Some corrections and clarifications | Huawei, HiSilicon | Rel-18 | Approved | Approved | |
| 9.5.2 | - | - | - | CR / pCR for High level functionalities | - | - | Docs:=26 | - | |
| 9.5.2 | S2-2305288 | P-CR | Approval | 23.586: Updates to Authorization and Provisioning for Ranging/SL positioning service | Xiaomi | Rel-18 | r01 agreed. Revised to S2-2305752. | LaeYoung (LGE) provides r01 merged with S2-2304243. ==== Revisions Deadline ==== Sherry (Xiaomi) is fine with r01. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305752 | P-CR | Approval | 23.586: Updates to Authorization and Provisioning for Ranging/SL positioning service. | Xiaomi | Rel-18 | Revision of S2-2305288r01. Approved | Approved | |
| 9.5.2 | S2-2305343 | P-CR | Approval | 23.586: TS23.586 Removing EN in UE Discovery & Selection | Intel | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304506 | P-CR | Approval | 23.586: 23.586 Update on Ranging Sidelink Positioning UE Discovery & Selection | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2305753. | Zhang (Ericsson) provides comments Hong (Qualcomm) provides r01. Wallter Dees (Philips) provides r02. Zhang (Ericsson) provides responses LiMeng (Huawei) provides r03 Deng Qiang (CATT) comments. LiMeng (Huawei) replies to Deng Qiang. Deng Qiang (CATT) replies to LiMeng (Huawei). LiMeng (Huawei) provides r04. Deng Qiang (CATT) provides r05. JungJe(Interdigital) comments ==== Revisions Deadline ==== Deng Qiang (CATT) replies to JungJe(Interdigital). Zhang (Ericsson) is OK with r05 and co-sign ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305753 | P-CR | Approval | 23.586: Update on Ranging/Sidelink Positioning UE Discovery & Selection. | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304506r05. Approved | Approved | |
| 9.5.2 | S2-2304816 | P-CR | Approval | 23.586: SL Positioning Server UE Discovery & Selection | vivo | Rel-18 | Merged into S2-2305755 | Walter Dees (Philips) thinks this proposal is covered by S2-2305289. Wen (vivo) replies to Walter Dees. Xiaoyan Shi (Intel) proposes to merge this contribution to S2-2305289. Wen(vivo) is ok to merge this contribution to S2-2305289. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304367 | P-CR | Approval | 23.586: Update to Located UE Discovery and Selection | Sony | Rel-18 | Merged into S2-2305754 | LiMeng (Huawei) asks questions. Lars (Sony) provides r01. Sherry (Xiaomi) proposes to merge this paper into 5286. Lars (Sony) ok to merge this paper into 5286. ==== Revisions Deadline ==== Hong (Qualcomm) objects original revision and r01. ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305286 | P-CR | Approval | 23.586: Updates to discovery and selection of Located UE | Xiaomi | Rel-18 | r06 agreed. Revised to S2-2305754, merging S2-2304367 | LiMeng (Huawei) provides r01. Sherry (Xiaomi) provides r02. Sherry (Xiaomi) provides r03. Walter (Philips) provides r04. Richard (Ericsson) provides comments Lars (Sony) comments on PRU JungJe(Interdigital) ask clarification. Sherry (Xiaomi) provides r05. JungJe(Interdigital) responds and provides r06. ==== Revisions Deadline ==== Hong (Qualcomm) only accepts r00 (i.e. the original version). Lars (Sony) Propose to agree r06 + Remove two bullets ' - Whether LOS path exists between candidate Located UE(s) and target UE - Stationary indication' + Remove Located UE may include a stationary indication during the discovery, which can be considered by the Target UE when selecting Located UE(s). + Remove NOTE1. Hong (Qualcomm) fine to agree r06 + Remove two bullets ' - Whether LOS path exists between candidate Located UE(s) and target UE - Stationary indication' + Remove Located UE may include a stationary indication during the discovery, which can be considered by the Target UE when selecting Located UE(s). + Remove NOTE1. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305754 | P-CR | Approval | 23.586: Updates to discovery and selection of Located UE. | Xiaomi | Rel-18 | Revision of S2-2305286r06, merging S2-2304367. Approved | Approved | |
| 9.5.2 | S2-2305289 | P-CR | Approval | 23.586: Discovery and selection of SL Positioning Server UE | Xiaomi | Rel-18 | r04 agreed. Revised to S2-2305755, merging S2-2304816 | Walter Dees (Philips) provides r01 with merged change 2 of S2-2305092. Xiaoyan Shi (Intel) provides comments.. Hong (Qualcomm) provides r02. JungJe(Interdigital) comments LiMeng (Huawei) comments Wen (vivo) comments Richard (Ericsson) provides comments Walter (Philips) provides r03. Hong (Qualcomm) replies to Walter. Walter (Philips) responds to Hong (Qualcomm). Wen (vivo) comments. LiMeng (Huawei) provides r04. Walter (Philips) provides r05. Richard (Ericsson) provides comment on r05, prefer r04. Sherry (Xiaomi) comments. ==== Revisions Deadline ==== Walter (Philips) proposes to go with r05. Richard (Ericsson) answers to Walter, and proposes go with r04 Walter (Philips) responds to Richard (Ericsson). Cai Simon (Nokia) prefers to go with r04 Sherry (Xiaomi) can accept both r04 and r05. ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305755 | P-CR | Approval | 23.586: Discovery and selection of SL Positioning Server UE. | Xiaomi, Philips International B.V. | Rel-18 | Revision of S2-2305289r04, merging S2-2304816. Approved | Approved | |
| 9.5.2 | S2-2304504 | P-CR | Approval | 23.586: 23.586 Update on Ranging/SL positioning handling | Huawei, HiSilicon | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304377 | P-CR | Approval | 23.586: Update the feature Network assisted SL positioning without NAS connection. | Sony | Rel-18 | Merged into S2-2305756 | LiMeng (Huawei) asks questions. Lars (Sony) responds to LiMeng and is ok to merge into S2-2304505. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304811 | P-CR | Approval | 23.586: SL positioning without NAS and 5GC NF involvement | vivo | Rel-18 | Merged into S2-2305756 | Richard (Ericsson) provides comments LiMeng (Huawei) suggests to merge this document into S2-2304505 Wen (vivo) is ok with LiMeng (Huawei)'s suggestion that merges this paper into 4505 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304505 | P-CR | Approval | 23.586: 23.586 Update on Network assisted Sidelink Positioning | Huawei, HiSilicon | Rel-18 | r07 agreed. Revised to S2-2305756, merging S2-2304813, S2-2304811 and S2-2304377 | Lider (ASUSTeK) comments LiMeng (Huawei) responds. Lars (Sony) Comments. Wen (vivo) comments. LiMeng (Huawei) responds and provide r01. Wen (vivo) comments on deferred MT-LR . Jungje(Interdigital) responded to Wen(vivo) Lider (ASUSTeK) comments on OoC understanding and r01. Xiaoyan Shi (Intel) comments. Hong (Qualcomm) comments. LiMeng (Huawei) responds and provides r02. Lider (ASUSTeK) is fine with r02. Lars (Sony) provides r03. Walter (Philips) comments LiMeng (Huawei) responds and provides r04 on top of r03. Hong (Qualcomm) comments and provides r05. LiMeng (Huawei) comments. Walter (Philips) provides revision r06. Hong (Qualcomm) provides r07. ==== Revisions Deadline ==== Magnus (Ericsson) can only accept r03, objects to r00-r02 LiMeng (Huawei) asks Magnus to confirm if the comments are to S2-2304505 (Ranging) Magnus H (Ericsson) withdraws my comments on this tdoc due to wrong thread. Sherry (Xiaomi) proposes to agree r07 + update title of clause 5.5.3 to be 'Network based SL positioning for UE without NAS connection' Sherry (Xiaomi) asks for clarification. Hong (Qualcomm) suggests agree r07 + updating title of 5.5.x to 'UE-only Operation for SL Positioning using Located UE' Sherry (Xiaomi) suggests agree r07 + updating title and clause number of 5.5.x to '5.X UE-only Operation for SL Positioning using Located UE' + updating title of clause 5.5.3 to be 'Network based SL positioning for UE without NAS connection' ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2305756 | P-CR | Approval | 23.586: Update on Network assisted Sidelink Positioning. | Huawei, HiSilicon, ASUSTeK | Rel-18 | Revision of S2-2304505r07, merging S2-2304813, S2-2304811 and S2-2304377. Approved | Approved | |
| 9.5.2 | S2-2304813 | P-CR | Approval | 23.586: EN resolve for NW assistant SL positioning without NAS | vivo | Rel-18 | Merged into S2-2305756 | LiMeng (Huawei) suggests to coordinate S2-2304813 and S2-2305008 to avoid confliction Wen (vivo) replies to Limeng ==== Revisions Deadline ==== LiMeng (Huawei) suggests to merge this document into 4505. Wen (vivo) is ok to merge this paper into 4505. ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2304378 | P-CR | Approval | 23.586: Update Ranging/SL Positioning service exposure though 5GC network. | Sony | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304518 | P-CR | Approval | 23.586: 23.586 Update of Ranging and Sidelink Positioning service exposure to UE | Huawei, HiSilicon | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2304519 | P-CR | Approval | 23.586: 23.586 Update of Ranging and Sidelink Positioning service exposure to AF | Huawei, HiSilicon | Rel-18 | Merged into S2-2305745 | David (Samsung) wonders if this paper can be merged into S2-2304549 LiMeng (Huawei) is fine to merge S2-2304519 into S2-2304549 Sherry (Xiaomi) provides r01. David (Samsung) observes that r01 is not a revision of this document and has been provided in the wrong thread, please provide it in S2-2304549. Sherry (Xiaomi) replies to David. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.5.2 | S2-2305284 | P-CR | Approval | 23.586: Support of Concurrent Ranging/Sidelink Positioning Requests | Xiaomi | Rel-18 | Approved | Approved | |
| 9.5.2 | S2-2305340 | CR | Approval | 23.501 CR4555 (Rel-18, 'B'): TS23.501 Support of SL Positioning | Intel | Rel-18 | Approved | Agreed | |
| 9.5.2 | S2-2304430 | CR | Approval | 23.502 CR3927R1 (Rel-18, 'B'): Ranging/Sidelink Positioning Subscription data in TS 23.502 | China Mobile | Rel-18 | Revision of S2-2302866 from S2#155. Covered by S2-2304508 | Lars (Sony) can this be merged into 4508? Aihua(CMCC) responses to Lars (Sony) and agrees to merge this CR into 4508. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.5.2 | S2-2304508 | CR | Approval | 23.502 CR4023 (Rel-18, 'B'): Ranging Sidelink Positioning Subscription data | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.5.2 | S2-2305278 | CR | Approval | 23.273 CR0318R1 (Rel-18, 'B'): Updates to LMF selection to support Ranging/Sidelink Positioning | Xiaomi | Rel-18 | Revision of S2-2302996 from S2#155. Approved | Agreed | |
| 9.5.2 | S2-2305280 | CR | Approval | 23.503 CR0930R1 (Rel-18, 'B'): Updates to support Ranging/Sidelink Positioning | Xiaomi | Rel-18 | Revision of S2-2302998 from S2#155. Approved | Agreed | |
| 9.5.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=18 | - | |
| 9.5.2 | S2-2304512 | P-CR | Approval | 23.586: 23.586, Procedures for Service Authorisation and Provisioning to UE | Huawei, HiSilicon | Rel-18 | Merge into S2-2304239 | NOT HANDLED | |
| 9.5.2 | S2-2305338 | P-CR | Approval | 23.586: TS23.586 Procedures for Service Authorization and Provisioning to UE | Intel | Rel-18 | Merge into S2-2304239 | NOT HANDLED | |
| 9.5.2 | S2-2304240 | P-CR | Approval | 23.586: Procedures for Service Authorization and Provisioning to NG-RAN | CATT | Rel-18 | Merge into S2-2305339 | NOT HANDLED | |
| 9.5.2 | S2-2304513 | P-CR | Approval | 23.586: 23.586, Procedures for Service Authorisation and Provisioning to RAN | Huawei, HiSilicon | Rel-18 | Merge into S2-2305339 | NOT HANDLED | |
| 9.5.2 | S2-2304241 | P-CR | Approval | 23.586: Procedures for UE Discovery | CATT | Rel-18 | Merge into S2-2304805 | NOT HANDLED | |
| 9.5.2 | S2-2304984 | P-CR | Approval | 23.586: KI#3, Ranging/SL Positioning Discovery | OPPO | Rel-18 | Merge into S2-2304805 | NOT HANDLED | |
| 9.5.2 | S2-2305342 | P-CR | Approval | 23.586: TS23.586 Procedures for UE Discovery | Intel | Rel-18 | Merge into S2-2304805 | NOT HANDLED | |
| 9.5.2 | S2-2304514 | P-CR | Approval | 23.586: 23.586 Procedure for Ranging and Sidelink Positioning service exposure to UE | Huawei, HiSilicon | Rel-18 | Merge into S2-2305177 | NOT HANDLED | |
| 9.5.2 | S2-2304818 | P-CR | Approval | 23.586: Procedures for Ranging service exposure to UE via PC5 | vivo | Rel-18 | Merge into S2-2305177 | NOT HANDLED | |
| 9.5.2 | S2-2304953 | P-CR | Approval | 23.586: The client triggering Relative Positioning | INSPUR | Rel-18 | Category F | NOT HANDLED | |
| 9.5.2 | S2-2305277 | P-CR | Approval | 23.586: Updates to LMF functionalities | Xiaomi | Rel-18 | Category F | NOT HANDLED | |
| 9.5.2 | S2-2304243 | P-CR | Approval | 23.586: Updates to clause 5.1 | LG Electronics | Rel-18 | Category F, can be merged into S2-2305288 | NOT HANDLED | |
| 9.5.2 | S2-2304817 | P-CR | Approval | 23.586: Updates to subscription for RangingSL Positioning | vivo | Rel-18 | Category F | NOT HANDLED | |
| 9.5.2 | S2-2304815 | P-CR | Approval | 23.586: QoS handling clarification | vivo | Rel-18 | Category F | NOT HANDLED | |
| 9.5.2 | S2-2305283 | P-CR | Approval | 23.586: Updates to Handling of Ranging/SL Positioning QoS | Xiaomi | Rel-18 | Category F | NOT HANDLED | |
| 9.5.2 | S2-2304507 | CR | Approval | 23.501 CR4334 (Rel-18, 'B'): Ranging SL Positioning Architecture | Huawei, HiSilicon | Rel-18 | Merge into S2-2305340 | NOT HANDLED | |
| 9.5.2 | S2-2305341 | CR | Approval | 23.502 CR4150 (Rel-18, 'B'): TS23.502 Ranging_Sidelink Positioning Subscription data | Intel | Rel-18 | Merge into S2-2304508 | NOT HANDLED | |
| 9.5.2 | S2-2305279 | CR | Approval | 23.273 CR0319R1 (Rel-18, 'B'): Updates to LMF service to support Ranging/Sidelink Positioning | Xiaomi | Rel-18 | Revision of S2-2302997 from S2#155 Can be postponed | NOT HANDLED | |
| 9.6.1 | - | - | - | Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) | - | - | Docs:=0 | - | |
| 9.6.2 | - | - | - | 5GC LoCation Services Phase 3 (eLCS_Ph3) | - | - | Docs:=65 | - | |
| 9.6.2 | - | - | - | LS In | - | - | Docs:=5 | - | |
| 9.6.2 | S2-2303928 | LS In | Action | LS from CT WG1: Reply LS on UE event reporting over a user plane connection to LCS client or AF | CT WG1 (C1-231128) | Rel-18 | Noted | Leo (Deutsche Telekom) proposes to NOTE the LS, as there is no action needed by SA2. | Noted |
| 9.6.2 | S2-2303929 | LS In | Action | LS from CT WG1: LS on LPP message and supplementary service event report over a user plane connection between UE and LMF | CT WG1 (C1-231129) | Rel-18 | Noted | Leo (Deutsche Telekom) proposes to NOTE the LS, as there is no action needed by SA2. | Noted |
| 9.6.2 | S2-2303944 | LS In | Action | LS from RAN WG1: LS reply on the requirement for LPHAP | RAN WG1 (R1-2302074) | Rel-18 | Noted | Scott (Inspur) provides comments Runze (Huawei) replies to Scott (Inspur). Ming (CATT) suggests to Note this LS In. Runze (Huawei) supports Ming (CATT). | Noted |
| 9.6.2 | S2-2303945 | LS In | Action | LS from RAN WG1: LS Reply on PRU Procedures | RAN WG1 (R1-2302146) | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2303951 | LS In | Action | LS from RAN WG2: Reply LS to SA2 on satellite access for PRUs | RAN WG2 (R2-2302270) | Rel-18 | Noted | Noted | |
| 9.6.2 | - | - | - | User Plane Positioning | - | - | Docs:=3 | - | |
| 9.6.2 | S2-2305114 | CR | Approval | 23.273 CR0364 (Rel-18, 'C'): Resolve the EN on the session break out for local LMF service | OPPO | Rel-18 | Noted | Yaxin (OPPO) provides r01 merging S2-2304857. Guanglei (Huawei) provides r02. Cai Simon (Nokia) comments Guanglei (Huawei) replies Yaxin (OPPO) provides r03 and replies to Cai Simon (Nokia). Guanglei (Huawei) comments on r03 Yaxin (OPPO) replies to Guanglei (Huawei). Guanglei (Huawei) replies to Yaxin Yaxin (OPPO) provides r04 and replies. Cai Simon (Nokia) asks further question Cai Simon (Nokia) comments to Guanglei (Huawei) Guanglei (Huawei) further replies Guanglei (Huawei) can live with r04 Yaxin (OPPO) replies to Cai Simon (Nokia). Cai Simon (Nokia) comments the reply not consistent with CR Cai Simon (Nokia) clarifies no need for option C and update to option B Guanglei (Huawei) further replies to Simon. Guanglei (Huawei) replies to Simon. Yaxin (OPPO) provides r05 and replies. Yaxin (OPPO) further reply to Cai Simon (Nokia). Guanglei (Huawei) comments on r05 Guanglei (Huawei) provides r06 Yaxin (OPPO) provides r07. Guanglei (Huawei) provides r09 Cai Simon (Nokia) hold objection to local LMF interface to PCF and R18 scope change Cai Simon (Nokia) provides r08 Yaxin (OPPO) can live with r09 or just postpone this CR. ==== Revisions Deadline ==== Guanglei (Huawei) proposes to approve r09, as it does not touch controversial issues Yaxin (OPPO) disagrees with Cai Simon (Nokia) and clarifies. Cai Simon (Nokia) proposes r08 and clarifies Richard (Ericsson) objects r08 and supports r06 Cai Simon (Nokia) accepts only r08 and objects all other revisions Guanglei (Huawei) objects r08, only ok with r06 or r09. Cai Simon (Nokia) proposes to NOTE the CR ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2304047 | CR | Approval | 23.273 CR0329 (Rel-18, 'B'): Adding Positioning Procedure over LCS-UP | Ericsson | Rel-18 | Noted | Stephen (Qualcomm) provides comments Cai Simon (Nokia) claims the CR is not compatible to 37.355 Richard (Ericsson) answers to Cai (Nokia) and Stephen (Qualcomm) Scott (Inspur) comments Richard (Ericsson) answers to Scott (Inspur) Richard (Ericsson) provides r01 Cai Simon (Nokia) comments Richard (Ericsson) answers to Cai Simon (Nokia) Richard (Ericsson) provided r02 and answers to Cai Simon (Nokia) Cai Simon (Nokia) comments r02 Richard (Ericsson) asks from Simon (Nokia) more clarification Yunjing (CATT) provides r03. Richard (Ericsson) provides comments on r03. ==== Revisions Deadline ==== Guanglei (Huawei) proposes to approve r02, objects r03, or postpone the CR, Stephen (Qualcomm) also prefers r02 and not r03 Cai Simon (Nokia) comments and proposes either NOTE or put to appendix Richard (Ericsson) proposes to accept r02 Richard (Ericsson) answers to Simon (Nokia) Cai Simon (Nokia) kindly reminds non of compatibility issues clarified Richard (Ericsson) disagrees with non-compatibility issues Yunjing (CATT) can accept r02. Cai Simon (Nokia) objects to all revisions Richard (Ericsson) disagrees with the reason of objection, still proposes to accept r02. Cai Simon (Nokia) insists objection Richard (Ericsson) still disagrees with the reason of objection Cai Simon (Nokia) suggests the way forward next meeting Richard (Ericsson) reacts on comments from Simon (Nokia) Cai Simon (Nokia) keeps objection and clarifies ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2305075 | CR | Approval | 23.273 CR0362 (Rel-18, 'F'): Update the user plane positioning to exclude the support of regulatory service | CATT | Rel-18 | Postponed | Richard (Ericsson) provides comments Cai Simon (Nokia) shows the CR not consistent with legacy regulatory documents Scott (Inspur) comments Guanglei (Huawei) comments Yunjing (CATT) provides r01. ==== Revisions Deadline ==== Cai Simon (Nokia) proposes to postpone the CR ==== Comments Deadline ==== | Postponed |
| 9.6.2 | - | - | - | NWDAF | - | - | Docs:=5 | - | |
| 9.6.2 | S2-2304670 | CR | Approval | 23.273 CR0337 (Rel-18, 'B'): Clarifications on NWDAF assisting LCS | vivo | Rel-18 | r04 agreed. Revised to S2-2305587. | Runze (Huawei) comments Amy (vivo) provides r01 and clarifies Cai Simon (Nokia) comments Amy (vivo) provides r02 and replies to Simon (Nokia) Richard (Ericsson) provides comment on r02 Amy (vivo) replies to Richard (Ericsson) Runze (Huawei) agrees with Richard (Ericsson), and propose not to add the EN. Amy (vivo) emphasizes the reply to Richard (Ericsson) to Runze (Huawei) about the EN Richard (Ericsson) answers to Amy Amy (vivo) thanks Richard (Ericsson) support on EN and provides r03 to fix the suggestion Runze (Huawei) replies to Amy (vivo) and provides r04. Amy (vivo) replies to Runze (Huawei) Runze (Huawei) replies to Amy (vivo). ==== Revisions Deadline ==== Amy (vivo) is ok with r04. Runze (Huawei) thanks Amy and proposes to agree r04. ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305587 | CR | Approval | 23.273 CR0337R1 (Rel-18, 'B'): Clarifications on NWDAF assisting LCS | Vivo | Rel-18 | Revision of S2-2304670r04. Approved | Agreed | |
| 9.6.2 | S2-2304671 | CR | Approval | 23.273 CR0338 (Rel-18, 'B'): Location verification for satellite access assisted by NWDAF analytics | vivo, Samsung, Nokia, Nokia Shanghai Bell | Rel-18 | r09 agreed. Revised to S2-2305588, merging S2-2305120 | Runze (Huawei) comments Scott (Inspur) comments Runze (Huawei) replies to Scott (Inspur) Runze (Huawei) replies to David (Samsung). Cai Simon (Nokia) comments David (Samsung) thanks Runze for spotting the missing tags in previous email, makes a proposal for a revision based on the discussion Amy (vivo) merges 5120 and provides r01 based on the interesting discussion David (Samsung) observes that r01 does not show changes over changes and does not follow the discussion below Amy (vivo) provides r02 and replies to David (Samsung) about r01 Amy (vivo) apologies for empty r02 below and emphasizes it here David (Samsung) thanks Amy and provides r03 based on r02 Runze (Huawei)provides r04. Runze (Huawei)provides weblink of r04. Cai Simon (Nokia) provides r05 Amy (vivo) objects r04 and r05 and provides r06. David (Samsung) provides r07. Cai Simon (Nokia) objects to local LMF interface to PCF and provides r08 Runze (Huawei) provides r08. David (Samsung) is OK with r08. Cai Simon (Nokia) provide r09 Amy (vivo) is OK with r08 and r09 ==== Revisions Deadline ==== Cai Simon (Nokia) accepts r09 Runze (Huawei) is ok with r09 ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305588 | CR | Approval | 23.273 CR0338R1 (Rel-18, 'B'): LCS services assisted by NWDAF analytics | Vivo, Samsung, Nokia, Nokia Shanghai Bell, Huawei | Rel-18 | Revision of S2-2304671r09, merging S2-2305120. Approved | Agreed | |
| 9.6.2 | S2-2305120 | CR | Approval | 23.273 CR0366 (Rel-18, 'F'): Procedures for interaction with NWDAF | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! Merged into S2-2305588 | Cai Simon (Nokia) comments David (Samsung) suggests to merge this document into S2-2304671 where the discussion on interactions with NWDAF is taking place ==== Revisions Deadline ==== Runze (Huawei) agrees with David (Samsung) this paper can be merged into 4671. ==== Comments Deadline ==== | Merged |
| 9.6.2 | - | - | - | GNSS | - | - | Docs:=2 | - | |
| 9.6.2 | S2-2304859 | CR | Approval | 23.273 CR0346 (Rel-18, 'F'): LMF service operation and procedure for GNSS assistance data transfer | Huawei, HiSilicon | Rel-18 | Postponed | Yunjing (CATT) asks questions for clarification. Guanglei (Huawei) replies to Yunjing Cai Simon (Nokia) comments based on questions and reply Richard (Ericsson) provides comments Guanglei (Huawei) further replies Guanglei (Huawei) replies to Richard. Cai Simon (Nokia) clarifies another misunderstanding of the CR Guanglei (Huawei) further replies to Simon. Guanglei (Huawei) further clarification. Guanglei (Huawei) further clarifications and provides r01. Cai Simon (Nokia) comments r01 Guanglei (Huawei) further clarifications... Guanglei (Huawei) further responses. Guanglei (Huawei) further responses and provides r02. Guanglei (Huawei) clarifies to Richard.. ==== Revisions Deadline ==== Richard (Ericsson) proposes to postpone paper and discuss on the next meeting if this function is required Guanglei (Huawei) understands the concern and is fine to postpone. ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2305121 | CR | Approval | 23.273 CR0367 (Rel-18, 'F'): Procedure update for multiple set of GNSS assistance data broadcast | Huawei, HiSilicon | Rel-18 | Noted | Stephen (Qualcomm) provides comments Runze(Huawei) replies to Stephen (Qualcomm). ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note the CR Runze (Huawei) hope Stephen (Qualcomm) to withdraw the objection as no technical issue with the CR. ==== Comments Deadline ==== | Noted |
| 9.6.2 | - | - | - | Unaware Positioning | - | - | Docs:=2 | - | |
| 9.6.2 | S2-2304949 | LS OUT | Approval | [DRAFT] LS on requirements of UE unaware positioning | INSPUR | Rel-18 | Noted | Stephen (Qualcomm) provides comments Runze (Huawei) share the same view as Stephen (Qualcomm). Scott(Inspur) replies to Runze(Huawei) and Stephen (Qualcomm). Runze (Huawei) replies to Scott (Inspur). ==== Revisions Deadline ==== Scott (Inspur) replies to Runze (Huawei). Yunjing (CATT) comments. Runze (Huawei) objects to this paper. Scott (Inspur) replies to Runze(Huawei) and Yunjing(CATT). Stephen (Qualcomm) also agrees the LS should not be sent (thus to be noted) ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2304951 | CR | Approval | 23.273 CR0353 (Rel-18, 'F'): Supporting UE/User unaware positioning | Inspur | Rel-18 | Noted | Runze (Huawei) provides comments. ==== Revisions Deadline ==== Runze (Huawei) objects to this paper, same reason as for 4949. ==== Comments Deadline ==== | Noted |
| 9.6.2 | - | - | - | PRU | - | - | Docs:=14 | - | |
| 9.6.2 | S2-2304861 | DISCUSSION | Discussion | Discussion on PRU existence indication | Huawei, HiSilicon | Rel-18 | Noted | Scott (Inspur) comments and request for clarification. Guanglei (Huawei) replies Scott (Inspur) replies Guanglei (Huawei) replies. Scott(Inspur) replies. Guanglei (Huawei) replies to Scott. Scott(Inspur) replies to guanglei and all. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2304862 | CR | Approval | 23.273 CR0348 (Rel-18, 'F'): Removal of EN of PRU existence indication | Huawei, HiSilicon | Rel-18 | Merged into S2-2305589 | Richard (Ericsson) proposes to merge this into 2304045 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.6.2 | S2-2304045 | CR | Approval | 23.273 CR0328 (Rel-18, 'B'): Update PRU s NRF impact | Ericsson | Rel-18 | r02 agreed. Revised to S2-2305589, merging S2-2304862 | Stephen (Qualcomm) provides comments Scott (Inspur) provides comments Guanglei (Huawei) also comments Richard (Ericsson) answers to Scott (Inspur) and to Stephen (Qualcomm) Scott (Inspur) answers to Richard(Ericsson) and all Cai Simon (Nokia) comments on the term usage Richard (Ericsson) provides r01 and answers to Simon Guanglei (Huawei) provides r02 Cai Simon (Nokia) clarifies Scott (Inspur) comments Richard (Ericsson) answers to Simon and to Scott Cai Simon (Nokia) emphasizes document consistency Richard (Ericsson) specification can use better term than TR, and TS does not refer to TR ==== Revisions Deadline ==== Scott (Inspur) replies to Richard (Ericsson) and propose to postpone the paper and insist on objection. Guanglei (Huawei) comments and proposes going with r02 Scott (Inspur) comments and propose to discuss further in the next meeting. Guanglei (Huawei) replies to Scott and clarify why we can go with r02. Scott(Inspur) replies to Guanglei(Huawei) and object r02. Richard (Ericsson) strongly proposes to go with r02, without this CT Groups starts to implement PRU wrongly Guanglei (Huawei) comment: based on offline discussion, we suggest Inspur to reconsider the positioning, can we approve r02? Scott (Inspur) comment. Richard (Ericsson) answer to Scott Guanglei (Huawei) agrees with Richard and proposes to go with r02. ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305589 | CR | Approval | 23.273 CR0328R1 (Rel-18, 'B'): Update PRU s NRF impact | Ericsson | Rel-18 | Revision of S2-2304045r02, merging S2-2304862. Approved | Agreed | |
| 9.6.2 | S2-2304046 | DISCUSSION | Discussion | Update PRU s NRF impact | Ericsson | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2305122 | CR | Approval | 23.273 CR0368 (Rel-18, 'F'): Clarification of PRU UE using NR satellite access | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305590. | Stephen (Qualcomm) provides comments Scott (Inspur) provides comments Runze (Huawei) replies. Runze (Huawei) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305590 | CR | Approval | 23.273 CR0368R1 (Rel-18, 'F'): Clarification of PRU UE using NR satellite access | Huawei, HiSilicon | Rel-18 | Revision of S2-2305122r01. Approved | Agreed | |
| 9.6.2 | S2-2305065 | DISCUSSION | Discussion | Discussion on Query of Serving LMF of PRU | CATT | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2305352 | CR | Approval | 23.273 CR0374 (Rel-18, 'B'): Updates to Procedures applicable to PRU | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Postponed | Cai Simon (Nokia) provide r01 to correct the cover page Stephen (Qualcomm) provides comments Yaxin (OPPO) provides comments. Cai Simon (Nokia) clarifies and provides r02 ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note the CR ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2305127 | CR | Approval | 23.273 CR0369 (Rel-18, 'F'): Further clarification on the support of PRUs and related procedures | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305591. CC#4: Postponed | Stephen (Qualcomm) provides comments Runze (Huawei) replies to Stephen (Qualcomm). Cai Simon (Nokia) asks questions Scott (Inspur) comments Runze (Huawei) replies to Cai Simon (Nokia) and Scott (Inspur). Scott (Inspur) replies to Runze (Huawei) Runze(Huawei) replies to Scott (Inspur) and provides r01. Runze(Huawei) replies to Scott (Inspur)'s comment. Runze (Huawei) provides r02. ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to postpone the CR Runze (Huawei) replies to Stephen (Qualcomm), and proposes to agree the CR. We should avoid lose the progress in this meeting and address minor concern in the May meeting ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2305591 | CR | Approval | 23.273 CR0369R1 (Rel-18, 'F'): Further clarification on the support of PRUs and related procedures | Huawei, HiSilicon | Rel-18 | Revision of S2-2305127r02. Approved. CC#4: WITHDRAWN | Withdrawn | |
| 9.6.2 | S2-2305350 | CR | Approval | 23.273 CR0372 (Rel-18, 'B'): Routing ID Update between AMF and LMF | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! r01 agreed. Revised to S2-2305592. CC#4: Noted | Cai Simon (Nokia) provide r01 to correct the cover page Stephen (Qualcomm) provides comments Cai Simon (Nokia) clarifies to Stephen (Qualcomm) ==== Revisions Deadline ==== Stephen (Qualcomm) disagrees both versions of the CR Cai Simon (Nokia) clarifies to Stephen (Qualcomm) and suggests EN Cai Simon (Nokia) proposes to approve the CR with EN ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2305592 | CR | Approval | 23.273 CR0372R1 (Rel-18, 'B'): Routing ID Update between AMF and LMF | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305350r01. Approved. CC#4: WITHDRAWN | Withdrawn | |
| 9.6.2 | S2-2304866 | CR | Approval | 23.502 CR4080 (Rel-18, 'F'): Update of the Namf_Communication_N1MessageNotify service operation | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.6.2 | - | - | - | Service continuity | - | - | Docs:=7 | - | |
| 9.6.2 | S2-2304864 | CR | Approval | 23.273 CR0349 (Rel-18, 'B'): Location service continuity between EPS and 5GS (bi-direction) for deferred MT-LR | Huawei, HiSilicon, Deutsche Telekom | Rel-18 | r04 agreed. Revised to S2-2305593. | Stephen (Qualcomm) provides comments Guanglei (Huawei) provides r01 Cai Simon (Nokia) asks a question Guanglei (Huawei) provides r02 Yunjing(CATT) provides comments. Guanglei (Huawei) replies Yunjing (CATT) replies. Guanglei (Huawei) replies. Stephen (Qualcomm) provides more comments Guanglei (Huawei) provides r03 Richard (Ericsson) provides question Guanglei (Huawei) replies to Richard Guanglei (Huawei) answers Simon's question. Richard (Ericsson) replies to Guanglei Guanglei (Huawei) further replies to Richard Guanglei (Huawei) provides r04 ==== Revisions Deadline ==== Stephen (Qualcomm) can accept the r04 Richard (Ericsson) supports r04 and would cosign it Yunjing (CATT) supports r04 and would like to cosign ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305593 | CR | Approval | 23.273 CR0349R1 (Rel-18, 'B'): Location service continuity between EPS and 5GS (bi-direction) for deferred MT-LR | Huawei, HiSilicon, Deutsche Telekom, Ericsson, CATT | Rel-18 | Revision of S2-2304864r04. Approved | Agreed | |
| 9.6.2 | S2-2305069 | CR | Approval | 23.273 CR0356 (Rel-18, 'F'): Update the Location Service Continuity between EPS and 5GS for Immediate Location Request | CATT | Rel-18 | r01 agreed. Revised to S2-2305594. | Runze (Huawei) provides comments. Yunjing (CATT) replies. Richard (Ericsson) provides comments. Yunjing (CATT) replies to Richard (Ericsson). Richard (Ericsson) answers to Yunjing Yunjing (CATT) replies to Richard (Ericsson) and provides r01. Richard (Ericsson) replies to Yunjing ==== Revisions Deadline ==== Cai Simon (Nokia) comments Runze (Huawei) supports r01. Richard (Ericsson) I am fine to agree the CR and continue on the next meeting ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305594 | CR | Approval | 23.273 CR0356R1 (Rel-18, 'F'): Update the Location Service Continuity between EPS and 5GS for Immediate Location Request | CATT | Rel-18 | Revision of S2-2305069r01. Approved | Agreed | |
| 9.6.2 | S2-2305066 | DISCUSSION | Discussion | Discussion on Solutions for Location Service Continuity between EPS and 5GS | CATT | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2305068 | CR | Approval | 23.273 CR0355 (Rel-18, 'F'): Update the Architecture of Location Service for interconnection between 5GC and EPC | CATT | Rel-18 | r02 agreed. Revised to S2-2305595. | Stephen (Qualcomm) provides comments Yunjing (CATT) replies. Yunjing (CATT) provides r01. Yunjing (CATT) provides r02 to avoid overlap with S2-2305069. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305595 | CR | Approval | 23.273 CR0355R1 (Rel-18, 'F'): Update the Architecture of Location Service for interconnection between 5GC and EPC | CATT | Rel-18 | Revision of S2-2305068r02. Approved | Agreed | |
| 9.6.2 | - | - | - | Satellite Access | - | - | Docs:=3 | - | |
| 9.6.2 | S2-2305119 | CR | Approval | 23.273 CR0365 (Rel-18, 'F'): Clarification on the low power or high accuracy positioning | Huawei, HiSilicon | Rel-18 | CC#4: r01 + changes agreed. Revised to S2-2306245. For CC#4 | Yunjing (CATT) proposes to merge this CR into S2-2305070. Runze (Huawei) replies to Yunjing (CATT). Yunjing (CATT) provides comments. Scott (Inspur) provides comments. Runze (Huawei) replies to Scott (Inspur) and suggests to close the open issue. Runze (Huawei) replies to Yunjing (CATT) and provides r01. ==== Revisions Deadline ==== Scott (Inspur) propose to postpone the paper. Yunjing (CATT) suggests to go with r01. Scott (Inpur) comments and propose to postpone the paper until SA1's feedback. Runze (Huawei) disagrees to postpone the paper, and hope Scott can withdraw the proposal. Otherwise this is for CC#4 discussion. ==== Comments Deadline ==== Runze (Huawei) proposes to add a note' NOTE 1: this may be revisited based on SA1 feedback.' On top of r01, and agree the paper. | Revised |
| 9.6.2 | S2-2306245 | CR | Approval | 23.273 CR0365R1 (Rel-18, 'F'): Clarification on the low power or high accuracy positioning | Huawei, HiSilicon | Rel-18 | Revision of S2-2305119. CC#4: Approved | Agreed | |
| 9.6.2 | S2-2304939 | CR | Approval | 23.273 CR0352 (Rel-18, 'F'): Removing the indication of UE location verification in LCS Request to LMF | INSPUR | Rel-18 | CR Cover sheet error! Noted | Stephen (Qualcomm) provides comments Scott (Inspur) replies to Stephen(Qalcomm) Cai Simon (Nokia) raises compatibility concern Guanglei (Huawei) comments Guanglei (Huawei) replies Guanglei (Huawei) further replies Cai Simon (Nokia) comments David (Samsung) agrees with other companies' concerns on this CR. Dimitris (Lenovo) also objects to this CR Richard (Ericsson) provides comments and agrees with other companies' concerns Scott (Inspur) comments. ==== Revisions Deadline ==== Stephen (Qualcomm) also proposes to note the CR Scott(Inspur) objects Stephen (Qualcomm)'s objection. ==== Comments Deadline ==== | Noted |
| 9.6.2 | - | - | - | Triggered Location | - | - | Docs:=5 | - | |
| 9.6.2 | S2-2304667 | DISCUSSION | Information | Discussion on two ambiguous aspects of event report allowed area | vivo | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2304668 | CR | Approval | 23.273 CR0335 (Rel-18, 'B'): Resolve two ambiguous aspects of event report allowed area | vivo | Rel-18 | r01 agreed. Revised to S2-2305596. | Stephen (Qualcomm) provides comments Amy (vivo) asks for clarification Stephen (Qualcomm) replies Amy (vivo) Amy (vivo) provides r01 Amy (vivo) thanks Stephen (Qualcomm) for your support ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305596 | CR | Approval | 23.273 CR0335R1 (Rel-18, 'B'): Resolve two ambiguous aspects of event report allowed area | Vivo | Rel-18 | Revision of S2-2304668r01. Approved | Agreed | |
| 9.6.2 | S2-2304669 | CR | Approval | 23.273 CR0336 (Rel-18, 'B'): The terminology replacing of power saving area | vivo | Rel-18 | r01 agreed. Revised to S2-2305597. | Yunjing (CATT) provides r01. Amy (vivo) thanks Yunjing for providing r01 and asks a question on 'event report expected area' inclusion in Ngmlc_Location_ProvideLocation service operation Yunjing (CATT) replies. Amy (vivo) supports r01 and replies to Yunjing (CATT) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305597 | CR | Approval | 23.273 CR0336R1 (Rel-18, 'B'): The terminology replacing of power saving area | Vivo, CATT | Rel-18 | Revision of S2-2304669r01. Approved | Agreed | |
| 9.6.2 | - | - | - | EN removal, and etc | - | - | Docs:=11 | - | |
| 9.6.2 | S2-2305064 | DISCUSSION | Discussion | Discussion on Proposals to Solve the Editor s Note introduced by 5G_eLCS_Ph3 WID | CATT | Rel-18 | Noted | Noted | |
| 9.6.2 | S2-2305070 | CR | Approval | 23.273 CR0357 (Rel-18, 'F'): Remove the Editor s Notes | CATT | Rel-18 | r02 agreed. Revised to S2-2305598. | Yunjing (CATT) provides r01. Cai Simon (Nokia) opposes all EN removal about UP Yunjing (CATT) provides r02 to take back EN on user plane positioning. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305598 | CR | Approval | 23.273 CR0357R1 (Rel-18, 'F'): Remove the Editor s Notes | CATT | Rel-18 | Revision of S2-2305070r02. Approved | Agreed | |
| 9.6.2 | S2-2305071 | CR | Approval | 23.273 CR0358 (Rel-18, 'F'): Update the LMF initiated User Plane Connection to solve Editor s Note | CATT | Rel-18 | CC#4: Noted | Stephen (Qualcomm) provides comments Yunjing (CATT) provides r01. Cai Simon (Nokia) proposes to postpone the CR until CT response Yunjing (CATT) provides r02 to remove changes waiting for CT response Yunjing (CATT) replies to Cai Simon (Nokia). Cai Simon (Nokia) clarifies to Yunjing (CATT) Yunjing (CATT) replies to Cai Simon (Nokia) and provides r03. ==== Revisions Deadline ==== Guanglei (Huawei) supports r03 Cai Simon (Nokia) objects the CR Richard (Ericsson) accepts r03 Cai Simon (Nokia) keeps the objection and clarifies ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2305073 | CR | Approval | 23.273 CR0360 (Rel-18, 'F'): Update the procedures applicable to a PRU | CATT | Rel-18 | Postponed | Stephen (Qualcomm) provides comments Yunjing (CATT) replies. Cai Simon (Nokia) proposes to consider S2-2303945_R1-2302146 Yunjing (CATT) replies to Cai Simon (Nokia). Scott (Inspur) comments. Stephen (Qualcomm) replies to Yunjing (CATT) Cai Simon (Nokia) comments on the confusing statements in CR Yunjing(CATT) replies to Simon(Nokia) and Scott(Inspur). Scott(Inspur) replies to Yunjing(CATT). Yunjing(CATT) replies and provides r01. ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to postpone the CR due to errors in both versions Yunjing (CATT) is fine to postpone the CR and replies to Stephen (Qualcomm). ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2305074 | CR | Approval | 23.273 CR0361 (Rel-18, 'F'): Update the PRU selection mechanism | CATT | Rel-18 | Noted | Stephen (Qualcomm) provides comments Cai Simon (Nokia) asks a question Yunjing (CATT) replies and provides r01. Guanglei (Huawei) comments. Scott (Inspur) comments. Cai Simon (Nokia) clarifies, provides r02 and co-signs Yaxin (OPPO) asks questions and provides suggestions. ==== Revisions Deadline ==== Guanglei (Huawei) proposes to postpone Guanglei (Huawei) clarifies: we object to using UDR or NRF for real-time PRU information monitoring, thus why this CR should be postponed or noted Stephen (Qualcomm) disagrees the r02 and r00 though r01 is acceptable for us Richard (Ericsson) objects the solution Yunjing (CATT) replies. ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2305067 | CR | Approval | 23.273 CR0354 (Rel-18, 'F'): Add new LMF service operations | CATT | Rel-18 | r01 agreed. Revised to S2-2305599. | Yunjing (CATT) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305599 | CR | Approval | 23.273 CR0354R1 (Rel-18, 'F'): Add new LMF service operations | CATT, Huawei, HiSilicon | Rel-18 | Revision of S2-2305067r01. Approved | Agreed | |
| 9.6.2 | S2-2305351 | CR | Approval | 23.273 CR0373 (Rel-18, 'B'): Clarification of Missing LMF ID in AMF logic | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305600. | Cai Simon (Nokia) provide r01 to correct the cover page Yaxin (OPPO) provides comments. Cai Simon (Nokia) clarifies to Yaxin (OPPO) Yaxin (OPPO) replies to Cai Simon (Nokia). Cai Simon (Nokia) agrees with the comments and provides r02 ==== Revisions Deadline ==== Yaxin (OPPO) is OK with r02. ==== Comments Deadline ==== | Revised |
| 9.6.2 | S2-2305600 | CR | Approval | 23.273 CR0373R1 (Rel-18, 'B'): Clarification of Missing LMF ID in AMF logic | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305351r02. Approved | Agreed | |
| 9.6.2 | S2-2304672 | CR | Approval | 23.032 CR0023 (Rel-18, 'B'): New shape to support hollow area | vivo | Rel-18 | Noted | Stephen (Qualcomm) provides comments and questions Runze (Huawei) comments. Hank (vivo) replies to Stephen(Qualcomm) and Runze(Huawei). Stephen (Qualcomm) provides more comments Scott (Inspur) provides comments Amy (vivo) thanks to Stephen, Runze and Scott for the discussion on 23032 defined GAD shape. ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 9.6.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=8 | - | |
| 9.6.2 | S2-2305072 | CR | Approval | 23.273 CR0359 (Rel-18, 'F'): Update the Terminology of Power Saving Area | CATT | Rel-18 | NOT HANDLED | ||
| 9.6.2 | S2-2304860 | CR | Approval | 23.273 CR0347 (Rel-18, 'F'): LMF service operation to support UP Positioning | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.6.2 | S2-2304865 | CR | Approval | 23.273 CR0350 (Rel-18, 'F'): LMF service operation to support of PRU location measurement transfer | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.6.2 | S2-2304857 | CR | Approval | 23.273 CR0344 (Rel-18, 'B'): Clarification on support of UL CL/BP/L-PSA insertion for UP positioning | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.6.2 | S2-2304741 | CR | Approval | 23.273 CR0341 (Rel-18, 'B'): Update of the PRU Association Procedure | Huawei, HiSilicon | Rel-18 | Scott (Inspur) provides comments and questions Guanglei (Huawei) reminds this CR is not handled in this e-meeting | NOT HANDLED | |
| 9.6.2 | S2-2304863 | CR | Approval | 23.502 CR4079 (Rel-18, 'F'): Subscription data update for UP positioning | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.6.2 | S2-2304740 | CR | Approval | 23.273 CR0340 (Rel-18, 'B'): Update of the UE initiated User Plane Connection Procedure | Huawei, HiSilicon | Rel-18 | Scott (Inspur) provides comments and questions Guanglei (Huawei) reminds this CR is not handled | NOT HANDLED | |
| 9.6.2 | S2-2304858 | CR | Approval | 23.273 CR0345 (Rel-18, 'F'): Alignment of functional description for UP positioning | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.7.1 | - | - | - | Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) | - | - | Docs:=0 | - | |
| 9.7.2 | - | - | - | Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | - | - | Docs:=72 | - | |
| 9.7.2 | - | - | - | LS In and LS Out | - | - | Docs:=3 | - | |
| 9.7.2 | S2-2303967 | LS In | Action | LS from SA WG1: Reply LS on service requirement for emergency service support over ProSe relay | SA WG1 (S1-230740) | Rel-18 | Noted | Fei (OPPO) proposed to note this LS from SA1. | Noted |
| 9.7.2 | S2-2304640 | LS OUT | Approval | [DRAFT] LS on 5G ProSe Layer-2 UE-to-UE Relay QoS enforcement | Qualcomm Incorporated | Rel-18 | r03 agreed. Revised to S2-2305915. | Yali (OPPO) provides r01. Mehrdad (Mediatek Inc.) prefers r01. Jungje(Interdigital) comments. Yali(OPPO) replies to Jungje(Interdigital). Deng Qiang (CATT) provides r02. Hong (Qualcomm) comments and prefers r01 over r02. ==== Revisions Deadline ==== JungJe(Interdigital) propose to agree r01 with deleting 'or SA2 define the method as above option' at end of clause 1 and deleting 'the options of ' at Action in clause 2. Steve (Huawei) provides r03 in drafts, we can be positive on RAN taking action. Mehrdad (Mediatek Inc.) prefers r01 or r03 but objects to original version. JungJe(Interdigital) prefer r03 but not OK with r01 itself. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305915 | LS OUT | Approval | Reply LS on 5G ProSe Layer-2 UE-to-UE Relay QoS enforcement | SA WG2 | Rel-18 | Revision of S2-2304640r03. Approved | Approved | |
| 9.7.2 | - | - | - | KI#1: UE-to-UE Relay | - | - | Docs:=17 | - | |
| 9.7.2 | S2-2304130 | CR | Approval | 23.304 CR0236 (Rel-18, 'F'): Update to 5G ProSe Layer-3 UE-to-UE Relay Communication for Ethernet Traffic | Ericsson, OPPO, CATT | Rel-18 | Approved | Agreed | |
| 9.7.2 | S2-2304234 | CR | Approval | 23.304 CR0242 (Rel-18, 'B'): Resolve EN on parameter provisioning for U2U Relay communication with integrated discovery | CATT | Rel-18 | r06 agreed. Revised to S2-2305916. | Yali (OPPO) provides r01. Zhang (Ericsson) provides comments Deng Qiang (CATT) comments on r01. Yali (OPPO) provides r02. Deng Qiang (CATT) provides r03. Jung Je (interdigital) comments r03 Deng Qiang (CATT) clarifies to Jung Je (interdigital). Changzheng (China Telecom) asks a question. Deng Qiang (CATT) clarified to Changzheng (China Telecom). Changzheng (China Telecom) thanks Deng Qiang for clarification. JungJe(Interdigital) responses Deng(CATT) and uploaded r05. Yali (OPPO) provides r06. JungJe(Interdigital) ask clarification. Deng Qiang (CATT) clarifies to JungJe(Interdigital). Deng Qiang (CATT) provides r07 on top of r06. Yali (OPPO) asks a question. Deng Qiang (CATT) clarifies to Yali (OPPO). Yali (OPPO) replies to Deng Qiang (CATT). JungJe(Interdigital) responds to Deng(CATT) and uploaded r08. Yali(OPPO) comments on r08 and thinks r06 is an acceptable version. JungJe(Interdigital) respondes Yali(OPPO) and provided r09. Yali(OPPO) replies to JungJe(Interdigital). JungJe(Interdigital) responds to Yali(OPPO) ==== Revisions Deadline ==== JungJe(Interdigital) is OK to agree to r06. Deng Qiang (CATT) is also fine with r06. Yali (OPPO) only accepts r06. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305916 | CR | Approval | 23.304 CR0242R1 (Rel-18, 'B'): Resolve EN on parameter provisioning for U2U Relay communication with integrated discovery | CATT | Rel-18 | Revision of S2-2304234r06. Approved | Agreed | |
| 9.7.2 | S2-2304235 | CR | Approval | 23.304 CR0243 (Rel-18, 'B'): Update of U2U Relay Communication with integrated Discovery procedure | CATT | Rel-18 | r02 agreed. Revised to S2-2305917. | Yali (OPPO) comments. Zhang (Ericsson) provides comment Jung Je (Interdigital) provides comment Deng Qiang (CATT) replies and provides r01. Yali (OPPO) provides r02. ==== Revisions Deadline ==== JungJe(Interdigital) is OK to r02. Deng Qiang (CATT) is fine with r02. Zhang (Ericsson) can live with r02 and provide comment Deng Qiang (CATT) thanks Zhang (Ericsson) understanding, we can further update next meeting. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305917 | CR | Approval | 23.304 CR0243R1 (Rel-18, 'B'): Update of U2U Relay Communication with integrated Discovery procedure | CATT | Rel-18 | Revision of S2-2304235r02. Approved | Agreed | |
| 9.7.2 | S2-2304280 | CR | Approval | 23.304 CR0248 (Rel-18, 'F'): Provisioning for traffic type of L3 U2U Relay | OPPO, Ericsson | Rel-18 | Approved | Agreed | |
| 9.7.2 | S2-2304416 | CR | Approval | 23.304 CR0253 (Rel-18, 'F'): Alignment of policy for U2U and Direct Discovery and Communication | Huawei, HiSilicon | Rel-18 | r00 agreed. Revised to S2-2305918. | Zhang (Ericsson) provides comments Steve (Huawei) provides r01 ==== Revisions Deadline ==== Hong (Qualcomm) OBJECTs r01. Zhang (Ericsson) agree with Hong that 36.331 should be added back Steve (Huawei) r00 is ok, it keeps 36.331. Steve (Huawei) proposes r00 with the 'The service is only specified for NR' bullet & NOTE 5 duplicates removed. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305918 | CR | Approval | 23.304 CR0253R1 (Rel-18, 'F'): Alignment of policy for U2U and Direct Discovery and Communication | Huawei, HiSilicon | Rel-18 | Revision of S2-2304416r00. Approved | Agreed | |
| 9.7.2 | S2-2304747 | CR | Approval | 23.304 CR0260 (Rel-18, 'B'): Support of identifiers for L2 U2U Relay | ASUSTeK | Rel-18 | CR Cover sheet error! Postponed | Deng Qiang (CATT) comments. Lider (ASUSTeK) responds to Deng Qiang. Wen (vivo) comments. Lider (ASUSTeK) responds to Wen. Lider (ASUSTeK) provides r01. JungJe(Interdigital) commented to Lider(ASUSTek) Lider (ASUSTeK) postpones this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.7.2 | S2-2304793 | CR | Approval | 23.304 CR0261 (Rel-18, 'B'): U2U relay capabilities and subscription | vivo | Rel-18 | Approved | Agreed | |
| 9.7.2 | S2-2304946 | CR | Approval | 23.304 CR0273 (Rel-18, 'B'): Clarification on AF-based Service Parameter Provisioning | ZTE | Rel-18 | r01 agreed. Revised to S2-2305919. | Deng Qiang (CATT) comments on the CR category. Hao (ZTE) responds and provides r01. ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r01. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305919 | CR | Approval | 23.304 CR0273R1 (Rel-18, 'F'): Clarification on AF-based Service Parameter Provisioning | ZTE | Rel-18 | Revision of S2-2304946r01. Approved | Agreed | |
| 9.7.2 | S2-2305175 | CR | Approval | 23.304 CR0278 (Rel-18, 'F'): Correction of LIU update procedure. | Interdigital | Rel-18 | Noted | Deng Qiang (CATT) provides r01. Zhang (Ericsson) show concerns with proposal JungJe(Interdigital) responded to DengQiang(CATT) and Zhang(Ericsson) Deng Qiang (CATT)replies to JungJe (Interdigital) and Zhang (Ericsson). JungJe(Interdigital) response to Deng Qiang(CATT) Deng Qiang(CATT) replies to JungJe (Interdigital). Hong (Qualcomm) comments and suggest to NOTE the CR. Deng Qiang (CATT) clarifies to Hong (Qualcomm). ==== Revisions Deadline ==== JungJe(Interdigital) is OK to r00 and object to r01. Deng Qiang (CATT) proposed to note this CR. JungJe(Interdigital) responds to Deng(CATT) and Hong(Qualcomm) ==== Comments Deadline ==== | Noted |
| 9.7.2 | S2-2305176 | CR | Approval | 23.304 CR0279 (Rel-18, 'B'): Link Modification Procedure with L3 UE-to-UE Relay | Interdigital | Rel-18 | r03 agreed. Revised to S2-2305920. | Deng Qiang (CATT) provides r01. Yali (OPPO) comments on r01. JungJe(Interdigital) responded to Yali (OPPO) and uploaded r01. Yali (OPPO) provides r03. Deng Qiang (CATT) comments on r03. ==== Revisions Deadline ==== JungJe(Interdigital) is OK with r03 Deng Qiang (CATT) is fine with r03 and requests co-source. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305920 | CR | Approval | 23.304 CR0279R1 (Rel-18, 'B'): Link Modification Procedure with L3 UE-to-UE Relay | Interdigital, CATT | Rel-18 | Revision of S2-2305176r03. Approved | Agreed | |
| 9.7.2 | S2-2305248 | CR | Approval | 23.503 CR1029 (Rel-18, 'C'): General description updates for Supporting UE-to-UE Relay | Xiaomi | Rel-18 | r01 agreed. Revised to S2-2305921. | Judy (Ericsson) provides r01 Jianning (Xiaomi) is ok with r01 ==== Revisions Deadline ==== Judy (Ericsson) asks to add as co-source ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305921 | CR | Approval | 23.503 CR1029R1 (Rel-18, 'C'): General description updates for Supporting UE-to-UE Relay | Xiaomi, Ericsson | Rel-18 | Revision of S2-2305248r01. Approved | Agreed | |
| 9.7.2 | - | - | - | KI#2: Path switching btw two indirect paths | - | - | Docs:=2 | - | |
| 9.7.2 | S2-2304945 | CR | Approval | 23.304 CR0272 (Rel-18, 'B'): Clarification on 5G ProSe UE-to-Network Relay Reselection and Path Switching | ZTE, Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305922. | Fei (OPPO) comments and provides r01. Deng Qiang (CATT) comments. Hao (ZTE) responds. Fei (OPPO) provides replies. Judy (Ericsson) comments Jing (China Telecom) comments. Hao (ZTE) responds and provides r02. ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r02. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305922 | CR | Approval | 23.304 CR0272R1 (Rel-18, 'B'): Clarification on 5G ProSe UE-to-Network Relay Reselection and Path Switching | ZTE, Huawei, HiSilicon | Rel-18 | Revision of S2-2304945r02. Approved | Agreed | |
| 9.7.2 | - | - | - | KI#3: Direct path switching btw PC5 and Uu | - | - | Docs:=6 | - | |
| 9.7.2 | S2-2304229 | CR | Approval | 23.304 CR0240 (Rel-18, 'F'): ENs resolution for path switching between PC5 path and Uu path | LG Electronics, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, Samsung, Apple, China Telecom, Ericsson, Intel | Rel-18 | r07 agreed. Revised to S2-2305923, merging S2-2304915, S2-2304911 and S2-2304421 | Steve (Huawei) comments Steve (Huawei) comments. Fei (OPPO) comments. LaeYoung (LGE) provides r01 by taking the proposed changes in S2-2304421 into account. Fei (OPPO) comments on r01. LaeYoung (LGE) provides r02. Saubhagya (Nokia) provides r03. Judy (Ericsson) comments Fei (OPPO) comments on r03. Steve (Huawei) comments, provides r04 LaeYoung (LGE) provides r05. Mehrdad (Mediatek Inc.) prefers r05. JungJe(Interdigital) provides r06. LaeYoung (LGE) provides r07. ==== Revisions Deadline ==== JungJe(Interdigital) is OK with r07. Mehrdad (Mediatek Inc.) is OK with r07. Steve (Huawei) can live with r07 ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305923 | CR | Approval | 23.304 CR0240R1 (Rel-18, 'F'): ENs resolution for path switching between PC5 path and Uu path | LG Electronics, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, Samsung, Apple, China Telecom, Ericsson, Intel, KT | Rel-18 | Revision of S2-2304229r07, merging S2-2304915, S2-2304911 and S2-2304421. Approved | Agreed | |
| 9.7.2 | S2-2304420 | CR | Approval | 23.304 CR0257 (Rel-18, 'F'): EN removal on IP address sharing during communication path switching | Huawei, HiSilicon, Interdigital | Rel-18 | Noted | Judy (Ericsson) comments LaeYoung (LGE) comments. Deng Qiang (CATT) comments. ==== Revisions Deadline ==== Fei (OPPO) proposed to note this CR or mark it merged into S2-2304229 LaeYoung (LGE) proposes to NOTE this CR. ==== Comments Deadline ==== | Noted |
| 9.7.2 | S2-2304421 | CR | Approval | 23.304 CR0258 (Rel-18, 'F'): Path selection policy used during communication path switching | Huawei, HiSilicon | Rel-18 | Merged into S2-2305923 | Judy (Ericsson) comments that this CR and 4229 propose competing solutions on how UE IP addresses are exchanged over PC5 between UEs. Judy (Ericsson) comments that this CR is assumed to be merged into 4229, and request to ignore the previous comment LaeYoung (LGE) also thinks that this CR can be MERGED into 4229. Mehrdad (Mediatek Inc.) also suggest to Mark this CR as merged into 4229 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.7.2 | S2-2304911 | CR | Approval | 23.304 CR0268 (Rel-18, 'F'): Clarification on path switching policy between PC5 and Uu reference points | Samsung, KT | Rel-18 | Merged into S2-2305923 | LaeYoung (LGE) proposes to NOTE this CR or merge this CR into S2-2304229. Fei (OPPO) also proposes to merge this CR into S2-2304229 Changhong (Intel) shares same view with LaeYoung to NOTE it. Kisuk (Samsung) merges this CR into S2-2304229. LaeYoung (LGE) replies to Kisuk (Samsung). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.7.2 | S2-2304915 | CR | Approval | 23.304 CR0269 (Rel-18, 'F'): Clarification on procedures for communication path switching between PC5 and Uu reference points | Samsung, KT | Rel-18 | Merged into S2-2305923 | LaeYoung (LGE) proposes to NOTE this CR. Fei (OPPO) also proposed to NOTE this CR. Changhong (Intel) shares same view with LaeYoung and Fei. Kisuk (Samsung) merges this CR into S2-2304229. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.7.2 | - | - | - | KI#5: Multi-path transmission | - | - | Docs:=6 | - | |
| 9.7.2 | S2-2304131 | CR | Approval | 23.304 CR0237 (Rel-18, 'F'): KI#5 Resolve EN for authorization of multi-path via Uu and via L3 U2N Relay | Ericsson, Intel | Rel-18 | r01 agreed. Revised to S2-2305924. | Mehrdad (Mediatek Inc.) supports this CR and requests to co-source. Judy (Ericsson) thanks Mehrdad (Mediatek Inc) for the support and provide r01 adding Mediatek Inc. as co-source ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305924 | CR | Approval | 23.304 CR0237R1 (Rel-18, 'F'): KI#5 Resolve EN for authorization of multi-path via Uu and via L3 U2N Relay | Ericsson, Intel, Mediatek Inc. | Rel-18 | Revision of S2-2304131r01. Approved | Agreed | |
| 9.7.2 | S2-2304132 | CR | Approval | 23.304 CR0238 (Rel-18, 'F'): KI#5 Resolve EN for term of multi-path via Uu and via U2N Relay | Ericsson, LG Electronics, Intel | Rel-18 | r01 agreed. Revised to S2-2305925. | Steve (Huawei) provides r01 Judy (Ericsson) thanks Steve (Huawei) for the revision and is fine with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305925 | CR | Approval | 23.304 CR0238R1 (Rel-18, 'F'): KI#5 Resolve EN for term of multi-path via Uu and via U2N Relay | Ericsson, LG Electronics, Intel | Rel-18 | Revision of S2-2304132r01. Approved | Agreed | |
| 9.7.2 | S2-2304230 | CR | Approval | 23.304 CR0241 (Rel-18, 'B'): Update to L2 link establishment for multi-path communication | LG Electronics | Rel-18 | Noted | Fei (OPPO) comments Wen (vivo) comments LaeYoung (LGE) replies to Fei (OPPO) and Wen (vivo). Steve (Huawei) the relay should be doing access control or priority determination Mehrdad (Mediatek Inc.) comments. LaeYoung (LGE) replies to Steve (Huawei) and Mehrdad (Mediatek Inc.). Fei (OPPO) provides comments. Deng Qiang (CATT) comments. Fei (OPPO) responds. Changhong (Intel) comments. LaeYoung (LGE) replies to Deng Qiang (CATT), Fei (OPPO) and Changhong (Intel). LaeYoung (LGE) sends ACK to HUG from Mehrdad (Mediatek Inc.). ;-) ==== Revisions Deadline ==== Fei (OPPO) objects this CR and proposes to note it. LaeYoung (LGE) sends ACK to HUG from Fei (OPPO). ;-) ==== Comments Deadline ==== | Noted |
| 9.7.2 | S2-2304933 | CR | Approval | 23.304 CR0270 (Rel-18, 'B'): MA PDU Session in multi-path transmission for L3 U2N Relay with N3IWF | China Telecom | Rel-18 | Approved | Agreed | |
| 9.7.2 | - | - | - | KI#7: Emergency Service over U2N relay | - | - | Docs:=15 | - | |
| 9.7.2 | S2-2304306 | CR | Approval | 23.304 CR0249 (Rel-18, 'F'): Emergency Priority Handling for 5G ProSe Layer-3 Relay | MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson, vivo, Huawei, HiSilicon, Samsung, AT&T | Rel-18 | r06 agreed. Revised to S2-2305926, merging S2-2305247 and S2-2304935 | Jianning (Xiaomi) provides r01 by merging from S2-2305247 Fei (OPPO) provides r02. Jianning (Xiaomi) provides question for clarification Mehrdad (Mediatek Inc.) replies to Xiaomi. Steve (Huawei) comments. Hannu (Nokia) provides r03. Jianning (Xiaomi) provide comments and provide r04 on top of r03 Mehrdad (Mediatek Inc.) provides r05. Fei (OPPO) provides r06. Mehrdad (Mediatek Inc.) replies to OPPO. Hannu (Nokia) supports r06. ==== Revisions Deadline ==== Jianning (Xiaomi) supports r06 Mehrdad (Mediatek Inc.) is ok with r06 Steve (Huawei) is ok with r06 ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305926 | CR | Approval | 23.304 CR0249R1 (Rel-18, 'F'): Emergency Priority Handling for 5G ProSe Layer-3 Relay | MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson, vivo, Huawei, HiSilicon, Samsung, AT&T, Xiaomi, OPPO | Rel-18 | Revision of S2-2304306r06, merging S2-2305247 and S2-2304935. Approved | Agreed | |
| 9.7.2 | S2-2304307 | CR | Approval | 23.304 CR0250 (Rel-18, 'F'): Indication of Support for Emergency Relaying | MediaTek Inc. | Rel-18 | r10 agreed. Revised to S2-2305927. | Judy (Ericsson) provides r01 Jianning (Xiaomi) provides r02 by merging from S2-2305247 Fei (OPPO) comments. Steve (Huawei) comments. Mehrdad (Mediatek Inc.) suggests to do a SoH during CC#2 for this CR original version vs r01 Judy (Ericsson) asks Fei (OPPO) for clarification Judy (Ericsson) responds to Steve (Huawei) Hannu (Nokia) provides r03. Mehrdad (Mediatek Inc.) clarifies that r01, r02 and r03 is not in line with SoH. Any new changes to be added to original version. Mehrdad (Mediatek Inc.) provides r04 with original wording to be used as baseline for further updates. Mehrdad (Mediatek Inc.) provides r05 merging again S2-2305247 into this CR. Hannu (Nokia) is OK with r05 and accepts the removal of his late change in clause 6.5.2.1.2 Steve (Huawei) provides r06 Judy (Ericsson) provides r07 Steve (Huawei) has some problem with r07 Wen (vivo) comments on r07 Mehrdad (Mediatek Inc.) replies to Ericsson Mehrdad (Mediatek Inc.) thinks based on comments raised we have to stick to agreed WF in SoH (option 1). Fei (OPPO) provides comments. Deng Qiang (CATT) comments. Judy (Ericsson) responds and provides r08 to resolve conflict with 4423 Judy (Ericsson) responds to Deng Qiang (CATT) Steve (Huawei) comments, provides r09 Mehrdad (Mediatek Inc.) provides r10 with small change in cover page versus r09. Judy (Ericsson) comments on r10 Mehrdad (Mediatek Inc.) replies to Ericsson. ==== Revisions Deadline ==== Fei (OPPO) can only accept r00, r09 and r10. Wen(vivo) also can only accept r00, r09 and r10 following the SoH results. Judy (Ericsson) cannot accept r00, cannot accept r09&r10 as they are, requesting changes to progress, explained below Fei (OPPO) provides r12 in draft folder on top of r10. See the summary of changes. Judy (Ericsson) thanks Fei (OPPO) and proposes NOTE text '5G ProSe Layer-2 UE-to-Network Relay can advertise its support of emergency service even if its serving PLMN does not support emergency service' Mehrdad (Mediatek Inc.) only accepts r00, r09, r10. Can live with wording in r12 on top of r10 with small change but objects to the rest of revisions. Judy (Ericsson) responds to Mehrdad (Mediatek Inc.) Mehrdad (Mediatek Inc.) replies to Ericsson, Huawei. Fei (OPPO) proposed the way forward. The changes made on top of r10 are summarized. Mehrdad (Mediatek Inc.) agrees with the Way Forward suggested by OPPO and the latest NOTE wording on top of r10, i.e. 'When emergency support is indicated by RAN, 5G ProSe Layer-2 UE-to-Network Relay can advertise its support of emergency service even if its serving PLMN does not support emergency service.' Fei (OPPO) two changes on top of r10 i.e. 1st: 'as defined in clause 5.4.4.2 and clause 5.4.4.3' has been moved before 'during 5G ProSe UE-to-Network Relay Discovery' in 3rd paragraph in clause 5.4.4.1; 2nd: NOTE 'When emergency support is indicated by RAN, 5G ProSe Layer-2 UE-to-Network Relay can advertise its support of emergency service even if its serving PLMN does not support emergency service.' is added in clause 5.4.4.2; Steve (Huawei) is ok with r10+changes proposed. Hannu (Nokia) supports r10 with the proposed update. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305927 | CR | Approval | 23.304 CR0250R1 (Rel-18, 'F'): Indication of Support for Emergency Relaying | MediaTek Inc., Xiaomi, Huawei, HiSilicon | Rel-18 | Revision of S2-2304307r10. Approved | Agreed | |
| 9.7.2 | S2-2304382 | CR | Approval | 23.304 CR0252 (Rel-18, 'F'): Emergency service via N3IWF | Nokia, Nokia Shanghai Bell | Rel-18 | r02 agreed. Revised to S2-2305928. | Steve (Huawei) comments on the potential to misunderstand the change. Judy (Ericsson) provide r01 Hannu (Nokia) thanks Steve and Judy for their help and provides r02 with added note ==== Revisions Deadline ==== Steve (Huawei) is ok with r02. ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305928 | CR | Approval | 23.304 CR0252R1 (Rel-18, 'F'): Emergency service via N3IWF | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304382r02. Approved | Agreed | |
| 9.7.2 | S2-2304422 | DISCUSSION | Agreement | Discussion on Indication of support of relaying of emergency service | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.7.2 | S2-2304423 | CR | Approval | 23.304 CR0259 (Rel-18, 'F'): Update on emergency service over U2N Relay | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2305929. | Wen (vivo) comments Steve (Huawei) comments, provides r01. Fei (OPPO) comments. Wen (vivo) comments. Steve (Huawei) asks for clarification Steve (Huawei) comments, provides r02 Wen (vivo) replies to Steve (Huawei) Mehrdad (Mediatek Inc.) comments. Judy (Ericsson) comments and checks the possibility to use 4307 for further discussion due to overlapping changes. Hannu (Nokia) supports Judy's proposal to deal with the overlapping changes in 4407. Steve (Huawei) provides r03 Steve (Huawei) provides r04 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305929 | CR | Approval | 23.304 CR0259R1 (Rel-18, 'F'): Update on emergency service over U2N Relay | Huawei, HiSilicon | Rel-18 | Revision of S2-2304423r04. Approved | Agreed | |
| 9.7.2 | S2-2304798 | DISCUSSION | Discussion | KI#7_Discussion on Provide the IP address of L3 Relay UE to P-CSCF | vivo | Rel-18 | Noted | Noted | |
| 9.7.2 | S2-2304799 | CR | Approval | 23.304 CR0264 (Rel-18, 'B'): KI#7_IP address allocation by Layer 3 Relay UE for emergency service | vivo | Rel-18 | Postponed | Fei (OPPO) asks questions Wen (vivo) replies to Fei Fei (OPPO) comments. Judy (Ericsson) comments. Wen (vivo) replies to Fei. Wen (vivo) replies to Judy. Deng Qiang (CATT) comments. Fei (OPPO) provides comments. Wen (vivo) replies to Fei and Qiang. Fei (OPPO) responded to Wen. Hannu (Nokia) comments and asks for more clarification on the impact area and wider analysis of candidate solutions. Hong (Qualcomm) comments. Wen (vivo) replies and provides r01. Fei (OPPO) comments on r01 and suggests to add some reference to IETF RFC. Wen (vivo) replies and provides r02. Wen (vivo) replies to Judy (Ericsson) Fei (OPPO) responds to Judy. Hannu (Nokia) proposes to postpone the CR. ==== Revisions Deadline ==== Fei (OPPO) postponing this CR is fine. Wen (vivo) replies and provide more information. Wen (vivo) suggests to mark this paper as 'postponed' not 'NOTED' in the chairnotes. ==== Comments Deadline ==== | Postponed |
| 9.7.2 | S2-2304935 | CR | Approval | 23.304 CR0271 (Rel-18, 'F'): Resolve EN on the service requirement for pre-empting relayed emergency service | China Telecom | Rel-18 | Merged into S2-2305926 | Changzheng <China Telecom> proposes to merge this CR into S2-2304306 (from MediaTek Inc.) to have a single stream of discussions. Mehrdad (Mediatek Inc.) agrees with merge. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.7.2 | S2-2304982 | CR | Approval | 23.304 CR0276 (Rel-18, 'F'): PLMN selection for L2 remote UE for emergency service | OPPO | Rel-18 | r03 agreed. Revised to S2-2305930. | Steve (Huawei) asks a question Fei (OPPO) responds to Steve (Huawei) Steve (Huawei) comments. Judy (Ericsson) comments Fei (OPPO) responds to Judy (Ericcsson) and Steve (Huawei), and provides r01. Steve (Huawei) provides r02 Hannu (Nokia) asks about the matching criteria of the multiple candidate Relay UEs and the PLMNs they advertise? Steve (Huawei) comments on mix-and-match Fei (OPPO) responds. Judy (Ericsson) ask question Fei (OPPO) provides r03. Mehrdad (Mediatek Inc.) supports r03 and requests a co-source. Hannu (Nokia) thanks Steve for commenting on mix-and-match. ==== Revisions Deadline ==== Steve (Huawei) is ok with r03 Hannu (Nokia) supports r03 ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305930 | CR | Approval | 23.304 CR0276R1 (Rel-18, 'F'): PLMN selection for L2 remote UE for emergency service | OPPO, MediaTek Inc. | Rel-18 | Revision of S2-2304982r03. Approved | Agreed | |
| 9.7.2 | S2-2305247 | CR | Approval | 23.304 CR0280 (Rel-18, 'C'): To remove the two ENs for UE-to-Network Relay emergency service | Xiaomi | Rel-18 | Merged into S2-2305926 | Fei (OPPO) proposed to merge this CR to S2-2304306 and S2-2304307. Mehrdad (Mediatek Inc.) agrees with OPPO. This CR can be marked as merged into S2-2304306 and S2-2304307. Jianning (Xiaomi) is ok to merge into 04306 and 04307 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.7.2 | - | - | - | Others: PWS | - | - | Docs:=2 | - | |
| 9.7.2 | S2-2304362 | CR | Approval | 23.304 CR0141R3 (Rel-18, 'B'): Support of Public Warning Notification Relaying by 5G ProSe UE-to-Network Relay. | Sony, LG Electronics | Rel-18 | Revision of S2-2302885 from S2#155. r04 agreed. Revised to S2-2305931. | Fei (OPPO) comments. LaeYoung (LGE) provides r01 and answers to Fei (OPPO). Wen (vivo) comments. Mehrdad (Mediatek Inc.) comments on original version and r01. Lars (Sony) provides r02. Fei (OPPO) asks further questions. Lars (Sony responds to Fei. LaeYoung (LGE) replies to Wen (vivo). Deng Qiang (CATT) comments. Wen (vivo) replies to LaeYoung (LGE). Lars (Sony) responds to Deng. LaeYoung (LGE) provides r03. Hong (Qualcomm) provides r04. LaeYoung (LGE) replies to Hong (Qualcomm). Lars (Sony) also fine with r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.7.2 | S2-2305931 | CR | Approval | 23.304 CR0141R4 (Rel-18, 'B'): Support of Public Warning Notification Relaying by 5G ProSe UE-to-Network Relay. | Sony, LG Electronics | Rel-18 | Revision of S2-2304362r04. Approved | Agreed | |
| 9.7.2 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=21 | - | |
| 9.7.2 | S2-2304236 | CR | Approval | 23.304 CR0244 (Rel-18, 'F'): Correction on Ethernet support for Layer-3 U2U Relay | CATT | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304237 | CR | Approval | 23.304 CR0245 (Rel-18, 'B'): Update of Layer-3 U2U Relay management procedures | CATT | Rel-18 | Jung Je (Interdigital) comments and uploaded r01. Yali (OPPO) comments this doc is marked 'exceeding TU Budget'. | NOT HANDLED | |
| 9.7.2 | S2-2304279 | CR | Approval | 23.304 CR0247 (Rel-18, 'F'): Clarification of 5G ProSe UE-to-UE Relay reselection | OPPO | Rel-18 | Jung Je (Interdigital) updated to r01. | NOT HANDLED | |
| 9.7.2 | S2-2304417 | CR | Approval | 23.304 CR0254 (Rel-18, 'F'): Clarification on RSC usage during relay discovery and relay reselection | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304419 | CR | Approval | 23.304 CR0256 (Rel-18, 'B'): Update of U2U Relay discovery to support negotiated Relay reselection | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304794 | CR | Approval | 23.502 CR4070 (Rel-18, 'B'): U2U relay subscription | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304795 | CR | Approval | 23.503 CR0998 (Rel-18, 'B'): ProSe Policy control for U2U relay case | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304796 | CR | Approval | 23.304 CR0262 (Rel-18, 'B'): U2U relay usage supplement | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304947 | CR | Approval | 23.304 CR0274 (Rel-18, 'F'): Modification of Procedure for 5G ProSe UE-to-UE Relay Discovery with Model B | ZTE | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304981 | CR | Approval | 23.304 CR0275 (Rel-18, 'F'): U2U capability over NAS | OPPO | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304238 | CR | Approval | 23.304 CR0246 (Rel-18, 'F'): Resolution of ENs with RAN dependency | CATT | Rel-18 | Jung Je (Interdigital) comments to postpone this CR. | NOT HANDLED | |
| 9.7.2 | S2-2304133 | CR | Approval | 23.502 CR3970 (Rel-18, 'F'): KI#5: Update related to EN resolution in TS 23.304 for term of multi-path via Uu and via U2N Relay | Ericsson, LG Electronics, Intel | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304134 | CR | Approval | 23.503 CR0953 (Rel-18, 'F'): KI#5: Update related to EN resolution in TS 23.304 for term of multi-path via Uu and via U2N Relay | Ericsson, LG Electronics, Intel | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304418 | CR | Approval | 23.304 CR0255 (Rel-18, 'F'): Clarification of multi-path transmission application role | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304797 | CR | Approval | 23.304 CR0263 (Rel-18, 'B'): Clarification on Multi-path | vivo | Rel-18 | Saubhagya (Nokia) asks for clarification Wen (vivo) replies to Saubhagya (Nokia) | NOT HANDLED | |
| 9.7.2 | S2-2304308 | CR | Approval | 23.304 CR0251 (Rel-18, 'F'): Subscription management for Layer-3 Remote UE multi-path communication | MediaTek Inc. | Rel-18 | George Foti (Ericsson) provides r01 | NOT HANDLED | |
| 9.7.2 | S2-2304135 | CR | Approval | 23.304 CR0239 (Rel-18, 'F'): KI#7 Support of relaying emergency service in the U2N Relay | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304800 | CR | Approval | 23.167 CR0371 (Rel-18, 'B'): KI#7_Location validation for the L3 remote UE by the E-CSCF | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304801 | CR | Approval | 23.304 CR0265 (Rel-18, 'B'): KI#7_Retrieve L3 relay UE's ID used for location verification | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304802 | CR | Approval | 23.167 CR0372 (Rel-18, 'B'): KI#7_Not perform UE identities verification for the remote UE | vivo | Rel-18 | NOT HANDLED | ||
| 9.7.2 | S2-2304983 | CR | Approval | 23.304 CR0277 (Rel-18, 'F'): DNN for emergency service | OPPO | Rel-18 | NOT HANDLED | ||
| 9.8.1 | - | - | - | Study on Generic group management, exposure and communication enhancements (FS_GMEC) | - | - | Docs:=0 | - | |
| 9.8.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | Docs:=57 | - | |
| 9.8.2 | - | - | - | KI#1: LADN Service Area for a group | - | - | Docs:=6 | - | |
| 9.8.2 | S2-2304108 | CR | Approval | 23.501 CR4211 (Rel-18, 'C'): Corrections to handling of LADN area per DNN and S-NSSAI | Ericsson | Rel-18 | r06 agreed. Revised to S2-2305601, merging S2-2305161 and S2-2304674 | Sang-Jun (Samsung) provides r01. Liping Wu (CATT) provides comments and r02. Ashok (Samsung) requests for clarification Stefan (Ericsson) replies to Liping Stefan (Ericsson) replies to Ashok Qianghua (Huawei) provides r03 Liping Wu (CATT) replies to Stefan Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides rev04 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides rev04, adding link Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides rev05, more text changes in cyan Hyunsook (LGE) provides a comment. Qianghua (Huawei) provides replies Ashok (Samsung) provides further comments Hyunsook (LGE) asks some more clarifications. Stefan (Ericsson) replies to Hyunsook Hyunsook (LGE) provides r06. ==== Revisions Deadline ==== Stefan (Ericsson) ok with r06 ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305601 | CR | Approval | 23.501 CR4211R1 (Rel-18, 'C'): Corrections to handling of LADN area per DNN and S-NSSAI | Ericsson, CATT, Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, LG Electronics | Rel-18 | Revision of S2-2304108r06, merging S2-2305161 and S2-2304674. Approved | Agreed | |
| 9.8.2 | S2-2304444 | CR | Approval | 23.502 CR4009 (Rel-18, 'C'): KI#1 Address EN for LADN aspects for SMF | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305602. | Qianghua (Huawei) provides r01 Stefan (Ericsson) provides r02 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is OK with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305602 | CR | Approval | 23.502 CR4009R1 (Rel-18, 'C'): KI#1 Address EN for LADN aspects for SMF | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304444r02. Approved | Agreed | |
| 9.8.2 | S2-2304674 | CR | Approval | 23.501 CR4374 (Rel-18, 'F'): Clarification on LADN per DNN and S-NSSAI | LG Electronics | Rel-18 | Merged into S2-2305601 | Sang-Jun (Samsung) proposes to merge 4674 into 4108 as suggested offline. ==== Revisions Deadline ==== Hyunsook (LGE): it can be marked as 'Merged into 4108' ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2305161 | CR | Approval | 23.501 CR4509 (Rel-18, 'B'): Resolving the ENs on the LADN service area | ZTE | Rel-18 | Merged into S2-2305601 | Sang-Jun (Samsung) proposes to merge 5161 into 4108 as suggested offline. Zhendong (ZTE) is fine with the merge proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | - | - | - | KI#1: Paras than 5G VN group data | - | - | Docs:=4 | - | |
| 9.8.2 | S2-2304442 | CR | Approval | 23.502 CR4008 (Rel-18, 'F'): KI#1 Solve the EN about 5G VN group data parameter | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2305603. | Stefan (Ericsson) comments and provides r01 Qianghua (Huawei) provides r02 Stefan (Ericsson) provides comments Qianghua (Huawei) provides replies Stefan (Ericsson) replies to Qianghua Qianghua (Huawei) provides r03 ==== Revisions Deadline ==== Stefan (Ericsson) objects to all revisions. OK with r01 and r03 if the cover page is as follows: Reason for change 'It is not clear in the NEF Parameter Provisioning call flow that the parameters can be provided for a group of UEs.', Summary of change: 'Clarify that the External Group ID can be provided as a target UE identifier.', Consequences if not approved: 'Unclear specifications' Qianghua (Huawei) accepts Stefan's proposal to go r03 with updates of the cover page: Reason for change 'It is not clear in the NEF Parameter Provisioning call flow that the parameters can be provided for a group of UEs.', Summary of change: 'Clarify that the External Group ID can be provided as a target UE identifier.', Consequences if not approved: 'Unclear specifications' ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305603 | CR | Approval | 23.502 CR4008R1 (Rel-18, 'F'): KI#1 Solve the EN about 5G VN group data parameter | Huawei, HiSilicon | Rel-18 | Revision of S2-2304442r03. Approved | Agreed | |
| 9.8.2 | S2-2304826 | CR | Approval | 23.501 CR4410 (Rel-18, 'B'): KI#1: Other Group Attributes | Samsung | Rel-18 | r04 agreed. Revised to S2-2305604. | Liping Wu (CATT) provides r01. Stefan (Ericsson) provides r02 Qianghua (Huawei) provides r03. Sang-Jun (Samsung) is fine with r03. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is fine with r03, too Stefan (Ericsson) is not ok with r03 Qianghua (Huawei) provides r04. ==== Revisions Deadline ==== Stefan (Ericsson) OK with r02 and r04. Objects to r00, r01, r03. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) prefers r04, OK with r02, objects r00, r01, r03. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305604 | CR | Approval | 23.501 CR4410R1 (Rel-18, 'B'): KI#1: Other Group Attributes | Samsung, Huawei, HiSilicon | Rel-18 | Revision of S2-2304826r04. Approved | Agreed | |
| 9.8.2 | - | - | - | KI#1: DNN and S-NSSAI specific paras | - | - | Docs:=5 | - | |
| 9.8.2 | S2-2304604 | CR | Approval | 23.502 CR4037 (Rel-18, 'B'): Add the DNN and S-NSSAI specific Group Parameters in related group data | CATT | Rel-18 | r03 agreed. Revised to S2-2305605. | Stefan (Ericsson) has concerns with the CR Qianghua (Huawei) comments Liping Wu (CATT) responses to Qianghua (Huawei) and Stefan (Ericsson) and provides r01 Stefan (Ericsson) provides r02 Qianghua (Huawei) provides r03 ==== Revisions Deadline ==== Stefan (Ericsson) can accept r02 and r03. Objects to r00, r01 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) accepts r02, r03. Objects to r00, r01. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305605 | CR | Approval | 23.502 CR4037R1 (Rel-18, 'B'): Add the DNN and S-NSSAI specific Group Parameters in related group data | CATT, Huawei, HiSilicon | Rel-18 | Revision of S2-2304604r03. Approved | Agreed | |
| 9.8.2 | S2-2304675 | CR | Approval | 23.502 CR4048 (Rel-18, 'F'): Clarification on Nnef_ParameterProvision service operation | LG Electronics | Rel-18 | Approved | Agreed | |
| 9.8.2 | S2-2304827 | CR | Approval | 23.501 CR4411 (Rel-18, 'B'): KI#1: QoS for a group | Samsung | Rel-18 | r02 agreed. Revised to S2-2305606. | Stefan (Ericsson) provides questions Qianghua (Huawei) provides comments Sang-Jun (Samsung) responds to Qianghua (Huawei) and Stefan (Ericsson) Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Question for clarification Sang-Jun (Samsung) provides r01 and replies to Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Still one more clarification and proposal for a typo correction Stefan (Ericsson) provides follow-up question Qianghua (Huawei) provides comments and make a way proposal. Sang-Jun (Samsung) provides r02 accpeting proposals from Qianghua, Stefan and Georgies. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) r02 is ok still a proposal for a further improvement ==== Revisions Deadline ==== Sang-Jun (Samsung) replies to Georgios Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is OK with the proposals from Sang-Jun. Prefer a NOTE in one of the CCs. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305606 | CR | Approval | 23.501 CR4411R1 (Rel-18, 'B'): KI#1: QoS for a group | Samsung | Rel-18 | Revision of S2-2304827r02. Approved | Agreed | |
| 9.8.2 | - | - | - | KI#1: Group-MBR | - | - | Docs:=5 | - | |
| 9.8.2 | S2-2304602 | CR | Approval | 23.501 CR4357 (Rel-18, 'B'): Update the Group-MBR parameter for a group | CATT | Rel-18 | Merged into S2-2305607 | Qianghua (Huawei) proposes to merge this CR into 05163 based on offline discussion Liping Wu (CATT) agrees to merge this CR into 05163 based on offline discussion. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2305163 | CR | Approval | 23.501 CR4511 (Rel-18, 'F'): Clarification on the group-MBR | ZTE | Rel-18 | r03 agreed. Revised to S2-2305607, merging S2-2304602 | Stefan (Ericsson) provides r01 Qianghua (Huawei) provides r02 Liping Wu (CATT) provides r03 and merged part of 4604 into 5163. Sang-Jun (Samsung) corrects r03 may be from merging part of 4602 (not 4604) into 5163. ==== Revisions Deadline ==== Sang-Jun (Samsung) is fine with r03 and asks to add Samsung as co-signer Zhendong (ZTE) is fine with r03. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305607 | CR | Approval | 23.501 CR4511R1 (Rel-18, 'F'): Clarification on the group-MBR | ZTE, CATT, Samsung | Rel-18 | Revision of S2-2305163r03, merging S2-2304602. Approved | Agreed | |
| 9.8.2 | S2-2304845 | CR | Approval | 23.503 CR1006 (Rel-18, 'F'): Clarifications for monitoring the data rate per group | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305608. | Stefan (Ericsson) provides r01 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is ok with r01 Mirko (Huawei) provides r02. Stefan (Ericsson) ok with r02 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) ok with r02 ==== Revisions Deadline ==== Sang-Jun (Samsung) is fine with r02 and asks to add Samsung as co-signer Liping Wu (CATT) is fine with r02 and asks to co-sign. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305608 | CR | Approval | 23.503 CR1006R1 (Rel-18, 'F'): Clarifications for monitoring the data rate per group | Huawei, HiSilicon, Samsung, CATT | Rel-18 | Revision of S2-2304845r02. Approved | Agreed | |
| 9.8.2 | - | - | - | KI#3: group Provisioning, monitoring | - | - | Docs:=13 | - | |
| 9.8.2 | S2-2304111 | CR | Approval | 23.502 CR3965 (Rel-18, 'C'): Addressing Editor s note related to AF requested QoS for a group of UEs | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305609, merging S2-2304447 | Qianghua (Huawei) provides r01 Stefan (Ericsson) provides r03 (please ignore r02) ==== Revisions Deadline ==== Georgios Gkellas (Nokia, Nokia Shanghai-Bell) objects any revision of 4111 as it was agreed in CC#2 to follow a single QoS API as way forward Qianghua (Huawei) this CR addresses other critical technical open issues, independent from common/separate API issue, Besides that, no matter single API/common API, no one disagrees to use separate procedures. So objection of this CR prevents the GMEC progress. Suggests for CC#3. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305609 | CR | Approval | 23.502 CR3965R1 (Rel-18, 'C'): Addressing Editor s note related to AF requested QoS for a group of UEs | Ericsson | Rel-18 | Revision of S2-2304111r03, merging S2-2304447. Approved | Agreed | |
| 9.8.2 | S2-2304112 | CR | Approval | 23.503 CR0950 (Rel-18, 'C'): Updates to description of AF-requested QoS for a group | Ericsson | Rel-18 | Merged into S2-2304458 (Postponed) | Sang-Jun (Samsung) proposes to merge 4112 into 4458 as suggested offline. Ling (Siemens) has concerns with NOTE 2 in the CR Qianghua (Huawei) proposes to merge 4112 into 4448 Stefan (Ericsson) ok to merge into 4448 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.8.2 | S2-2304113 | CR | Approval | 23.501 CR4213 (Rel-18, 'C'): Updates to description of AF-requested QoS for a group | Ericsson | Rel-18 | Merged into S2-2305611 | Sang-Jun (Samsung) proposes to merge 4113 into 5162 as suggested offline. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2304446 | CR | Approval | 23.501 CR4312 (Rel-18, 'C'): KI#3 address the ENs about restructuring and the scenario without TSCTSF | Huawei, HiSilicon | Rel-18 | Merged into S2-2305611 | Sang-Jun (Samsung) proposes to merge 4446 into 5162 as suggested offline. Qianghua (Huawei) agrees the merge proposal ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2304447 | CR | Approval | 23.502 CR4010 (Rel-18, 'C'): KI#3 address the ENs about the scenario without TSCTSF | Huawei, HiSilicon | Rel-18 | Merged into S2-2305609 | Sang-Jun (Samsung) proposes to merge 4447 into 4111 as suggested offline. Qianghua (Huawei) agrees the merge proposal ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2304448 | CR | Approval | 23.503 CR0970 (Rel-18, 'C'): KI#3 address the ENs about restructuring and the scenario without TSCTSF | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2305610. | Stefan (Ericsson) provides r01 Stefan (Ericsson) provides r02 Ling (Siemens) provides r03 Qianghua (Huawei) provides r04 ==== Revisions Deadline ==== Georgios Gkellas (Nokia, Nokia Shanghai-Bell) objects any revision of 4448 as it was agreed in CC#2 to follow a single QoS API as way forward Qianghua (Huawei) this CR addresses other critical technical open issues, independent from common/separate issue, objection of this CR prevents the GMEC progress. Suggests for CC#3. ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305610 | CR | Approval | 23.503 CR0970R1 (Rel-18, 'C'): KI#3 address the ENs about restructuring and the scenario without TSCTSF | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304448r04. Approved | Agreed | |
| 9.8.2 | S2-2304456 | CR | Approval | 23.501 CR4317 (Rel-18, 'B'): The contribution removes ENs related to provisioning of traffic characteristics and monitoring of performance characteristics for a group of UEs | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2305611 | Sang-Jun (Samsung) proposes to merge 4456 into 5162 as suggested offline. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Replies to Sang-Jun Sang-Jun (Samsung) replies to Georgios Qianghua (Huawei) agrees to merge 4456 into 5162 as suggested by Sang-Jun Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees to merge 4456 to 5162 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2304457 | CR | Approval | 23.502 CR4012 (Rel-18, 'B'): Extend the Nnef_AFsessionWithQoS service operation to support provisioning of traffic characteristics and monitoring of performance characteristics for a group of UEs | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Qianghua (Huawei) objects to merge new GMEC NEF API into the AFSessionwithQoS/AIMLsys API and comments for a way forward Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Replies to Qianghua Sang-Jun (Samsung) also objects to merging new GMEC NEF API into the AFSessionwithQoS/AIMLsys API Qianghua (Huawei) sustains the objection to approve or endorse this CR given the reasons explained curing CC#1/#2 and emails. Zhendong (ZTE) share the same view with Huawei. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.8.2 | S2-2304458 | CR | Approval | 23.503 CR0972 (Rel-18, 'B'): Extend the Nnef_AFsessionWithQoS service operation to support provisioning of traffic characteristics and monitoring of performance characteristics for a group of UEs | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Qianghua (Huawei) objects to merge new GMEC NEF API into the AFSessionwithQoS/AIMLsys API and provides additional comments Georgios Gkellas (Nokia, Nokia Shanghai-Bell) Replies to Qianghua Sang-Jun (Samsung) also objects to merging new GMEC NEF API into the AFSessionwithQoS/AIMLsys API Qianghua (Huawei) sustains the objection to approve or endorse this CR given the reasons explained curing CC#1/#2 and emails, same for 4457 Zhendong (ZTE) share the same view with huawei. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides r01 ==== Revisions Deadline ==== Qianghua (Huawei) objects r00 and r01 of this CR. Independently from whether to merge, R00 and R01 loses a lot of progress we have made for the other open issues of KI#3 ==== Comments Deadline ==== | Postponed |
| 9.8.2 | S2-2305162 | CR | Approval | 23.501 CR4510 (Rel-18, 'F'): Resolving the ENs on the Provisioning and monitoring for a group | ZTE | Rel-18 | r06 agreed. Revised to S2-2305611, merging S2-2304456, S2-2304446 and S2-2304113 | Stefan (Ericsson) provides r01 Qianghua (Huawei) provides r02 Stefan (Ericsson) provides r03 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees with r03 and provides r04 cosigning as 4456 is merged in this one Qianghua (Huawei) provides r05 Ling (Siemens) provides r06 ==== Revisions Deadline ==== Zhendong (ZTE) both r05 and r06 are fine. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) prefers r06 ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305611 | CR | Approval | 23.501 CR4510R1 (Rel-18, 'F'): Resolving the ENs on the Provisioning and monitoring for a group | ZTE, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon | Rel-18 | Revision of S2-2305162r06, merging S2-2304456, S2-2304446 and S2-2304113. Approved | Agreed | |
| 9.8.2 | - | - | - | KI#4: Cross SMF 5G VN group comm. | - | - | Docs:=7 | - | |
| 9.8.2 | S2-2304428 | CR | Approval | 23.501 CR4306 (Rel-18, 'B'): Support for 5G VN group with multiple SMF(Set)s | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | r08 agreed. Revised to S2-2305612, merging S2-2304938 and S2-2304833 | Liping Wu (CATT) provides r01. Qianghua (Huawei) provides r02, merging part of 4449 into this CR Hiroshi (NEC) provides r03 to merge S2-2304938 into S2-2304428. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides r04 Qianghua (Huawei) provides r05 Stefan (Ericsson) provides r06 Qianghua (Huawei) provides replies Hiroshi (NEC) agree on r06, thank you for your updates. Stefan (Ericsson) replies to Qianghua Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees with r06 Qianghua (Huawei) OK with r06 and provides replies Qianghua (Huawei) provides r07 Stefan (Ericsson) provides r08 ==== Revisions Deadline ==== Sang-Jun (Samsung) is fine with r08 and asks to add Samsung as a co-signer ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305612 | CR | Approval | 23.501 CR4306R1 (Rel-18, 'B'): Support for 5G VN group with multiple SMF(Set)s | Ericsson, Nokia, Nokia Shanghai Bell, CATT, NEC, Huawei, HiSilicon, Samsung | Rel-18 | Revision of S2-2304428r08, merging S2-2304938 and S2-2304833. Approved | Agreed | |
| 9.8.2 | S2-2304449 | CR | Approval | 23.501 CR4313 (Rel-18, 'B'): KI#4 implementation of cross-SMF VN group communication | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2305613. | Qianghua (Huawei) provides r01, merging part of the CR into 4428 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides r02 Stefan (Ericsson) provides r03 Qianghua (Huawei) provides replies Stefan (Ericsson) provides r04 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees with r04 Qianghua (Huawei) provides r05 ==== Revisions Deadline ==== Sang-Jun (Samsung) is fine with r05 and asks to add Samsung as a co-signer ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305613 | CR | Approval | 23.501 CR4313R1 (Rel-18, 'B'): KI#4 implementation of cross-SMF VN group communication | Huawei, HiSilicon, Samsung | Rel-18 | Revision of S2-2304449r05. Approved | Agreed | |
| 9.8.2 | S2-2304606 | CR | Approval | 23.502 CR4038 (Rel-18, 'B'): 23.502: Add the function of multiple SMFs for VN group communication | CATT | Rel-18 | Noted | Qianghua (Huawei) provides r01 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) asks for a clarification Qianghua (Huawei) provides replies Stefan (Ericsson) comments and provides r02 Liping Wu(CATT) response to Georgios Gkellas (Nokia, Nokia Shanghai-Bell). Liping Wu(CATT) responses to Stefan (Ericsson) and provides r03 ==== Revisions Deadline ==== Stefan (Ericsson) provides questions Liping Wu (CATT) responses to Stefan (Ericsson) Stefan (Ericsson) objects to all versions, including r00 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) objects to all versions, too ==== Comments Deadline ==== Liping Wu(CATT) responses to Stefan (Ericsson) and ask to approve r02 | Noted |
| 9.8.2 | S2-2304833 | CR | Approval | 23.501 CR4412 (Rel-18, 'B'): KI#4: Multiple SMFs for 5G VN Communication | Samsung | Rel-18 | Merged into S2-2305612 | Qianghua (Huawei) proposes to merge the content of this CR into 4428/4449 Sang-Jun (Samsung) agrees to merge the content of this CR into 4428/4449 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | S2-2304938 | CR | Approval | 23.501 CR4440 (Rel-18, 'B'): Support for 5G VN group communication | NEC | Rel-18 | Merged into S2-2305612 | Sang-Jun (Samsung) proposes to merge 4938 into 4428 as suggested offline. Hiroshi (NEC) agree to merge 4938 into 4428. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.8.2 | - | - | - | KI#5 | - | - | Docs:=6 | - | |
| 9.8.2 | S2-2304450 | CR | Approval | 23.501 CR4314 (Rel-18, 'F'): KI#5 correction on the QoS support for UE with multiple groups | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305614. | Qianghua (Huawei) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305614 | CR | Approval | 23.501 CR4314R1 (Rel-18, 'F'): KI#5 correction on the QoS support for UE with multiple groups | Huawei, HiSilicon | Rel-18 | Revision of S2-2304450r01. Approved | Agreed | |
| 9.8.2 | S2-2304837 | CR | Approval | 23.501 CR4413 (Rel-18, 'B'): KI#5: Reference Correction for Group QoS | Samsung | Rel-18 | r01 agreed. Revised to S2-2305615. | Sang-Jun (Samsung) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305615 | CR | Approval | 23.501 CR4413R1 (Rel-18, 'B'): KI#5: Reference Correction for Group QoS | Samsung | Rel-18 | Revision of S2-2304837r01. Approved | Agreed | |
| 9.8.2 | S2-2305290 | CR | Approval | 23.501 CR4541 (Rel-18, 'B'): Update to Annex O to correct referenced clause number and add an optional condition for setup of the QoS flow | China Telecom | Rel-18 | r01 agreed. Revised to S2-2305616. | Qianghua (Huawei) provides r01 ==== Revisions Deadline ==== Heng(China Telecom) is also ok with r01 ==== Comments Deadline ==== | Revised |
| 9.8.2 | S2-2305616 | CR | Approval | 23.501 CR4541R1 (Rel-18, 'B'): Update to Annex O to correct referenced clause number and add an optional condition for setup of the QoS flow | China Telecom | Rel-18 | Revision of S2-2305290r01. Approved | Agreed | |
| 9.8.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=11 | - | |
| 9.8.2 | S2-2304109 | CR | Approval | 23.502 CR3964 (Rel-18, 'C'): SMF awareness of LADN per DNN and S-NSSAI | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304443 | CR | Approval | 23.501 CR4310 (Rel-18, 'C'): KI#1 Address EN for LADN aspects for SMF | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304445 | CR | Approval | 23.501 CR4311 (Rel-18, 'C'): KI#1 Address EN for LADN aspects for AMF | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304455 | CR | Approval | 23.501 CR4316 (Rel-18, 'B'): LADN service area clarifications for enhanced group attribute management | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304110 | CR | Approval | 23.501 CR4212 (Rel-18, 'C'): Resolving open issue on NEF parameter provisioning for GMEC | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304441 | CR | Approval | 23.501 CR4309 (Rel-18, 'F'): KI#1 Solve the EN about 5G VN group data parameter | Huawei, HiSilicon | Rel-18 | Stefan (Ericsson) comments and provides r01 | NOT HANDLED | |
| 9.8.2 | S2-2304603 | CR | Approval | 23.503 CR0983 (Rel-18, 'B'): Update the Group-MBR parameter for a group | CATT | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304825 | CR | Approval | 23.501 CR4409 (Rel-18, 'B'): KI#1: Group MBR Support | Samsung | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304830 | CR | Approval | 23.503 CR1000 (Rel-18, 'B'): KI#1: Group MBR Support | Samsung | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304844 | CR | Approval | 23.501 CR4414 (Rel-18, 'F'): Clarifications for monitoring the data rate per group | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.8.2 | S2-2304605 | CR | Approval | 23.501 CR4358 (Rel-18, 'B'): Add the function of multiple SMFs for VN group communication | CATT | Rel-18 | NOT HANDLED | ||
| 9.9.1 | - | - | - | Study on System Support for AI/ML-based Services (FS_AIMLsys) | - | - | Docs:=0 | - | |
| 9.9.2 | - | - | - | System Support for AI/ML-based Services (AIMLsys) | - | - | Docs:=87 | - | |
| 9.9.2 | - | - | - | General & LS In / Out | - | - | Docs:=10 | - | |
| 9.9.2 | S2-2303965 | LS In | Action | Reply LS on KPIs for AI/ML model transfer in 5GS | SA WG1 (S1-230324) | Rel-18 | Noted | Noted | |
| 9.9.2 | S2-2304265 | LS OUT | Approval | [DRAFT] LS on charging aspects of AI/ML traffic | Samsung | Rel-18 | r00 agreed. Revised to S2-2305426. | Revised | |
| 9.9.2 | S2-2305426 | LS OUT | Approval | LS on charging aspects of AI/ML traffic | SA WG2 | Rel-18 | Revision of S2-2304265r00. Approved | Approved | |
| 9.9.2 | S2-2304067 | LS OUT | Approval | LS for improved KPIs involving end-to-end data volume transfer time analytics | SA WG2 | Rel-18 | Approved | Zhang (Ericsson) ask clarification ==== Revisions Deadline ==== ==== Comments Deadline ==== | Approved |
| 9.9.2 | S2-2305238 | CR | Approval | 23.501 CR4192R1 (Rel-18, 'F'): High level feature description for AIMLsys | Ericsson, Samsung | Rel-18 | Revision of S2-2304037. r10 agreed. Revised to S2-2305430, merging S2-2305378 Proposed to be used as the baseline to merge with S2-2305378 | Tricci (OPPO) thanks Ericsson and Samsung for the CR and proposes to merge OPPO's S2-2305378 into this CR S2-2305238 by providing r01. David (Samsung) provides comments and r02 Belen (Ericsson) provides r03 David (Samsung) replies to Ericsson, provides r04 Tricci (OPPO) thanks David (Samsung) and Belen (Ericsson) update of the revisions. OPPO has more questions towards Samsung changes and will provide more further update once the questions are answered. Bahador (NTT DOCOMO) provides a comment. David (Samsung) replies to NTT Docomo and OPPO, provides r05 Tricci (OPPO) thanks David (Samsung) reply and accepts OPPO's comments. OPPO provides r06 to further clean up the EN. Tricci (OPPO) thanks Bahador (NTT DOCOMO) comment and can accept to remove the Distributed term from the general clause. Bahador (NTT DOCOMO) replies to David (Samsung) and Tricci (OPPO) Dongjoo (Nokia) asks a question and spots a typo. David (Samsung) provides r07 and comments Dongjoo (Nokia) is fine with r07. Belen (Ericsson) provides r08 Tricci (OPPO) provides r09 to replace Consolidated MBR by Consolidated MDR. David (Samsung) provides r10 deleting one outstanding instance of 'Distributed' learning in the description ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305430 | CR | Approval | 23.501 CR4192R2 (Rel-18, 'F'): High level feature description for AIMLsys | Ericsson, Samsung, OPPO | Rel-18 | Revision of S2-2305238r10, merging S2-2305378. Approved | Agreed | |
| 9.9.2 | S2-2305378 | CR | Approval | 23.501 CR4564 (Rel-18, 'F'): 23.501 General Clause Update for AIMLsys | OPPO | Rel-18 | Merged into S2-2305430 Proposed to merge this CR with S2-2305238 | David (Samsung) believes this paper has been merged into S2-2305238 Tricci (OPPO) thanks David (Samsung) and confirms this paper has been merged into S2-2305238 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304037 | CR | Approval | 23.501 CR4192 (Rel-18, 'F'): High level feature description for AIML | Ericsson, Samsung | Rel-18 | CR Cover sheet error! Revised to S2-2305238 | Revised | |
| 9.9.2 | S2-2304254 | CR | Approval | 23.501 CR4255 (Rel-18, 'F'): R18 AIMLsys_General_23501 CR_EN on AIML traffic | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2305431. | David (Samsung) comments and provides r01 Dongjoo (Nokia) thanks David (Samsung) for providing r01 and is fine with it. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305431 | CR | Approval | 23.501 CR4255R1 (Rel-18, 'F'): R18 AIMLsys_General_23501 CR_EN on AIML traffic | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304254r01. Approved | Agreed | |
| 9.9.2 | - | - | - | Key Issue #1: Monitoring of network resource utilization for support of Application AI/ML operations | - | - | Docs:=16 | - | |
| 9.9.2 | S2-2304258 | CR | Approval | 23.501 CR4257 (Rel-18, 'F'): R18 AIMLsys_KI1_23501 CR_SingleSO_for_QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Agreed | |
| 9.9.2 | S2-2304259 | CR | Approval | 23.502 CR3981 (Rel-18, 'F'): R18 AIMLsys_KI1_23502 CR_SingleSO_for_QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Check Affected Clauses! r03 + changes agreed Revised to S2-2305432. | Dongjoo (Nokia) provides r01 merging S2-2304457 in based on the SoH taken at CC#2 Tricci (OPPO) thanks Dongjoo (Nokia) provides revision of the merging API CR and provides r02 to suggest the way forward for the merging. Dongjoo (Nokia) provides r03 Dongjoo (Nokia) provides r04 Dongjoo (Nokia) provides r05 ==== Revisions Deadline ==== Dongjoo (Nokia); This CR needs to be discussed for CC#3 along with S2-2304257. Tricci (OPPO) corrects the agenda# to AI#4.1 for this email thread since Dario has already correct it once for us. Tricci (OPPO) would like to let Dongjoo (Nokia) to know that, this CR has now moved to agenda AI#4.1 as suggested in CC#2. Mirko (Huawei) objects to all versions of this CR. Tricci (OPPO) respectfully disagrees with Mirko (Huawei) objection, and your objection will also block the progress of other CR S2-2304039 which has already updated to align with this CR according to the decision in CC#2. Mirko (Huawei) responds to Tricci (OPPO) that other CRs are not blocked. Belen (Ericsson) provides comments, objects to this contribution Dongjoo (Nokia) provides a draft revision on top of r05 based on the discussion in CC#3. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305432 | CR | Approval | 23.502 CR3981R1 (Rel-18, 'F'): R18 AIMLsys_KI1_23502 CR_SingleSO_for_QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304259r03 + changes. Approved | Agreed | |
| 9.9.2 | S2-2305042 | CR | Approval | 23.502 CR4100 (Rel-18, 'F'): Define a single API for Multi-member AF session request QoS procedure | QUALCOMM JAPAN LLC. | Rel-18 | Noted | Dongjoo (Nokia) provides comments and asks questions. Juan Zhang (Qualcomm) suggests to wait for the discussion and decision in 4.1 and we can discuss the details for CR. Dongjoo (Nokia) proposes to NOTE this CR based on the SoH result. Belen (Ericsson) also proposes to NOTE this CR based on the SoH result. Juan Zhang (Qualcomm) agrees to note the CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.9.2 | S2-2305048 | CR | Approval | 23.501 CR4471 (Rel-18, 'F'): Define a single API for Multi-member AF session request QoS procedure | QUALCOMM JAPAN LLC. | Rel-18 | Noted | Dongjoo (Nokia) provides comments. Juan Zhang (Qualcomm) suggests to wait for the discussion and decision in 4.1 and we can discuss the details for CR. Dongjoo (Nokia) proposes to NOTE this CR based on the SoH result. Belen (Ericsson) also proposes to NOTE this CR based on the SoH result. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) agrees to note the CR. ==== Comments Deadline ==== | Noted |
| 9.9.2 | S2-2305056 | DISCUSSION | Discussion | Clean up the Multi-member AF session with required QoS for a list of UEs procedure | QUALCOMM JAPAN LLC. | Rel-18 | Noted | Tricci (OPPO) thanks Juan (Qualcomm) for the DP to describe the proposed changes in the companion CRs. OPPO would like to respond. Juan Zhang (Qualcomm) replies to Tricci (OPPO). Tricci (OPPO) thanks Juan Zhang (Qualcomm) reply and provides further responses. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.9.2 | S2-2305058 | CR | Approval | 23.502 CR4102 (Rel-18, 'F'): Clean up the Multi-member AF session with required QoS for a list of UEs procedure | QUALCOMM JAPAN LLC. | Rel-18 | Merged into S2-2306246 Merge into (revision of) S2-2304039 | Tricci (OPPO) thanks Juan (Qualcomm) proposal and suggests it to be merged into S2-2304039 (from Ericsson) based on the additional comments from OPPO below. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304039 | CR | Approval | 23.502 CR3954 (Rel-18, 'B'): Solving ENs in the Procedures for Consolidated-MBR Monitoring | Ericsson | Rel-18 | CC#4: r10 + changes agreed. Revised to S2-2306246, merging S2-2305058, S2-2305381, S2-2304759, S2-2304885 and S2-2304695. Proposed to be used as the baseline to be merged with S2-2305058, S2-2305381, S2-2304759, S2-2304885 | Belen (Ericsson) provides r01, it merges with S2-2305381, S2-2304759 <ftp://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_156E_Electronic_2023-04/Docs/S2-2304759.zip> , S2-2304885. Belen (Ericsson) provides r02. Tricci (OPPO) thanks Belen (Ericsson) provides merged revision. OPPO provides r04 to restore the correct term of Consolidated MBR and does not agree to rename Consolidated MBR to Consolidated Data Rate because the term is related to maximum threshold. OPPO provides also some minor corrections. Jihoon (ETRI) provides comments. Tricci (OPPO) thanks Jihoon (ETRI) comments and provides feedback. Tricci (OPPO) apologizes for sharing the wrong r03 version before, r04 version should be the latest. Juan Zhang (Qualcomm) provides comments. Tricci (OPPO) thanks Juan Zhang (Qualcomm) comments and provides further responses. Tricci (OPPO) corrects some typos in previous email. Belen (Ericsson) provides r05. Dongeun (Samsung) comments Tricci (OPPO) thanks Belen (Ericsson) prepared r05 and still reading it and may provide comment later, but would like to respond to Belen's question first on the definition of Consolidated MBR. Tricci (OPPO) responds to Juan (Qualcomm) comments and have the concern that Juan does not fully understand the purpose of the new API here is to support aggregated AF session for a list of UEs. Tricci (OPPO) responds to Juan Zhang (Qualcomm) comments and believe that Tricci (OPPO) thanks Jihoon (ETRI) comments/suggestions and provides feedback. Dongjoo (Nokia) provides r06 based on the result of the SoH taken at CC#2 Jihoon (ETRI) provides r07. Juan Zhang (Qualcomm) replies to Tricci (OPPO) comments and have a concern that Tricci does not fully understand my comments. Jihoon (ETRI) replies to Tricci (OPPO). Belen (Ericsson) provides r08. Juan Zhang (Qualcomm) supports r08. Mirko (Huawei) comments. Tricci (OPPO) thanks Mirko (Huawei) comments and provides feedback and r09. Tricci (OPPO) fixes the typos from previous email, no new revision this time. Sorry... Dongeun (Samsung) provides r10 ? ==== Revisions Deadline ==== Tricci (OPPO) accepts r09 or r10. ? Juan Zhang (Qualcomm) is OK with r10. ? Dongeun (Samsung) suggest to approve r10 in this meeting and asks to add Samsung in co-source list. ? Tricci (OPPO) restores the email title of this thread which has been cut-off and updates OPPO's position on this CR. OPPO can accept r09 or r10 with the removal of the text related to the partial resource allocation of the UE corresponding to the alternative QoS. ? Mirko (Huawei) responds and proposes further updates. ==== Comments Deadline ==== Belen (ericsson) provides r11 Tricci (OPPO) thanks Belen (ericsson) hardwork to clean up the text and provides r11. OPPO is okay with r11 but has two questions. Belen (ericsson) provides r12 | Revised |
| 9.9.2 | S2-2306246 | CR | Approval | 23.502 CR3954R1 (Rel-18, 'B'): Solving ENs in the Procedures for Consolidated-MBR Monitoring | Ericsson, Huawei, ETRI, OPPO, Samsung | Rel-18 | Revision of S2-2304039r10 + changes, merging S2-2305058, S2-2305381, S2-2304759, S2-2304885 and S2-2304695. CC#4: Approved | Agreed | |
| 9.9.2 | S2-2305381 | CR | Approval | 23.502 CR4158 (Rel-18, 'F'): Update 23.502 for Multi-member AF session | OPPO | Rel-18 | Merged into S2-2306246 Merge into (revision of) S2-2304039 | Tricci (OPPO) agrees to merge 5381 into Ericsson's 4039. ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304759 | CR | Approval | 23.502 CR4065 (Rel-18, 'B'): Update on Multi-member AF session with required QoS for a list of UEs | ETRI | Rel-18 | Merged into S2-2306246 Merge into (revision of) S2-2304039 | Tricci (OPPO) thanks ETRI's CR and proposes to merge the procedures in clauses 4.15.6.13, 4.15.6.13.1 to 4.15.6.13.3 into Ericsson's CR (S@-2304039) and just keeps the service API part in this CR, i.e. all clauses within 5.2.6.31. OPPO provides additional comments for clause 5.2.6.31.5 below. Jihoon (ETRI) agrees with the proposal by Tricci (OPPO). Tricci (OPPO) thanks Jihoon (ETRI) kind acceptance for OPPO's proposed changes to NOTE 5, and requests ETRI to include OPPO as the supporting company when producing the next revision. Belen (Ericsson) replies to OPPO Dongjoo (Nokia) asks a question on SO updates. Jihoon (ETRI) replies to Dongjoo (Nokia) and clarifies this CR to be merged into S2-230429. Dongjoo (Nokia) asks a f/up question. Jihoon (ETRI) replies to Dongjoo (Nokia) and corrects wrong information in the previous email. This CR has been merged into S2-2304039. Dongjoo (Nokia) replies to Jihoon (ETRI) that the clarification is well understood. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304885 | CR | Approval | 23.502 CR4083 (Rel-18, 'F'): Update the procedures of group QoS request | Huawei, HiSilicon | Rel-18 | Merged into S2-2306246 Merge into (revision of) S2-2304039 | Tricci (OPPO) thanks Huawei CR and proposes to merge Huawei's S2-2304885 into Ericsson's CR (S2-2304039) with the following additional comments from OPPO. Wang Yuan (Huawei) is ok to merge S2-2304885 into S2-2304039 and discuss the technical issues in the thread S2-2304039. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304695 | CR | Approval | 23.502 CR4056 (Rel-18, 'B'): CR 23502 CMBR event exposure in UPF | vivo | Rel-18 | Merged into S2-2306246 Merge into (revision of) S2-2304039 | Tricci (OPPO) thanks vivo for the CR, however, OPPO does not think the proposal from vivo described in this CR would work. Huazhang (vivo) reply to Tricci (OPPO), and provides r01 Tricci (OPPO) thanks Huazhang(vivo) kind clarifications and the update of r01. The intent of the proposed changes from vivo overlaps the CR prepared by Ericsson (S2-2304039) and hence, OPPO proposes vivo's CR to be merged into Ericsson's CR. Belen (Ericsson) objects to this CR. Belen (Ericsson) objects to the initial revision, also agree to merge r01 and S2-2304039. Huazhang (vivo) agree to merge r01 to S2-2304039 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304821 | CR | Approval | 23.501 CR4408 (Rel-18, 'B'): NEF capability for the new AIML service | Samsung | Rel-18 | r01 agreed. Revised to S2-2305433. | Tricci (OPPO) thanks Samsung for the CR to update the UE capability and would like to cosign the CR. Tricci (OPPO) apologizes for the typo in previous comment. It should be NEF capability and not the UE capability. OPPO still would like to cosign. Thanks. Dongjoo (Nokia) comments that this CR needs to be kept open until the decision on whether to combine the related APIs or not is made. Dongjoo (Nokia) provides comments. Dongeun (Samsung) provides r01 Dongjoo (Nokia) is fine with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305433 | CR | Approval | 23.501 CR4408R1 (Rel-18, 'B'): NEF capability for the new AIML service | Samsung, OPPO | Rel-18 | Revision of S2-2304821r01. Approved | Agreed | |
| 9.9.2 | S2-2304366 | CR | Approval | 23.502 CR3995 (Rel-18, 'F'): Correct the error usage of '5GS latency' | China Mobile | Rel-18 | CR Cover sheet error! Noted | Dongjoo (Nokia) provides comments and asks questions. Dan (China Mobile) provides reply and provide r01, the other change can be merged into 4039. Dongjoo (Nokia) is fine with r01. Mirko (Huawei) comments that Requested 5GS Delay has to be kept in the AF request. Dan (China Mobile) do not agree with the requested 5GS delay understanding. ==== Revisions Deadline ==== Mirko (Huawei) objects to all versions of the CR because the delay requirement has to be kept in the AF request. ==== Comments Deadline ==== | Noted |
| 9.9.2 | - | - | - | Key Issue #4: Enhancing External Parameter Provisioning | - | - | Docs:=5 | - | |
| 9.9.2 | S2-2304040 | CR | Approval | 23.502 CR3955 (Rel-18, 'B'): Update to external parameter provisioning for expected UE behaviour | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305434. Proposed as baseline for clauses 4.15.6.3, 4.15.6.3x (new), 5.2.3.6.1, 5.2.3.6.2 | Dongjoo (Nokia) asks questions. Mehrdad (Mediatek Inc.) requests to mark how the change affects different entities. Zhang (Ericsson) response to Dongjoo (Nokia) Dongjoo (Nokia) provide feedback to Zhang (Ericsson). Zhang (Ericsson) provide r01 David (Samsung) provides r02 and comments. Dongjoo (Nokia) responds to Zhang (Ericsson). Dongjoo (Nokia) provides comments. David (Samsung) comments. Dongjoo (Nokia) provides r03. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305434 | CR | Approval | 23.502 CR3955R1 (Rel-18, 'B'): Update to external parameter provisioning for expected UE behaviour | Ericsson, Samsung | Rel-18 | Revision of S2-2304040r03. Approved | Agreed | |
| 9.9.2 | S2-2304260 | CR | Approval | 23.502 CR3982 (Rel-18, 'B'): R18 AIMLsys_KI4_23502 CR for clarification on parameter provisioning | Nokia, Nokia Shanghai Bell | Rel-18 | r05 + changes agreed. Revised to S2-2305435, merging S2-2304267. Proposed as baseline for clause 4.15.6.2 | David (Samsung) provides r01, merging S2-2304267 into S2-2304260 and providing additional changes and comments Dongjoo (Nokia) provides r02, reflecting the received comments and responds to David(Samsung) David (Samsung) would like to co-sign, provides r03 with just formatting corrections Dongjoo (Nokia) is fine with r03 provided by David (Samsung) Juan Zhang (Qualcomm) askes question for clarification. Dongjoo (Nokia) answers to the question from Juan (Qualcomm). Zhang (Ericsson) provides comments Dongjoo (Nokia) provides feedback to Zhang (Ericsson). David (Samsung) agrees with Nokia. Dongjoo (Nokia) agrees with David (Samsung). David (Samsung) kindly requests an updated from Zhang (Ericsson). Mehrdad (Mediatek Inc.) thinks NOTE 5 wording is rather normative. Dongjoo (Nokia) provides r04. Zhang (Ericsson) provides r05 Dongjoo (Nokia) object r05. ==== Revisions Deadline ==== Dongjoo (Nokia) suggests approving r05 plus an EN 'How NEF determines which value to take when multiple values of one parameter are provisioned to 5GC is FFS'. Zhang (Ericsson) only accept r05 and object all other versions Dongjoo (Nokia) proposes rewording of the proposed EN. Zhang (Ericsson) is OK to add an EN on top of r05: EN: It is FFS Whether it makes sense that multiple AFs can provide to the expected UE behaviors of the same UE. Dongjoo (Nokia) accepts the EN proposed by Zhang (Ericsson) for the sake of progress. David (Samsung) thanks Zhang and Dongjoo for the agreement, is also OK with the proposed EN on top of r05. Dongjoo (Nokia) confirms that we are fine with r05 + EN: It is FFS Whether it makes sense that multiple AFs can provide to the expected UE behaviors of the same UE. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305435 | CR | Approval | 23.502 CR3982R1 (Rel-18, 'B'): R18 AIMLsys_KI4_23502 CR for clarification on parameter provisioning | Nokia, Nokia Shanghai Bell, Samsung | Rel-18 | Revision of S2-2304260r05 + changes, merging S2-2304267. Approved | Agreed | |
| 9.9.2 | S2-2304267 | CR | Approval | 23.502 CR3984 (Rel-18, 'F'): Confidence levels clarification in external parameter provisioning | Samsung | Rel-18 | Merged into S2-2305435 Proposed to be merged into S2-2304260 | David (Samsung) confirms this CR has now been merged into S2-2304260 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | - | - | - | Key Issue #5: 5GC Enhancements to enable Application AI/ML Traffic Transport | - | - | Docs:=8 | - | |
| 9.9.2 | S2-2304697 | CR | Approval | 23.502 CR4057 (Rel-18, 'B'): PDTQ policy renegotiation, PDTQ storage and parameter enhancement in PDTQ create request | vivo | Rel-18 | r06 agreed. Revised to S2-2305436. Proposed to be used as the baseline to be merged with S2-2304887 | Wang Yuan (Huawei) provides comments. Jungshin (Samsung) provides comments Belen (Ericsson) provides comments Huazhang (vivo) reply to Yuan Huazhang (vivo) reply to Jungshin Huazhang (vivo) reply to Belen Huazhang (vivo) provides r01 Tricci (OPPO) shares the similar concern as Wang Yuan (Huawei) except for the 2nd change from vivo Tricci (OPPO) requests Huazhang (vivo) to refer the earlier OPPO's response for this CR. Only the 2nd change that OPPO can support. Thanks. Jungshin (Samsung) provides further comments Huazhang (vivo) thanks Tricci for your comments, I will provide the revision later. Jungshin (Samsung) provides response to Huazhang (Vivo) Huazhang (vivo) provide r02 and reply to Jungshin Wang Yuan (Huawei) provides comments on r02 and proposes to merge the changes in clause 5.2.12.2.1 into S2-2304887. Huazhang (vivo) provides r03 to reflect the comments from Yuan Tricci (OPPO) thanks and supports Huazhang (vivo) update. OPPO provides r04 with some editorial update and also clean up to remove changes over changes as well as to add OPPO as the supporting companies. Huazhang (vivo) thanks Tricci for the revision, Huazhang is ok for this revision Belen (Ericsson) provides r05, comments. Huazhang (vivo) thanks Belen for the revision, and want to confirm that you want to undo the changes in 4.16.15.1 right? Huazhang (vivo) provides r06 on top of r05, that undo the change 1 (the change 1 is delete the whole paragraph of 4.16.15.1) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305436 | CR | Approval | 23.502 CR4057R1 (Rel-18, 'B'): PDTQ policy renegotiation, PDTQ storage and parameter enhancement in PDTQ create request | Vivo, OPPO, Ericsson | Rel-18 | Revision of S2-2304697r06. Approved | Agreed | |
| 9.9.2 | S2-2304887 | CR | Approval | 23.502 CR4084 (Rel-18, 'F'): Update the procedures for PDTQ policy | Huawei, HiSilicon | Rel-18 | r03 + changes agreed. Revised to S2-2305437. Proposed to be merged into S2-2304697 | Tricci (OPPO) thanks Yuan (Huawei) prepared the CR and prepared r01 to correct steps 8 & 9 in clause 4.16.15.2.1. OPPO also requests Huawei to provide editable figures in the updated CR which are replaced by Huawei. Wang Yuan (Huawei) replies to Tricci (OPPO) and provides r02. Jungshin (Samsung) provides comments Tricci (OPPO) thanks Jungshin (Samsung) comments and provides response. Jungshin (Samsung) provide response to Tricci (OPPO) Tricci (OPPO) thanks Jungshin (Samsung) further clarifications and agrees with Jungshin. Thanks.. Wang Yuan (Huawei) provides r03 to reflect the comments from Jungshin (Samsung). Belen (Ericsson) provides comments on r03, and applies to other revisions, Wang Yuan (Huawei) replies to Belen (Ericsson). ==== Revisions Deadline ==== Belen (Ericsson) can only agree on r03 if the first change 4.16.5.2 is removed. Wang Yuan (Huawei) replies to Belen (Ericsson) and accepts to remove the first change from r03. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305437 | CR | Approval | 23.502 CR4084R1 (Rel-18, 'F'): Update the procedures for PDTQ policy | Huawei, HiSilicon | Rel-18 | Revision of S2-2304887r03 + changes. Approved | Agreed | |
| 9.9.2 | S2-2304698 | CR | Approval | 23.503 CR0990 (Rel-18, 'B'): CR 23503 PDTQ policy renegotiation procedure | vivo | Rel-18 | Merged into S2-2305438 Proposed to be merged into S2-2304888 | Tricci (OPPO) thanks vivo's CR, however, OPPO has fundamental concern regarding to leverage the Nnef_PDTQPolicyNegotiation_Update to make changes to the selected PDTQ policy which is not the right approach. Wang Yuan (Huawei) shares the same concern with Tricci (OPPO). Jungshin (Samsung): We also have the same view as OPPO and Huawei and would request clarification. Belen (Ericsson) states that the proposed text is not related to the removed Editor´s Note, the CR cannot be accepted. ==== Revisions Deadline ==== Huazhang (vivo) hope to merge this paper to S2-2304888, as in the tdoc handling list ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304888 | CR | Approval | 23.503 CR1009 (Rel-18, 'B'): Updates on PDTQ policy | Huawei, HiSilicon | Rel-18 | r06 agreed. Revised to S2-2305438, merging S2-2305365 and S2-2304698 Proposed to be used as the baseline to be merged with S2-2304698 | Tricci (OPPO) thanks Huawei for the CR and proposes to merge S2-2305365 (from InterDigital) into S2-2304888 (from Huawei). OPPO would like to ask for clarifications. Wang Yuan (Huawei) replies to Tricci (OPPO). Belen (Ericsson) provides comments. Wang Yuan (Huawei) replies to Belen (Ericsson) and provides r01. Tricci (OPPO) thanks Yuen (Huawei) reply but still have question and would like to ask for further clarifications. Tricci (OPPO) thanks Yuen (Huawei) further clarifications but disagrees that there is no need for PCF/ASP interaction if the ASP has permitted PDTQ policy re-negotiated. Tricci (OPPO) provides r03 to clarify the PCF/ASP interaction if the AF has permitted PDTQ policy re-negotiated. Jungshin (Samsung) ask for clarification on changes in r03 Belen (Ericsson) comments on r03 Jungshin (Samsung) provides r04 Mirko (Huawei) comments. Wang Yuan (Huawei) provides comments and r05 and r06. Ulises Olvera (InterDigital Inc.) provides comments, we are OK with either revision (r05 or r06), but prefer r05. ==== Revisions Deadline ==== Tricci (OPPO) thanks Yuan (Huawei) to provide the two new revisions and apologizes for the late comments. Tricci (OPPO) can accept r06 but undo the removal of Samsung's clarification for the option to notify the AF proposed in r04. Thanks. Tricci (OPPO) can accept r06 only if r06 is revised to undo the removal of Samsung's clarification for the option to notify the AF proposed in r04. Thanks. Jungshin (Samsung): We can accept r05 or r06. Wang Yuan (Huawei) asks Tricci (OPPO) for clarification. Tricci (OPPO) responds to Wang Yuan (Huawei) and would like to accept r06 as-is after verifying the Samsung sentence is there. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305438 | CR | Approval | 23.503 CR1009R1 (Rel-18, 'B'): Updates on PDTQ policy | Huawei, HiSilicon | Rel-18 | Revision of S2-2304888r06, merging S2-2305365 and S2-2304698. Approved | Agreed | |
| 9.9.2 | S2-2305365 | CR | Approval | 23.503 CR1039 (Rel-18, 'B'): Re-negotiation of PDTQ time window | InterDigital, Europe, Ltd. | Rel-18 | Merged into S2-2305438 Proposed to be merged into S2-2304888 | Tricci (OPPO) thanks Ulises (InterDigital) for the CR and proposes to merge this CR S2-2305365 into Huawei's CR S2-2304888. Please kindly consider. Many thanks. Wang Yuan (Huawei) proposes to merge this CR into S2-2304888 and asks for clarification, suggests to further discuss in thread of 4888. Belen (Ericsson) is okay with the proposal to merge into 4888, but comments that periodic reporting is a valid option too. Ulises Olvera (InterDigital Inc.) agrees to merge S2-2305365 into S2-2304888 but the merge should include the periodic reporting request, as this is a valid option too, we provide r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | - | - | - | Key Issue #6: QoS and Policy enhancements | - | - | Docs:=7 | - | |
| 9.9.2 | S2-2304261 | CR | Approval | 23.502 CR3983 (Rel-18, 'B'): R18 AIMLsys_KI6_23502 CR for adding timing info for AF QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Bahador (NTT DOCOMO) requests for clarification. Bahador (NTT DOCOMO) resends with correct AI in the subject. Dongjoo (Nokia) provide feedback to Bahador (NTT DOCOMO). Bahador (NTT DOCOMO) replies to Dongjoo (Nokia) Dongjoo (Nokia) provides feedback to Bahador (NTT DOCOMO) Mirko (Huawei) comments and is still not convinced that the proposal is beneficial from an overall system perspective. Dongjoo (Nokia) provides feedback to Mirko (Huawei) Belen (Ericsson) don't think adding timing info is required, provides comments. Dongjoo (Nokia) provides feedback to Belen (Ericsson) Belen (Ericsson) replies to Nokia Dongjoo (Nokia) replies to Belen (Ericsson) Dongjoo (Nokia) provides r01. ==== Revisions Deadline ==== Dongjoo (Nokia) suggest approving r01 plus an EN 'The benefits versus disadvantages of adding the timing information are FFS'. Dongjoo (Nokia) requests this CR to be discussed in CC#3. Tao(VC) further check the view of r01 Mirko (Huawei) objects to all versions of this CR. Dongjoo (Nokia) proposes to Postpone this CR. ==== Comments Deadline ==== | Postponed |
| 9.9.2 | S2-2304262 | CR | Approval | 23.503 CR0960 (Rel-18, 'B'): R18 AIMLsys_KI6_23503 CR for adding timing info for AF QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Belen (Ericsson) don't think adding timing info is required, provides comments. Dongjoo (Nokia) provides r02 Mirko (Huawei) responds. Dongjoo (Nokia) responds to Mirko (Huawei) ==== Revisions Deadline ==== Dongjoo (Nokia) suggest approving r02 plus an EN 'The benefits versus disadvantages of adding the timing information are FFS'. Dongjoo (Nokia) requests this CR to be discussed in CC#3. Tao(VC) further check with Mirko and Belen whether latest proposal of Dongjoo (Nokia) is ok or not. Belen (Ericsson) objects to this CR, all revisions. Mirko (Huawei) objects to all versions of this CR. Dongjoo (Nokia) replied to Belen (Ericsson). Dongjoo (Nokia) proposes to Postpone this CR. ==== Comments Deadline ==== | Postponed |
| 9.9.2 | S2-2304286 | DISCUSSION | Discussion | Discussion on standardised 5QI for AIML-based services | Samsung | Noted | Noted | ||
| 9.9.2 | S2-2304285 | CR | Approval | 23.501 CR4261 (Rel-18, 'B'): Standardised 5QI for AIML-based services | Samsung, OPPO | Rel-18 | Merged into S2-2305439 | Dongjoo (Nokia) propose to NOTE this CR. Tingyu (Samsung) replies to Dongjoo (Nokia). Dongjoo (Nokia) replies to Tingyu (Samsung). Tingyu (Samsung) merged this CR into S2-2305055. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2305051 | DISCUSSION | Discussion | Discussion on 5QIs to support AIML service | QUALCOMM JAPAN LLC. | Rel-18 | Noted | Noted | |
| 9.9.2 | S2-2305055 | CR | Approval | 23.501 CR4473 (Rel-18, 'F'): 5QI for AIML services | QUALCOMM JAPAN LLC. | Rel-18 | r05 agreed. Revised to S2-2305439, merging S2-2304285 | Dongjoo (Nokia) generally support this CR but asks for a revision. Mehrdad (Mediatek Inc.) comments Tingyu (Samsung) provides comments. Yang (OPPO) comments Juan Zhang (Qualcomm) provides comments. Dongjoo (Nokia) provides comments. Dongjoo (Nokia) asks f/up questions to Juan (Qualcomm) Juan Zhang (Qualcomm) replies to Dongjoo (Nokia) Juan Zhang (Qualcomm) replies to Tingyu (Samsung). Mehrdad (Mediatek Inc.) requests some revisions. Serge (T-Mobile USA) provides supportive comments. Belen (Ericsson) supports this proposal Tingyu (Samsung) provides r01 with merging S2-2304285 into this CR, documenting the comments and minor modifications of the terminology to align with SA1. Yang (OPPO) provides r02 Juan Zhang (Qualcomm) provides comments to r01 and r02. Mehrdad (Mediatek Inc.) provides r03 based on r01. Dongjoo (Nokia) provides r04. Yang (OPPO) explain why 5QI=85 is suitable for DL Split AI/ML image recognition and provides r05 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with either r04 or r05. Dongjoo (Nokia) suggests going with r05 as OPPO proposed. Mehrdad (Mediatek Inc.) is ok with r03, r04 or r05 but objects to the rest of revisions and original version. Yang (OPPO) prefer r05, can live with r04 as well Tingyu (Samsung) is ok with r04 and r05. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305439 | CR | Approval | 23.501 CR4473R1 (Rel-18, 'F'): 5QI for AIML services | Qualcomm Incorporated, Samsung, OPPO | Rel-18 | Revision of S2-2305055r05, merging S2-2304285. Approved | Agreed | |
| 9.9.2 | - | - | - | Key Issue #7: 5GS Assistance to Federated Learning Operation | - | - | Docs:=10 | - | |
| 9.9.2 | - | - | - | A. On assistance to selection of UE for FL operation | - | - | Docs:=25 | - | |
| 9.9.2 | S2-2305345 | DISCUSSION | Endorsement | Moderated Discussions - Member Selection Terminology | OPPO (Rapporteur) | Rel-18 | Noted | Noted | |
| 9.9.2 | S2-2305379 | CR | Approval | 23.501 CR4565 (Rel-18, 'F'): 23.501 Member UE terminology update | OPPO | Rel-18 | r01 agreed. Revised to S2-2305440, merging S2-2304425 Proposed to be used as the baseline to be merged withS2-2304425 | Jingran(OPPO) provides merged version r01 and S2-2305379 is used as the baseline to be merged with S2-2304425 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305440 | CR | Approval | 23.501 CR4565R1 (Rel-18, 'F'): 23.501 Member UE terminology update | OPPO | Rel-18 | Revision of S2-2305379r01, merging S2-2304425. Approved | Agreed | |
| 9.9.2 | S2-2304425 | CR | Approval | 23.501 CR4305 (Rel-18, 'F'): Member-UE selection without the NEF assistance in TS 23.501 | China Mobile, MediaTek Inc. | Rel-18 | Merged into S2-2305440 Proposed to be merged into S2-2305379 | Jingran(OPPO) proposes to merge S2-2304425 into S2-2305379r01, please see the merged version in the thread S2-2305379. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2305380 | CR | Approval | 23.502 CR4157 (Rel-18, 'F'): 23.502 Member UE terminology update | OPPO | Rel-18 | r02 agreed. Revised to S2-2305441, merging S2-2304426 Proposed to be used as the baseline to be merged with S2-2304426 | Jingran(OPPO) provides merged version r01 and S2-2305380 is used as the baseline to be merged with S2-2304426 Jingran(OPPO) provides merged version r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305441 | CR | Approval | 23.502 CR4157R1 (Rel-18, 'F'): 23.502 Member UE terminology update | OPPO | Rel-18 | Revision of S2-2305380r02, merging S2-2304426. Approved | Agreed | |
| 9.9.2 | S2-2304426 | CR | Approval | 23.502 CR4006 (Rel-18, 'F'): Member-UE selection without the NEF assistance in TS 23.502 | China Mobile | Rel-18 | Merged into S2-2305441 Proposed to be merged into S2-2305380 | Jingran(OPPO) proposes to merge S2-2304426 into S2-2305380r01, please see the merged version in the thread S2-2305380. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2304283 | CR | Approval | 23.502 CR3986 (Rel-18, 'B'): Updates to assistance for UE member selection | Samsung | Rel-18 | Postponed | Jingran(OPPO) provides comments Jaewoo (LGE) provides comments. Dongjoo (Nokia) shares the same view with OPPO and LGE. Tingyu (Samsung) replies to Jingran(OPPO), Jaewoo (LGE) and Dongjoo (Nokia), and provides further clarification. Mehrdad (Mediatek Inc.) comments OPPO (Tricci) thanks Tingyu (Samsung) further clarifications, however, OPPO is not convinced the benefits to support UE de-selection and UE list update when filtering criteria are changed, and hence, OPPO cannot accept such proposal. Tingyu (Samsung) replies to Mehrdad (Mediatek Inc.) and provides r01. Juan Zhang (Qualcomm) provides comments. Tingyu (Samsung) replies and provides r02. Tricci (OPPO) thanks Tingyu (Samsung) response and provides further clarifications. Belen (ericsson) provides comments. Tingyu (Samsung) replies to Belen (ericsson) and Tricci (OPPO) and provides r03. Tricci (OPPO) thanks Tingyu (Samsung) update but still cannot agree on the update operation for the filtering as well as the notify discard. Wang Yuan (Huawei) sees some benefits for this solution. Tricci (OPPO) ask Wang Yuan (Huawei) for clarifications. Tingyu (Samsung) thanks Wang Yuan (Huawei) and replies to Tricci (OPPO). ==== Revisions Deadline ==== Tricci (OPPO) would like to respond to Tingyu (Samsung). Tricci (OPPO) rejects any version of this CR due to lack of technical justification for introducing duplicated control flow and new notification service that can be handled by existing notification service. Tao(Sony) supports Tricci(Oppo)'s comments on the full UE list re-evaluation. Tingyu (Samsung) asks to open this CR in CC#3 or #4, replies to Tricci (OPPO)'s and very late comments from Tao(Sony), thinks Tricci's objection lacks technical basis. Belen (Ericsson) asks to POSTPONE this CR. Tricci (OPPO) would like Tingyu (Samsung) to provide technical justification (basis) what are the different between steps 1 to 5 vs. steps 6 - 9 after updating the filtering criteria and also why existing Notify is not sufficient to be reused such that you need to introduce a new Notify Discard since you re-evaluate the UE list anyway? How NEF will respond differently? Please clarify. Tingyu (Samsung) is ok to postpone this CR and replies to Tricci. ==== Comments Deadline ==== Tricci (OPPO) still don't see the value of this proposal. OPPO still did not get the answer from Tingyu (Samsung) and will try one last time. Tingyu (Samsung) replies to Tricci with the values of the proposals and emphasises that Tricci's previous comments have been fully addressed (based on our interpretation of those questions). | Postponed |
| 9.9.2 | S2-2304889 | CR | Approval | 23.501 CR4427 (Rel-18, 'F'): Clarifications on the UE member selection assistance functionality | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305442. | Dongjoo (Nokia) provides comments. Wang Yuan (Huawei) replies to Dongjoo (Nokia) and provides r01. Dongjoo (Nokia) is fine with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305442 | CR | Approval | 23.501 CR4427R1 (Rel-18, 'F'): Clarifications on the UE member selection assistance functionality | Huawei, HiSilicon | Rel-18 | Revision of S2-2304889r01. Approved | Agreed | |
| 9.9.2 | S2-2305360 | CR | Approval | 23.502 CR4153 (Rel-18, 'D'): AIMLsys: KI#7 Fixing clause 4.15.13 structure | InterDigital, Europe, Ltd. | Rel-18 | Merged into S2-2305444 | Dongjoo (Nokia) proposes to merge this CR into S2-2304035 as the changes are overlapped. David (Samsung) agrees with Nokia's comments Ulises (InterDigital Inc.) agrees with both Dongjoo (Nokia) and David (Samsung) that S2-2305360 can be merged into S2-2304035 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.9.2 | S2-2305224 | CR | Approval | 23.501 CR4530 (Rel-18, 'B'): Service Experience filtering criteria in assistance to UE member selection | InterDigital, Europe, Ltd. | Rel-18 | CC#4: Approved | Mehrdad (Mediatek Inc.) thinks this CR is dependent on progress of S2-2304573 in this meeting. Ulises (InterDigital Inc.) replies to Mediatek's comments, we have address Meditek's comments as well as other's, in S2-2304573r01, this should clear the way for the 23.501 CR counterpart. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.9.2 | S2-2304573 | CR | Approval | 23.502 CR4031 (Rel-18, 'B'): Service Experience filtering criteria in assistance to UE member selection | InterDigital, Europe, Ltd. | Rel-18 | r02 agreed. Revised to S2-2305443. | Mehrdad (Mediatek Inc.) requests some clarification. Jingran(OPPO) provides comment. Belen (Ericsson) provides comment. Ulises (InterDigital Inc.) provides replies to Belen (Ericsson), Jingran (Oppo), and Mehrdad (MediaTek), and provides r01 Mehrdad (Mediatek Inc.) can not agree with original version and r01 and provides r02. Ulises (InterDigital Inc.) comments on Mediatek's proposal, and agrees to r02 ==== Revisions Deadline ==== Jingran (OPPO) is ok with r02. Mehrdad (Mediatek Inc.) can live with r02 but objects to r01 and original version. ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305443 | CR | Approval | 23.502 CR4031R1 (Rel-18, 'B'): Service Experience filering criteria in assistace to UE member selection | InterDigital, Europe, Ltd. | Rel-18 | Revision of S2-2304573r02. Approved | Agreed | |
| 9.9.2 | S2-2304638 | CR | Approval | 23.502 CR4042 (Rel-18, 'C'): Update to UE Member Filtering Criteria | Sony | Rel-18 | Postponed | David (Samsung) provides comments on this CR Tao (Sony) replies and provides r01 ==== Revisions Deadline ==== David (Samsung) cannot accept r00 or r01 Tao (Sony) replies to David(Samsung) and suggests to postpone the CR to next meeting (SA2#157). David (Samsung) is OK to postpone. Tao (Sony) thanks David(Samsung) for further clarification and agrees to discuss in next meeting. ==== Comments Deadline ==== | Postponed |
| 9.9.2 | S2-2305367 | CR | Approval | 23.502 CR4155 (Rel-18, 'B'): AIMLsys: KI#7 UP Security filtering criteria for UE Member Selection | InterDigital, Europe, Ltd. | Rel-18 | Postponed | Jingran(OPPO) provides comments Juan Zhang (Qualcomm) provides comments Ulises (InterDigital Inc.) replies to comments from Jingran (Oppo), and Juan (Qualcomm) Jingran(OPPO) replies to Ulises (InterDigital Inc.) Belen (Ericsson) provides comments Ulises (InterDigital Inc.) replies to comments from Jingran (Oppo), and provides r01 Ulises (InterDigital Inc.) replies to comments from Belen (Ericsson) and Qualcomm (Juan), and does not see a technical reason why UP security policy status cannot be expose to NEF as long as it's not exposed to AF. ==== Revisions Deadline ==== Jingran(OPPO) provides comments and suggests to Note or postpone this CR. Juan Zhang (Qualcomm) objects all the version for this proposal. Ulises (InterDigital Inc.) replies to comments Jingran (Oppo) and agrees to postpone this CR for now. Ulises (InterDigital Inc.) replies to comments Qualcomm (Juan), we have agreed to postpone this CR, but we did not receive technical comments from Qualcomm we didn't address. W.r.t: 'I do not believe even the AF will send this as an assistance criterial to NEF' this is not a technical comment. ==== Comments Deadline ==== | Postponed |
| 9.9.2 | S2-2304036 | CR | Approval | 23.501 CR4191 (Rel-18, 'F'): Translation of Internal-External Information for Assisting Application Layer AI/ML Operations | Ericsson | Rel-18 | CC#4: r01 + changes agreed. Revised to S2-2306247. For CC#4 | Jingran (OPPO) provides comment. Belen (Ericsson) provides r01 David (Samsung) provides question for clarification ==== Revisions Deadline ==== Belen (Ericsson) asks to approve r01, including Samsung proposed rephrasing. Jingran(OPPO) is fine with r01. David (Samsung) can agree to late r02 with updates to r01 as shown by Ericsson. Belen (Ericsson) provides r02, David (Samsung) comments that r02 does not include the agreed update in cl. 5.46.2 Belen (Ericsson) provides r03 David (Samsung) can live with r03 David (Samsung) can live with r03 provided after deadline, objects to rest of revisions ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2306247 | CR | Approval | 23.501 CR4191R1 (Rel-18, 'F'): Translation of Internal-External Information for Assisting Application Layer AI/ML Operations | Ericsson | Rel-18 | Revision of S2-2304036r01 + changes. CC#4: Approved | Agreed | |
| 9.9.2 | S2-2304035 | CR | Approval | 23.502 CR3953 (Rel-18, 'F'): AIMLsys - QoS filtering criteria corrections | Ericsson | Rel-18 | r01 agreed. Revised to S2-2305444, merging S2-2305360 | Jihoon (ETRI) provides comments. Belen (Ericsson) replies to comments. Jihoon (ETRI) replies to Belen (Ericsson). Belen (Ericsson) provides r01 Jihoon (ETRI) thanks Belen for clarification and is okay for r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305444 | CR | Approval | 23.502 CR3953R1 (Rel-18, 'F'): AIMLsys - QoS filtering criteria corrections | Ericsson | Rel-18 | Revision of S2-2304035r01, merging S2-2305360. Approved | Agreed | |
| 9.9.2 | S2-2304291 | CR | Approval | 23.502 CR3988 (Rel-18, 'B'): RAN throughput distribution filtering criteria for FL member selection | NTT DOCOMO | Rel-18 | Noted | Jingran(OPPO) provides comments Bahador (NTT DOCOMO) replies to Jingran (OPPO) Jingran (OPPO) replies to Bahador (NTT DOCOMO) ==== Revisions Deadline ==== Jingran (OPPO) objects this CR and propose to Note it ==== Comments Deadline ==== | Noted |
| 9.9.2 | S2-2304616 | CR | Approval | 23.502 CR4040 (Rel-18, 'B'): AIMLsys: KI#7 additional information provided by NEF | LG Electronics | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305445. | Bahador (NTT DOCOMO) provides a comment. Jaewoo (LGE) replies to Bahador (NTT DOCOMO) and provides r01. Juan Zhang (Qualcomm) provides comments. Bahador (NTT DOCOMO) replies to Jaewoo (LGE) Jaewoo (LGE) replies to Juan Zhang (Qualcomm) and provides r02. Juan Zhang (Qualcomm) provides comments to Jaewoo (LGE). Jaewoo (LGE) replies to Juan Zhang (Qualcomm) for clarification. Juan Zhang (Qualcomm) is OK with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305445 | CR | Approval | 23.502 CR4040R1 (Rel-18, 'B'): AIMLsys: KI#7 additional information provided by NEF | LG Electronics | Rel-18 | Revision of S2-2304616r02. Approved | Agreed | |
| 9.9.2 | S2-2304614 | CR | Approval | 23.502 CR4039 (Rel-18, 'B'): AIMLsys: KI#7 Adding maximum number of UEs as a member selection filtering criterion | LG Electronics | Rel-18 | CR Cover sheet error! r01 agreed. Revised to S2-2305446. | Jingran (OPPO) provides comment. Jaewoo (LGE) replies to Jingran (OPPO) and provides r01. Jingran(OPPO) replies to Jaewoo (LGE) and is ok with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305446 | CR | Approval | 23.502 CR4039R1 (Rel-18, 'B'): AIMLsys: KI#7 Adding maximum number of UEs as a member selection filtering criterion | LG Electronics | Rel-18 | Revision of S2-2304614r01. Approved | Agreed | |
| 9.9.2 | - | - | - | B. On performance monitoring analytics/exposure | - | - | Docs:=16 | - | |
| 9.9.2 | S2-2304038 | CR | Approval | 23.288 CR0734 (Rel-18, 'F'): Update to the Input of E2E Data Volume Transfer Time Analytics | Ericsson | Rel-18 | Approved | Wang Yuan (Huawei) proposes to merge S2-2304038 into S2-2304890r01, please see the merged version in the thread S2-2304890. Zhang (Ericsson) response to Yuan (Huawei) and propose to use this paper as the baseline for application server info ==== Revisions Deadline ==== Zhang (Ericsson) indicate the paper is the baseline for application server Info, it can be agreed as it is Tao(VC) check whether we can go with r00 ==== Comments Deadline ==== | Agreed |
| 9.9.2 | S2-2304287 | CR | Approval | 23.288 CR0748 (Rel-18, 'B'): Service data from AF for E2E data volume transfer time analytics | NTT DOCOMO | Rel-18 | r03 agreed. Revised to S2-2305449. | Wang Yuan (Huawei) proposes to merge S2-2304287 into S2-2304890r01, please see the merged version in the thread S2-2304890. Bahador (NTT DOCOMO) disagrees to merge S2-2304287 into S2-2304890. Jihoon (ETRI) provides comments. Bahador (NTT DOCOMO) responds to Jihoon (ETRI) and provides r01. Tingyu (Samsung) provides comments Bahador (NTT DOCOMO) responses to Tingyu (Samsung). Zhang (Ericsson) provides comments Bahador (NTT DOCOMO) provides r02. Tingyu (Samsung) replies to Bahador (NTT DOCOMO). Bahador (NTT DOCOMO) replies to Tingyu (Samsung) and provides r03. Tingyu (Samsung) is fine with r03. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305449 | CR | Approval | 23.288 CR0748R1 (Rel-18, 'B'): Service data from AF for E2E data volume transfer time analytics | NTT DOCOMO | Rel-18 | Revision of S2-2304287r03. Approved | Agreed | |
| 9.9.2 | S2-2304890 | CR | Approval | 23.288 CR0790 (Rel-18, 'F'): Update the End-to-end data volume transfer time analytics | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2305450. Proposed to be merged into S2-2304038 | Wang Yuan (Huawei) proposes to use S2-2304890 as the baseline to be merged with S2-2304038 and S2-2304287, and provides the merged version S2-2304890r01. Jihoon (ETRI) asks a question for clarification. Bahador (NTT DOCOMO) requests for clarification and provides r02 to undo merging S2-2304287 to S2-2304890. Zhang (Ericsson) response to Yuan (Huawei) and suggest to use S2-2304038 as baseline for application server info Tricci (OPPO) requests for clarifications from Zhang (Ericsson) and Yuan (Huawei) regarding IP@ vs. FQDN vs.DNAI Tingyu (Samsung) asks for clarification. Wang Yuan (Huawei) replies to Jihoon (ETRI), Bahador (NTT DOCOMO), Zhang (Ericsson), Tricci (OPPO) and Tingyu (Samsung), and provides r03. Tricci (OPPO) thanks Wang Yuan (Huawei) for the clarifications and happy to know that there is an agreement between Ericsson and Huawei for which addressing to use. Tingyu (Samsung) replies. Wang Yuan (Huawei) replies to Tingyu (Samsung) and provides r04. Bahador (NTT DOCOMO) replies to Yuan (Huawei) Zhang (Ericsson) thanks Yuan for the collaboration and OK with r03 Tingyu (Samsung) replies and can live with r03 but prefers r04. Wang Yuan (Huawei) replies to Bahador (NTT DOCOMO). ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 and object all other versions ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305450 | CR | Approval | 23.288 CR0790R1 (Rel-18, 'F'): Update the End-to-end data volume transfer time analytics | Huawei, HiSilicon | Rel-18 | Revision of S2-2304890r03. Approved | Agreed | |
| 9.9.2 | S2-2304696 | CR | Approval | 23.288 CR0780 (Rel-18, 'B'): Clarification of N6 data collection and output enhancement for End-to-end data volume transfer | vivo | Rel-18 | r01 agreed. Revised to S2-2305451. | Jihoon (ETRI) provides comments. Huazhang (vivo) reply to Jihoon (ETRI) Dongjoo (Nokia) provides comments. Huazhang (vivo) provide r01 Tingyu (Samsung) provides comments. Huazhang (vivo) reply to Tingyu Tingyu (Samsung) replies to Huazhang (vivo). Tingyu (Samsung) replies and thanks Huazhang (vivo) for the further clarifications. Huazhang (vivo) thanks Tingyu for your comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305451 | CR | Approval | 23.288 CR0780R1 (Rel-18, 'B'): Clarification of N6 data collection and output enhancement for End-to-end data volume transfer | Vivo | Rel-18 | Revision of S2-2304696r01. Approved | Agreed | |
| 9.9.2 | S2-2304288 | CR | Approval | 23.502 CR3987 (Rel-18, 'B'): E2E data volume transfer time information event ID of AF | NTT DOCOMO | Rel-18 | Approved | Agreed | |
| 9.9.2 | S2-2304068 | CR | Approval | 23.288 CR0736 (Rel-18, 'C'): OAM input Corrections and EN addition | Verizon, Samsung | Rel-18 | CR Cover sheet error!. Confirm Spec version used - CR states 18.0.1! r01 agreed. Revised to S2-2305452. | Peretz (Verizon) provides an updated cover page ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305452 | CR | Approval | 23.288 CR0736R1 (Rel-18, 'C'): OAM input Corrections and EN addition | Verizon, Samsung | Rel-18 | Revision of S2-2304068r01. Approved | Agreed | |
| 9.9.2 | S2-2304368 | CR | Approval | 23.288 CR0751 (Rel-18, 'B'): Resolve an EN on which AF event can be used to collect Server location | China Mobile | Rel-18 | r01 agreed. Revised to S2-2305447. Proposed to be merged into S2-2304038 | Zhang (Ericsson) provides comments and suggest to merge the second change of the paper into S2-2304038 Dan (China Mobile)agree this merge into S2-2304038 Zhang (Ericsson) thanks Dan and provide r01 Dan (China Mobile) thanks and ok with r01 ==== Revisions Deadline ==== Zhang (Ericsson) indicate the paper shall not be marked as merged, r01 is agreeable ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305447 | CR | Approval | 23.288 CR0751R1 (Rel-18, 'B'): Resolve an EN on Which AF event can be used to collect Server location | China Mobile | Rel-18 | Revision of S2-2304368r01. Approved | Agreed | |
| 9.9.2 | S2-2304617 | CR | Approval | 23.288 CR0776 (Rel-18, 'F'): AIMLsys: KI#7 Clarification for validity conditions of E2E data volume transfer time analytics | LG Electronics | Rel-18 | CR Cover sheet error! r00 agreed. Revised to S2-2305427. | Revised | |
| 9.9.2 | S2-2305427 | CR | Approval | 23.288 CR0776R1 (Rel-18, 'F'): AIMLsys: KI#7 Clarification for validity conditions of E2E data volume transfer time analytics | LG Electronics | Rel-18 | Revision of S2-2304617r00. Approved | Agreed | |
| 9.9.2 | S2-2304886 | CR | Approval | 23.288 CR0789 (Rel-18, 'F'): Update to remove the EN for DN performance predictions | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305453. | Tingyu (Samsung) provides comments. Jingran (OPPO) provides comments. Wang Yuan (Huawei) replies to Tingyu (Samsung) and Jingran (OPPO). Jingran (OPPO) replies to Huawei. Tingyu (Samsung) replies to Yuan (Huawei). Wang Yuan (Huawei) replies to Jingran (OPPO) and Tingyu (Samsung) and provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.9.2 | S2-2305453 | CR | Approval | 23.288 CR0789R1 (Rel-18, 'F'): Update to remove the EN for DN performance predictions | Huawei, HiSilicon | Rel-18 | Revision of S2-2304886r01. Approved | Agreed | |
| 9.10.1 | - | - | - | Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) | - | - | Docs:=0 | - | |
| 9.10.2 | - | - | - | 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | - | - | Docs:=73 | - | |
| 9.10.2 | - | - | - | General | - | - | Docs:=9 | - | |
| 9.10.2 | S2-2303964 | LS In | Action | LS from RAN WG3: Reply LS on FS_5MBS_Ph2 progress | RAN WG3 (R3-231030) | Rel-18 | Noted | LiMeng (Huawei) propose to mark this document as NOTED. | Noted |
| 9.10.2 | S2-2304435 | CR | Approval | 23.247 CR0223 (Rel-18, 'F'): Update about SMF selection in TS 23.247 | China Mobile | Rel-18 | Noted | Judy (Ericsson) comments Aihua (CMCC) replies to Judy(Ericsson). Zhendong (ZTE) provides comments. Aihua (CMCC) replies to Zhendong(ZTE). Haris(Qualcomm) indicates that the CR is not acceptable in its present form (R00) Thomas(Nokia) comments Aihua(CMCC) replies to Haris and Thomas, and provides r01 Aihua(CMCC) replies to Judy (Ericsson), and provides r02. Haris(Qualcomm) comments that r01 and r02 are technically incorrect Aihua(CMCC) replies to Haris (Qualcomm), and provides r03. Aihua(CMCC) replies to Haris (Qualcomm), and provides r04. ==== Revisions Deadline ==== Judy (Ericsson) comments that the CR proposal may not work if MBS auth info is available but the PDU Session is already established Aihua(CMCC) replies to Judy (Ericsson) . Judy (Ericsson) responds to Aihua(CMCC) Aihua(CMCC) replies. Judy (Ericsson) propose to NOTE this paper as the proposal may not work ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2304319 | CR | Approval | 23.247 CR0213 (Rel-18, 'F'): Update functional entity clauses for group message delivery and power saving functions | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2305454. | Judy (Ericsson) provides r01 Zhendong (ZTE) provides comments. Thomas (Nokia) provides r02 Judy (Ericsson) comments and provide r03 Thomas(Nokia) provides r04 ==== Revisions Deadline ==== Judy (Ericsson) prefers r01/r03, can live with r04, objects to r00/r02 Thomas(Nokia) prefers r04, objects against r00, r01 and r03 ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305454 | CR | Approval | 23.247 CR0213R1 (Rel-18, 'F'): Update functional entity clauses for group message delivery and power saving functions | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304319r04. Approved | Agreed | |
| 9.10.2 | S2-2305333 | CR | Approval | 23.247 CR0252 (Rel-18, 'F'): Enabling simultaneous join for high number of UEs that support multicast RRC inactive reception | Nokia, Nokia Shanghai-Bell | Rel-18 | Revised to S2-2305362 | Revised | |
| 9.10.2 | S2-2305363 | CR | Approval | 23.247 CR0252R1 (Rel-18, 'F'): Enabling simultaneous join for high number of UEs that support multicast RRC inactive reception | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305333. r03 agreed. Revised to S2-2305455. | Judy (Ericsson) provides r01 Xiaoyan (CATT) provides comments. Thomas(Nokia) replies to Xiaoyan. Haris(Qualcomm) asks question for clarification and proposes alternative wording Thomas(Nokia) replies to Haris Haris(Qualcomm) responds and asks question LiMeng (Huawei) responds. Thomas (Nokia) provides r02 Haris(Qualcomm) provides r03 ==== Revisions Deadline ==== Judy (Ericsson) question the need of NOTE Y Thomas(Nokia) replies to Judy ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305455 | CR | Approval | 23.247 CR0252R2 (Rel-18, 'F'): Enabling simultaneus join for high number of UEs that support multicast RRC inactive reception | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305363r03. Approved | Agreed | |
| 9.10.2 | S2-2304320 | CR | Approval | 23.247 CR0214 (Rel-18, 'F'): Update the abbreviation for Release 18 | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305456. | Judy (Ericsson) provides r01 and comments Haris(Qualcomm) comments Thomas(Nokia) comments LiMeng (Huawei) provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305456 | CR | Approval | 23.247 CR0214R1 (Rel-18, 'F'): Update the abbreviation for Release 18 | Huawei, HiSilicon | Rel-18 | Revision of S2-2304320r02. Approved | Agreed | |
| 9.10.2 | - | - | - | Data key in Parameter Provision | - | - | Docs:=3 | - | |
| 9.10.2 | S2-2305331 | CR | Approval | 23.502 CR4148 (Rel-18, 'B'): MBS assistance information in UDM | Nokia, Nokia Shanghai-Bell | Rel-18 | CC#4: r02 + changes agreed. Revised to S2-2306250. Approve r02? Ericsson has sustained objection. Discuss this again in CC#4 to check if we need WA. | Judy (Ericsson) raises concern of this CR, and proposes to adopt the solution in 4145. Fenqin (Huawei) comments Thomas(Nokia) suggest a show-of-hands Judy (Ericsson) asks Fenqin (Huawei) question and comments Thomas (Nokia) provides replies to Judy Hugh (AT&T) asks a question Judy (Ericsson) comments and provide r01 Thomas (Nokia) objects against r01, which is Option 3 which gained little support in the show-of-hands. Provides r02 to maintain acceptable unrelated changes from r01 Fenqin (Huawei) comments and support r02. ==== Revisions Deadline ==== Judy (Ericsson) objects to r00, r02, can live with r01 allowing GPSI/MBS Session ID as data key Fenqin (Huawei) objects to r01, accept r00 /r02 Thomas(Nokia) suggest taking this issue to a CC ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2306250 | CR | Approval | 23.502 CR4148R1 (Rel-18, 'B'): MBS assistance information in UDM | Nokia, Nokia Shanghai-Bell, Huawei | Rel-18 | Revision of S2-2305331r02 + changes. CC#4: Approved | Agreed | |
| 9.10.2 | S2-2304145 | CR | Approval | 23.502 CR3971 (Rel-18, 'F'): Resolve EN on Parameter Provision data key for MBS Session Assistance Info in UDM | Ericsson | Rel-18 | Noted | Thomas (Nokia) comments that this CR competes with S2-2305331 and only one can be agreed. Prefers the solution in S2-2305331 and suggest deciding based on show of hands Judy (Ericsson) raise concern on this CR Judy (Ericsson) request to withdraw previous comment which is intended for 5331 Fenqin (Huawei) comments Thomas (Nokia) suggest noting this CR due to the show-of-hands results in favor of S2-2305331 Fenqin (Huawei) share the same view as Thomas and suggest to noted this paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | - | - | - | MBS Assistance Information update | - | - | Docs:=3 | - | |
| 9.10.2 | S2-2304146 | DISCUSSION | Agreement | KI#1 Definition of MBS Assistance Information | Ericsson | Rel-18 | Noted | Haris(Qualcomm) comments Thomas(Nokia) shares the concerns of Harris Judy (Ericsson) responds to Thomas(Nokia) and Haris(Qualcomm) Fenqin (Huawei) shares the same view as Harris and Thomas. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2304147 | CR | Approval | 23.247 CR0206 (Rel-18, 'F'): KI#1 Definition of MBS Assistance Information | Ericsson | Rel-18 | Noted | Haris(Qualcomm) objects to the CR Judy (Ericsson) responds to Haris(Qualcomm). Fenqin (Huawei)share the same view as Haris ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2305330 | CR | Approval | 23.247 CR0251 (Rel-18, 'F'): Resolving open issues for MBS multicast RRC inactive reception | Nokia, Nokia Shanghai-bell | Rel-18 | Check Affected Clauses! Noted | Judy (Ericsson) comments and objects to r00 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | - | - | - | Mobility for RRC Inactive reception | - | - | Docs:=10 | - | |
| 9.10.2 | S2-2304148 | CR | Approval | 23.247 CR0207 (Rel-18, 'F'): KI#1 Correction of mobility procedures for delivery of multicast MBS session data to RRC_INACTIVE UE | Ericsson | Rel-18 | CC#4: r05 + changes agreed. Revised to S2-2306248. Agree r05? For CC#4. | Xiaoyan (CATT) provides comments. Judy (Ericsson) responds to Xiaoyan (CATT) Haris(Qualcomm) provides comments Judy (Ericsson) responds to Haris(Qualcomm) and provides r01 Thomas (Nokia) provides r02 Fenqin (Huawei) suggest to go with r01 Judy (Ericsson) also suggest to go for r01 Thomas (Nokia) objects against r00 and r01. Thomas (Nokia) provides r03 Judy (Ericsson) provides r04 based on r01, objects to r02 &r03 Thomas(Nokia) objects against r04 Fenqin(Huawei) comments Judy (Ericsson) provides r05 based on r03, only cover sheet is updated Xiaoyan (CATT) provides r06 ==== Revisions Deadline ==== Judy (Ericsson) comments that the EN added in r06 is not justified. Xiaoyan (CATT) replies to Judy (Ericsson). Thomas(Nokia) objects against r05 and r06. Judy (Ericsson) accepts r01/r04/r05, cannot accept r06 as is, requesting to remove the EN, objects to other revisions (r00 included), and responds to Xiaoyan (CATT) LiMeng (Huawei) clarifies to Thomas that r05 and r06 do not remove the NOTEs. Fenqin (Huawei) suggest to go with r05 Tao(VC) check whether we can go with r05 Thomas(Nokia) correct himself, can accept r05 Xiaoyan (CATT) can live with r06 + removing 'in the N2 SM information', and objects to other revisions LiMeng (Huawei) suggests to determine the way forward of this document in CC#4. Judy (Ericsson) finds it dfficult to understand why Xiaoyan (CATT) insists on adding an EN which is irrelevant to this paper, request CC discussion. Thomas(Nokia) also believes that the suggested EN is unrelated to the mobility procedures and the subject of the CR. Fenqin (Huawei) share the same view as Thomas and Judy. Xiaoyan (CATT) responds to Fenqin, Thomas and Judy. ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2306248 | CR | Approval | 23.247 CR0207R1 (Rel-18, 'F'): KI#1 Correction of mobility procedures for delivery of multicast MBS session data to RRC_INACTIVE UE | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon | Rel-18 | Revision of S2-2304148r05 + changes. CC#4: Approved | Agreed | |
| 9.10.2 | S2-2304581 | CR | Approval | 23.247 CR0226 (Rel-18, 'B'): Mobility Registration Update and Service Request procedures for local multicast service | CATT | Rel-18 | r01 agreed. Revised to S2-2305457. | Thomas (Nokia) questions need for this CR. Comments that changes would also need to fit to Rel-17 changes discussed in parallel Fenqin (Huawei) comments Judy (Ericsson) comments Xiaoyan (CATT) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305457 | CR | Approval | 23.247 CR0226R1 (Rel-18, 'B'): Mobility Registration Update and Service Request procedures for local multicast service | CATT | Rel-18 | Revision of S2-2304581r01. Approved | Agreed | |
| 9.10.2 | S2-2304582 | CR | Approval | 23.247 CR0227 (Rel-18, 'B'): Mobility Registration Update and Service Request procedures for location dependent multicast service | CATT | Rel-18 | r01 agreed. Revised to S2-2305458. | Thomas (Nokia) questions need for this CR. Comments that changes would also need to fit to Rel-17 changes discussed in parallel Fenqin (Huawei) comments Judy (Ericsson) comments Xiaoyan (CATT) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305458 | CR | Approval | 23.247 CR0227R1 (Rel-18, 'B'): Mobility Registration Update and Service Request procedures for location dependent multicast service | CATT | Rel-18 | Revision of S2-2304582r01. Approved | Agreed | |
| 9.10.2 | S2-2304956 | CR | Approval | 23.247 CR0240 (Rel-18, 'F'): Open issue related to mobility procedures of RRC Inactivate state UE | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305459. | Xiaoyan (CATT) provides comments. Judy (Ericsson) provides r01 Thomas (Nokia) provides r02 Fenqin (Huawei) provides r03 ==== Revisions Deadline ==== Judy (Ericsson) request a revision in r03, as some text are deleted without track changes Thomas (Nokia) objects against r03, suggest agreeing r02 Judy (Ericsson) responds Fenqin (Huawei) suggest to go with r03+ '..with the following enhancements: - If the UE context cannot be retrieved successfully, the NG-RAN triggers the UE to move to RRC_IDLE state as specified in TS 38.300 [9]. The UE initiates the Mobility Registration Update procedure or Service Request procedure to activate the associated PDU session(s). Hence the shared delivery (if not already established) or the individual delivery can be established towards the NG-RAN node to enable delivery of multicast MBS session data to the UEs.' Restore with deletion change mark.. Or we can go with R02 with the understanding that no change at clause 7.2.3.8.1+7.2.3.8.2, it will be removed later. Thomas (Nokia) responds to Judy Fenqin (Huawei) responds to Thomas and fine to go with r02. Judy (Ericsson) is fine with r02 too ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305459 | CR | Approval | 23.247 CR0240R1 (Rel-18, 'F'): Open issue related to mobility procedures of RRC Inactivate state UE | Huawei, HiSilicon; Nokia, Nokia Shanghai-Bell, Ericsson | Rel-18 | Revision of S2-2304956r02. Approved | Agreed | |
| 9.10.2 | S2-2305344 | CR | Approval | 23.247 CR0253 (Rel-18, 'F'): Mobility procedures for RRC inactive UEs | Nokia, Nokia Shanghai-Bell | Rel-18 | r04 + changes agreed. Revised to S2-2305460. | Xiaoyan (CATT) provides comments. Thomas (Nokia) replies to Xiaoyan and provides r01. Judy (Ericsson) comments Thomas (Nokia) replies to Judy Fenqin (Huawei) provides r02 Thomas (Nokia) provides r03 Thomas (Nokia) provides r04 ==== Revisions Deadline ==== Judy (Ericsson) comments that the description in r05 is incorrect. Thomas(Nokia) suggest agreeing r05 + Remove 'while the multicast MBS session is in Active state' Fenqin (Huawei) agree to go with r04 + Remove 'while the multicast MBS session is in Active state' Judy (Ericsson) agree to the proposal from Fenqin and Thomas Thomas (Nokia) agrees to the proposal of Fenqin (there is no r05) ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305460 | CR | Approval | 23.247 CR0253R1 (Rel-18, 'F'): Mobility procedures for RRC inactive UEs | Nokia, Nokia Shanghai-Bell, ZTE | Rel-18 | Revision of S2-2305344r04 + changes. Approved | Agreed | |
| 9.10.2 | - | - | - | Deferred UE leaving and synchronizing MBS session status | - | - | Docs:=2 | - | |
| 9.10.2 | S2-2304343 | DISCUSSION | Agreement | On the need for deferred leaving procedure in RRC_INACTIVE | Qualcomm Incorporated | Noted | Noted | ||
| 9.10.2 | S2-2304344 | CR | Approval | 23.247 CR0196R1 (Rel-18, 'B'): Procedures for deferred leaving when the UE is in RRC_INACTIVE state | Qualcomm Incorporated | Rel-18 | Revision of S2-2302952 from S2#155. CR Cover sheet error! Noted | Thomas (Nokia) raises concerns against this CR LiMeng (Huawei) has the similar concerns as Thomas regarding the proposal. Judy (Ericsson) share Thomas and Li Meng's comments where were also shared during pre-meeting telco. Zhendong (ZTE) share similar comments with Nokia, Ericsson and Huawei. Xiaoyan (CATT) supports this CR and believes that deferred leaving is critical to R18 UEs receiving multicast MBS sessions in RRC_INACTIVE state feature. Haris(Qualcomm) provides responses to the comments ==== Revisions Deadline ==== Tao(VC) can Haris' explanation address the concern so that R00 be approved or not? LiMeng (Huawei) comments LiMeng (Huawei) comments on MM-SM separation issue. Judy (Ericsson) share LiMeng (Huawei)'s comments Thomas(Nokia) suggests noting this CR Haris(Qualcomm) responds Fenqin (Huawei) also suggest to Note this CR Xiaoyan (CATT) responds to Fenqin (Huawei) Judy (Ericsson) thanks Fenqin (Huawei) for the analysis and also suggest to NOTE this paper Xiaoyan (CATT) clarifies to LiMeng (Huawei) that there is no MM-SM separation issue. LiMeng (Huawei) responds. Fenqin (Huawei) responds to Xiaoyan (Huawei) Xiaoyan (CATT) points out the analytics of Fenqin is wrong and responds to Judy (Ericsson) Fenqin (Huawei) responds to Xiaoyan (CATT) again ==== Comments Deadline ==== Haris(Qualcomm) comments | Noted |
| 9.10.2 | - | - | - | General update of KI#2 | - | - | Docs:=5 | - | |
| 9.10.2 | S2-2304153 | CR | Approval | 23.247 CR0210 (Rel-18, 'C'): KI#2 Resolve EN in broadcast procedures for resource sharing in network sharing | Ericsson | Rel-18 | r04 agreed. Revised to S2-2305461, merging S2-2305393 | LiMeng (Huawei) suggests to address S2-2305252 at first. Judy (Ericsson) agrees with LiMeng (Huawei) as this CR is dependent on the outcome of 5252 discussion. Thomas(Nokia) suggest to merge this CR into 5393. Judy (Ericsson) provide r01 and proposes to use this CR as basis which originally adopts the approach of using step a/b for multicast N3mb and unicast N3mb. Thomas(Nokia) objects against r00 and r01. Thomas (Nokia) provide r02. Judy (Ericsson) provides r03 Thomas (Nokia) provide r04. ==== Revisions Deadline ==== Judy (Ericsson) accepts r03/r04, objects to r02 ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305461 | CR | Approval | 23.247 CR0210R1 (Rel-18, 'C'): KI#2 Resolve EN in broadcast procedures for resource sharing in network sharing | Ericsson, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304153r04, merging S2-2305393. Approved | Agreed | |
| 9.10.2 | S2-2305370 | CR | Approval | 23.247 CR0256 (Rel-18, 'F'): Unicast tunnel establishment and release for resource sharing across multiple broadcast MBS Sessions during network sharing | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! Revised to S2-2305393 | Revised | |
| 9.10.2 | S2-2305393 | CR | Approval | 23.247 CR0256R1 (Rel-18, 'B'): Unicast tunnel establishment and release for resource sharing across multiple broadcast MBS Sessions during network sharing | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305370. Merged into S2-2305461 | LiMeng (Huawei) suggests to address S2-2305252 at first. Thomas (Nokia) provides r01 based on S2-2305252r05 Judy (Ericsson) propose to merge this CR to 4153 and comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.10.2 | S2-2304152 | CR | Approval | 23.247 CR0209 (Rel-18, 'F'): KI#2 Regarding RAN config. to associate MBS Sessions delivering same content during network sharing | Ericsson | Rel-18 | Noted | LiMeng (Huawei) ask for clarification regarding the option of 'the association of MBS session identifiers (i.e. TMGIs) configured in NG-RAN'. Judy (Ericsson) asks for clarification Xiaoyan (CATT) provides comments. Haris(Qualcomm) indicates that is ok with WF proposed by Limeng but for the record objects to this CR (S2-2304152) version as is at the moment Thomas(Nokia) also object against this CR and suggest using the S2-2304873 thread to discuss how to resolve the ENs LiMeng (Huawei) comments that the proposal S2-2304152 and S2-2304873 are mutually exclusive, suggests to focus on the agreeable version of S2-2304873 if it is the majorities' choice. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | - | - | - | CR on Location Dependent MBS service | - | - | Docs:=10 | - | |
| 9.10.2 | S2-2304151 | LS OUT | Approval | [DRAFT] LS on location dependent MBS Session in network sharing in 5MBS_Ph2 | Ericsson | Rel-18 | Noted | LiMeng (Huawei) wonders the necessity of waiting the decision from RAN WGs regarding location dependent service for KI#2. Judy (Ericsson) responds to LiMeng (Huawei) that the need of the LS depends on the discussion. Thomas(Nokia) believes the LS is not required. Judy (Ericsson) responds to Thomas(Nokia) Zhendong (ZTE) agree with Nokia and Huawei ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2304149 | DISCUSSION | Agreement | KI#2 Discussion on association of location dependent MBS Sessions in MOCN | Ericsson | Rel-18 | Noted | Haris(Qualcomm) comments Judy (Ericsson) wonders if Haris (Qualcomm) assumes a NG-RAN node serves only MBS service Area, however this assumption may not be valid. Explained. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2304321 | DISCUSSION | Discussion | Discussion on the open issues of KI#2 | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.10.2 | S2-2304870 | DISCUSSION | Discussion | Discussion and proposal on the MOCN enhancement for the location dependent MBS session | ZTE | Rel-18 | Noted | Noted | |
| 9.10.2 | S2-2305362 | DISCUSSION | Discussion | Handling of location dependent sessions for MOCN network sharing | Nokia, Nokia Shanghai-Bell | Noted | Noted | ||
| 9.10.2 | S2-2304150 | CR | Approval | 23.247 CR0208 (Rel-18, 'C'): KI#2 Associating location dependent MBS Sessions delivering the same content during network sharing | Ericsson | Rel-18 | Noted | Judy (Ericsson) clarifies that Content ID is not a separate IE but an enhanced part of Associated Session ID. Haris(Qualcomm) objects to the CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | S2-2304583 | CR | Approval | 23.247 CR0194R2 (Rel-18, 'B'): Resource efficiency in MOCN network sharing for location dependent MBS service | CATT | Rel-18 | Revision of S2-2303357 from S2#155. Postponed | Thomas (Nokia) provides r01 LiMeng (Huawei) comments on r01 and provides r02 Xiaoyan (CATT) provides r03 Thomas (Nokia) provides r04 Judy (Ericsson) asks questions Xiaoyan (CATT) provides r05 Thomas(Nokia) replies to Judy Judy (Ericsson) provides r06 Xiaoyan (CATT) provides r07 ==== Revisions Deadline ==== Judy (Ericsson) comments and propose to postpone this paper Xiaoyan (CATT) provides clarifications to Judy (Ericsson), proposes to agree r07 or r07+small changes Thomas has concerns on r05 to r07. Could agree r07 plus changes of Xiaoyan + one additional change Judy (Ericsson) responds and propose to postpone this CR (i.e. object to this CR for the sake of clarity) ==== Comments Deadline ==== | Postponed |
| 9.10.2 | S2-2304871 | CR | Approval | 23.247 CR0231 (Rel-18, 'B'): Resolving the EN on the MOCN enhancement for the location dependent MBS session | ZTE | Rel-18 | CC#4: r04 + changes agreed. Revised to S2-2306249, merging S2-2305364. For CC#4 | Thomas (Nokia) provides r01 to merge S2-2305364 LiMeng (Huawei) provides r02 Zhendong (ZTE) is fine with r02. Haris(Qualcomm) provides r03 LiMeng (Huawei) is fine with r03 Zhendong (ZTE) is fine with r03. Judy (Ericsson) provides r04 ==== Revisions Deadline ==== Haris(Qualcomm) r04 is not acceptable. Proposes to agree r03 Judy (Ericsson) can only live with r04, objects to other revisions (r00 included). Thomas(Nokia) objects against r04 Zhendong (ZTE) agree with thomas, the CC conclusion is this is up to RAN implementation. Judy (Ericsson) comments LiMeng (Huawei) asks if we can agree with r04+ Replace 'based on Associated Session ID and MBS Service Area' with 'based on RAN implementation, e.g., Associated Session ID, or TMGI and MBS Service Area', and add 'For a location dependent MBS session (see Clauses 6.2.3), the AF(s) that create the location dependent MBS sessions towards the participating PLMNs shall supply service areas that contain the same shared radio cells (but may contain different non-shared radio cells).' Thomas (Nokia) can agree with r04+ Remove 'which means all the PLMNs participating network sharing are required to configure the same list of shared cells and/or list of tracking areas for the MBS service areas mapped from the same geographical areas.' Replace 'based on Associated Session ID and MBS Service Area' with 'based on RAN implementation, e.g., Associated Session ID, or TMGI and MBS Service Area', and add 'For a location dependent MBS session (see Clauses 6.2.3), the AF(s) that create the location dependent MBS sessions towards the participating PLMNs shall supply service areas that contain the same shared radio cells (but may contain different non-shared radio cells).' LiMeng (Huawei) can accept the proposal from Thomas. LiMeng (Huawei) comments LiMeng (Huawei) requests to discuss in CC#4, and suggests r04 + 1. remove the paragraph between the 1st and 2nd bullet; 2. add 'NOTE x: For location dependent broadcast services, the shared NG-RAN is required to determine that the multiple broadcast MBS Sessions via different CNs deliver the same content for location-dependent MBS session with additionally considering the other information (e.g. MBS Service Area), which is up to RAN implementation.' after 2nd bullet. 3. add 'For a location dependent MBS session (see Clauses 6.2.3), the AF(s) that create the location dependentMBS sessions towards the participating PLMNs shall supply MBS Service Areas that point to the same shared radio cells (but may contain different non-shared radio cells)' after figure 6.18-1. Thomas (Nokia) accepts the proposal of LiMeng ==== Comments Deadline ==== LiMeng (Huawei) requests to discuss in CC#4, and suggests r04 + 1. remove the paragraph between the 1st and 2nd bullet; 2. add 'NOTE x: For location dependent broadcast services, the shared NG-RAN is required to determine that the multiple broadcast MBS Sessions via different CNs deliver the same content for location-dependent MBS session with additionally considering the other information (e.g. MBS Service Area), which is up to RAN implementation.' after 2nd bullet. 3. add 'For a location dependent MBS session (see Clauses 6.2.3), the AF(s) that create the location dependentMBS sessions towards the participating PLMNs shall supply MBS Service Areas that point to the same shared radio cells (but may contain different non-shared radio cells)' after figure 6.18-1. | Revised |
| 9.10.2 | S2-2306249 | CR | Approval | 23.247 CR0231R1 (Rel-18, 'B'): Resolving the EN on the MOCN enhancement for the location dependent MBS session | ZTE, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304871r04 + changes, merging S2-2305364. CC#4: Approved | Agreed | |
| 9.10.2 | S2-2305364 | CR | Approval | 23.247 CR0254 (Rel-18, 'F'): Handling of location dependent sessions for Resource sharing across broadcast MBS Sessions during network sharing | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! Merged into S2-2306249 Merge into (revision of) S2-2304871 | LiMeng (Huawei) suggests to merge this document into S2-2304583. Thomas (Nokia) prefers to merge this document into S2-2304871. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.10.2 | - | - | - | CR on configured TMGI relationship | - | - | Docs:=5 | - | |
| 9.10.2 | S2-2304872 | DISCUSSION | Discussion | Discussion on TMGI index for the configuration mechanism in the MOCN enhancement | ZTE | Rel-18 | Noted | Noted | |
| 9.10.2 | S2-2305366 | DISCUSSION | Discussion | TMGI allocation for Resource sharing across broadcast MBS Sessions during network sharing based on configuration | Nokia, Nokia Shanghai-Bell | Rel-18 | Noted | Noted | |
| 9.10.2 | S2-2304873 | CR | Approval | 23.247 CR0232 (Rel-18, 'F'): Resolving the EN on TMGI index and TMGI update for the configuration mechanism in the MOCN enhancement | ZTE | Rel-18 | CC#4: r07 + changes agreed. Revised to S2-2306251. For CC#4 | Thomas (Nokia) objects against r00 and provides r01 LiMeng (Huawei) provides r02 Zhendong (ZTE) provides r03. Thomas (Nokia) provides r04. LiMeng (Huawei) accepts r04. Judy (Ericsson) provides r05 and comment Haris(Qualcomm) comments that r05 is not acceptable Zhendong (ZTE) provides r06. Thomas (Nokia) provides r07, objects against r06 and r05 ==== Revisions Deadline ==== Haris(Qualcomm) is ok with r07. Objects to r05. R06 is possibly incomplete Judy (Ericsson) accept only r05, objects to other revisions. LiMeng (Huawei) asks to check this issue in CC#4. ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2306251 | CR | Approval | 23.247 CR0232R1 (Rel-18, 'F'): Resolving the EN on TMGI index and TMGI update for the configuration mechanism in the MOCN enhancement | ZTE | Rel-18 | Revision of S2-2304873r07 + changes. CC#4: Approved | Agreed | |
| 9.10.2 | S2-2305368 | CR | Approval | 23.247 CR0255 (Rel-18, 'F'): TMGI allocation for Resource sharing across broadcast MBS Sessions during network sharing | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! Noted | Judy (Ericsson) assumes this CR will be NOTED and 4873 is chosen to progress. For the sake of clarity, we object to this CR. Thomas(Nokia) confirms that the CR can be noted, as we use 4873. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.10.2 | - | - | - | Update of Group Message Delivery | - | - | Docs:=4 | - | |
| 9.10.2 | S2-2304328 | CR | Approval | 23.247 CR0220 (Rel-18, 'F'): Update group message delivery procedure. | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! r03 agreed. Revised to S2-2305462. | Judy (Ericsson) provides r01 LiMeng (Ericsson) thanks Judy's update and provides r02 Judy (Ericsson) provides r03 (please ignore r02) and comments LiMeng (Huawei) accepts r03 and clarifies that r02 is provided by LiMeng (Huawei). Judy (Ericsson) thanks LiMeng (Huawei) for clarification ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305462 | CR | Approval | 23.247 CR0220R1 (Rel-18, 'B'): Update group message delivery procedure | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304328r03. Approved | Agreed | |
| 9.10.2 | S2-2304950 | CR | Approval | 23.247 CR0237 (Rel-18, 'C'): Clarification of applications for Group Message Delivery | KPN N.V. | Rel-18 | r04 agreed. Revised to S2-2305463. | LiMeng (Huawei) comments and provides r02. LiMeng (Huawei) corrects that it is r01 that was provided in the last email instead of r02. Judy (Ericsson) comments. Xiaoyan (CATT) provides comments. Thomas (Nokia) provides comments, questions need for the CR. LiMeng (Huawei) clarifies the questions. LiMeng (Huawei) provides r02. Prachi Sachdeva (KPN) provides clarifications on the points raised Haris(Qualcomm) asks why this CR is Cat.C Thomas(Nokia) thanks Prachi Sachdeva for his answers. Judy (Ericsson) has the same question as Haris on CR Cat and comments to r02 Prachi (KPN) responds to comments from Judy and Haris Prachi (KPN) provides R03 Judy (Ericsson) responds to Prachi (KPN) and provides r04 ==== Revisions Deadline ==== Judy (Ericsson) can only live with r04. Prachi (KPN) accepts r04 from Judy. Acceptable versions for KPN are r03 and r04 ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305463 | CR | Approval | 23.247 CR0237R1 (Rel-18, 'D'): Clarification of applications for Group Message Delivery | KPN N.V. | Rel-18 | Revision of S2-2304950r04. Approved | Agreed | |
| 9.10.2 | - | - | - | Resolve EN on eDRX > 10.24s | - | - | Docs:=4 | - | |
| 9.10.2 | S2-2304325 | DISCUSSION | Discussion | Discussion on the open issues of KI#5 | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.10.2 | S2-2305377 | CR | Approval | 23.247 CR0260 (Rel-18, 'F'): Resolving open issues for Multicast MBS procedures for UEs using power saving functions | Nokia, Nokia Shanghai-bell | Rel-18 | r03 agreed. Revised to S2-2305464, merging S2-2304327 | LiMeng (Huawei) asks questions. Thomas (Nokia) answers to LiMeng. Haris(Qualcomm) responds to LiMeng LiMeng (Huawei) responds to Haris and Thomas. Thomas(Nokia) replies to LiMeng. Haris(Qualcomm) agrees with Thomas and proposes r01 Thomas(Nokia) provides r02 Judy (Ericsson) comments Thomas(Nokia) provides r03 ==== Revisions Deadline ==== Haris(Qualcomm) is ok with r03. Agrees with Judy's issue that can be discussed in future since it applies in multicast Thomas(Nokia) is fine with r03, objects to r02 (for the sake of completeness) ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305464 | CR | Approval | 23.247 CR0260R1 (Rel-18, 'F'): Resolving open issues for Multicast MBS procedures for UEs using power saving functions | Nokia, Nokia Shanghai-Bell, Huawei, Qualcomm | Rel-18 | Revision of S2-2305377r03, merging S2-2304327. Approved | Agreed | |
| 9.10.2 | S2-2304327 | CR | Approval | 23.247 CR0219 (Rel-18, 'F'): Update the EN for the support of eDRX of KI#5 | Huawei, HiSilicon | Rel-18 | Merged into S2-2305464 | Thomas (Nokia) comments that this CR competes with S2-2305377 and both should be merged. Raises concerns against one aspect of this CR ==== Revisions Deadline ==== LiMeng (Huawei) is OK to merge this document into 5377. ==== Comments Deadline ==== | Merged |
| 9.10.2 | - | - | - | Scheduled Activation times | - | - | Docs:=6 | - | |
| 9.10.2 | S2-2305372 | CR | Approval | 23.247 CR0257 (Rel-18, 'F'): Service announcement updates for UE using power saving function | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! Not a CR. Revised to S2-2305392 | Revised | |
| 9.10.2 | S2-2305392 | DISCUSSION | Discussion | Service announcement updates for UE using power saving function | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305372. Noted | Noted | |
| 9.10.2 | S2-2305374 | CR | Approval | 23.247 CR0258 (Rel-18, 'F'): Update of MBS service announcement for capability-limited devices | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error!. Check Affected Clauses! r01 agreed. Revised to S2-2305465. | Xiaoyan (CATT) provides r01 Thomas(Nokia) replies to Xiaoyan and raises concerns against r01 Judy (Ericsson) asks Xiaoyan (CATT) question ==== Revisions Deadline ==== Xiaoyan (CATT) objects to r00. Thomas(Nokia) objects to r01. Suggest agreeing r01 + Add at the end of new text 'via multicast or broadcast'. Xiaoyan (CATT) is fine with the suggestion from Thomas(Nokia).. ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305465 | CR | Approval | 23.247 CR0258R1 (Rel-18, 'B'): Update of MBS service announcement for capability-limited devices | Nokia, Nokia Shanghai-Bell, CATT | Rel-18 | Revision of S2-2305374r01. Approved | Agreed | |
| 9.10.2 | S2-2305375 | CR | Approval | 23.247 CR0259 (Rel-18, 'F'): MBS session activation for UEs using power saving functions | Nokia, Nokia Shanghai-Bell | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305466. | Judy (Ericsson) asks questions Thomas (Nokia) replies to Judy Judy (Ericsson) clarifies the question to Thomas (Nokia) Judy (Ericsson) provides r01 Thomas(Nokia) accepts r01. Thomas (Nokia) corrects himself, does not accept r01 and provides r02 Judy (Ericsson) comments on r02 Thomas(Nokia) replies to Judy ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2305466 | CR | Approval | 23.247 CR0259R1 (Rel-18, 'B'): MBS session activation for UEs using power saving functions | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305375r02. Approved | Agreed | |
| 9.10.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=12 | - | |
| 9.10.2 | S2-2304875 | CR | Approval | 23.247 CR0234 (Rel-18, 'F'): Clarifying the UE kept in connected and resolving the EN. | ZTE | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304876 | CR | Approval | 23.247 CR0235 (Rel-18, 'F'): Resolving the EN on the RRC resume for RRC inactive reception | ZTE | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2305157 | CR | Approval | 23.247 CR0195R1 (Rel-18, 'B'): Multicast session status sync between UE and network | CATT | Rel-18 | Revision of S2-2302792 from S2#155 | NOT HANDLED | |
| 9.10.2 | S2-2304322 | CR | Approval | 23.247 CR0215 (Rel-18, 'F'): Update the procedures of KI#2 | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304874 | CR | Approval | 23.247 CR0233 (Rel-18, 'F'): Clarification on the N3mb tunnel management for the MOCN enhancement | ZTE | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304324 | CR | Approval | 23.247 CR0217 (Rel-18, 'F'): Update the EN for location dependent MBS service of KI#2 | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.10.2 | S2-2304323 | CR | Approval | 23.247 CR0216 (Rel-18, 'F'): Update the EN for TMGI allocation of KI#2 | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! | Haris(Qualcomm) provides r01 LiMeng (Huawei) thanks Haris for r01 and now we use S2-2304873 as the basis for further discussion. | NOT HANDLED |
| 9.10.2 | S2-2304154 | CR | Approval | 23.247 CR0211 (Rel-18, 'F'): KI#4 Service announcement information from NEF to AF in group message delivery | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304206 | CR | Approval | 23.247 CR0212 (Rel-18, 'C'): Remove EN for support of CM-CONNECTED with RRC_INACTIVE state with eDRX > 10.24s | Qualcomm Incorporated | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304587 | CR | Approval | 23.247 CR0228 (Rel-18, 'B'): Resolving EN on service announcement for MBS reception by UEs using power saving functions | CATT | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304326 | CR | Approval | 23.247 CR0218 (Rel-18, 'F'): Remove the EN for asynchronous service announcement between UE and AF | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.10.2 | S2-2304877 | CR | Approval | 23.247 CR0236 (Rel-18, 'F'): Clarification on EN in the service announcement | ZTE | Rel-18 | NOT HANDLED | ||
| 9.11.1 | - | - | - | Study on Network Slicing Phase 3 (FS_eNS_Ph3) | - | - | Docs:=0 | - | |
| 9.11.2 | - | - | - | Network Slicing Phase 3 (eNS_Ph3) | - | - | Docs:=92 | - | |
| 9.11.2 | - | - | - | KI#1 | - | - | Docs:=24 | - | |
| 9.11.2 | S2-2304598 | DISCUSSION | Discussion | Discussion on slice replacement notification from NSSF | LG Electronics | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2304705 | DISCUSSION | Discussion | On the identification of both the replaced and the Alternative S-NSSAI of sessions in the system | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2304194 | CR | Approval | 23.501 CR4234 (Rel-18, 'F'): Resolving open issues related to Alternative S-NSSAI | Ericsson, ZTE, Lenovo | Rel-18 | r04 agreed. Revised to S2-2306036. | Haiyang (Huawei) provides r01 Alessio(Nokia) provides comments and concerns with this paper. Proposes to use 4726 instead as this CR as is does not seem to provide a complete solution. Dongeun (Samsung) provides comments Peter Hedman (Ericsson) provides reply to Nokia Peter Hedman (Ericsson) provides comments and r02 Alessio(Nokia) provides reply to ericsson Jinguo(ZTE) comments Krisztian (Apple) provides r03. Alessio(Nokia replies to Jinguo(ZTE) that we should not wait for RAN to tell us what we know in sA2: the replacement needs handling in the RAN for AoS reasons and resource management reasons. We also need to signal both replaced and alternative S-NSSAI to RAN and all nodes and UE involved as per our DP in 4705 Alessio(Nokia) objects to r03 as it in fact assumes the original resources are unusable and also there is no AoS restriction according to original AoS. This means also that implicitly this is a feature that can be used for by passible the AoS limitations and provide continuity of service outside AoS that was ruled out in study phase when we discussed the use cases to be covered Jinguo(ZTE) provides r04 Peter Hedman (Ericsson) KI#1 is about slice replacement i.e. new S-NSSAI for the PDU Session is given to RAN and RAN can decide what resources are required for AS there is no need for anything new, option is to remove the PDU Session Modification ==== Revisions Deadline ==== Jinguo(ZTE) suggests to approve r04 which is provided before the deadline. Alessio(Nokia) can live with r04 or also nothing as this is just updating notes (no normative progress). Alessio(Nokia) proposes to note all other revisions than r04 Peter Hedman (Ericsson) can accept r04 (would have preferred r03) Genadi (Lenovo) can accept r04 (in order to have at least one EN removed). Cover page needs update, at least 'Summary of change' and may need to discuss during CC#3/4. Peter Hedman (Ericsson) r04+cover sheet cleanup is of course ok ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306036 | CR | Approval | 23.501 CR4234R1 (Rel-18, 'F'): Resolving open issues related to Alternative S-NSSAI | Ericsson, ZTE, Lenovo, Apple | Rel-18 | Revision of S2-2304194r04. Approved | Agreed | |
| 9.11.2 | S2-2304521 | CR | Approval | 23.501 CR4335 (Rel-18, 'B'): Support of network slice replacement for handover | Huawei, HiSilicon | Rel-18 | Postponed | Dongeun (Samsung) comments Haiyang (Huawei) clarifies to Dongeun (Samsung) Peter Hedman (Ericsson) provides r01 Jinguo(ZTE) is ok with r01 Dongeun (Samsung) comments and provides r02 Genadi (Lenovo) provides r03. Alessio(Nokia) would like to understand the problem space before agreeing to any solution... what is the problem we solve? For now we do not agree any solution till we know the use case we are addressing here Peter Hedman (Ericsson) provides reply Haiyang (Huawei) is OK with r03. ==== Revisions Deadline ==== Myungjune (LGE) supports r03 and wants to cosign. Alessio(Nokia) comments that this basically instructs implementors to not delay the handover if there is right at decision to replace time the Handover in preparation phase (HO already started?). noting that there can also be intra-gNB Handovers the only thing to say is ' network slice replacement does not impact ongoing Handovers'. This is even easier. However this CR text assumes the AMF is always involved in handover - Now the question is whether the AMF can see there is intra-gNB HO and unwantedly it impacts the handover by replacing slice? Maybe we postpone this paper to discuss this more. We Propose to postpone this paper to have a complete solution. Haiyang (Huawei) provides reply Alessio(Nokia) comments that there seems no clarity on the use case/scenario then as I got two different answers on the scenario. One more reason to postpone. Peter Hedman (Ericsson) ok with r03 Genadi (Lenovo) provides comments to Alessio (Nokia). Peter Hedman (Ericsson) provides comments Alessio(Nokia) I would be ok with r03 if we make a generic statement which is independent on type of handover like: 'Ongoing handover procedures for PDU sessions of a S-NSSAI shall not be interrupted when this S-NSSAI replacement occurs in the 5GC'. Then remove 'During UE mobility in CM-CONNECTED state, when the AMF determines that the PDU Session to be switched in the Target NG-RAN is associated with an S-NSSAI that is to be replaced with the Alternative S-NSSAI, the following applies: - During the handover procedure, the (T-)AMF may still continue the handover procedure using the original S-NSSAI even if this S-NSSAI is to be replaced, e.g. due to unavailable or congested. - After the completion of the handover procedure, the (T-)AMF performs Network Slice Replacement for the existing PDU session as described above. ' Haiyang (Huawei) provides comments ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2304726 | CR | Approval | 23.501 CR4386 (Rel-18, 'C'): Clarifications on the handling of the Alternative S-NSSAI | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Dongeun (Samsung) comments Myungjune (LGE) comments. Haiyang (Huawei) comments. Genadi (Lenovo) provides comments and a suggestion for a revision. Jinguo(ZTE) provides comment Iskren (NEC) provides comment. Peter Hedman (Ericsson) provides comments and agree with previous comments i.e. therefore better to use another CR and note this one Alessio(Nokia) replies to Samsung comments and provides r01 Alessio(Nokia) comments and invites to consider r01 alessio(Nokia) believes the r01 is aligned to the suggestion except that we still believe the UE needs to know what RAN resources to consider (otherwise the UE may use the new slice resources for RACH and the network instead would like it to use the old slice resources only. Does it make sense? Alessio(noia) replies to jinguo that there is end to end impact that we need to consider when a replacement occurs. If we do not take care now the feature is not deployable as ti may create instability in rAN when the CN resources are the only reason for change as it is assumed in this work now Alessio(Nokia) strongly disagrees with Peter as sending only to new slice resources does not allow the RAN to apply the policies of limitation of AoS and resource anamgent taking old and new slice into account (what other slice this is a replacement of?) basiscally Ericsson is forcing the CN issue to caus resources reorganizations in alternative and original slice also in the rAN when this is not in scope of this work. Myungjune (LGE) replies to Alessio(Nokia) Peter Hedman (Ericsson) provides comments and objects to the CR (r00, r01) Genadi (Lenovo) comments that r01 goes to the right direction, but still does not agree that 'Replacement Assistance Information' is sent to the RAN and that the updated NSAG should consider the replaced S-NSSAI. Jinguo(ZTE) comments on the RFSP part. Iskren (NEC) This CR is not acceptable. alessio(Nokia) comments on Jinguo's comments ==== Revisions Deadline ==== Peter Hedman (Ericsson) propose to note the CR, and we re-discuss the NSAG and RRM aspects at the next meeting Alessio(nokia) can only state this is important aspect of the feature. Without this the rAN resource usage is impossible to be controlled appropriately. This feature needs to take care of RAN resource handling ... ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304912 | CR | Approval | 23.501 CR4432 (Rel-18, 'B'): 23501 Network slice replacement update for NSSF | vivo | Rel-18 | Postponed | Dongeun (Samsung) comments Jinguo(ZTE) share same conern as Dongeun (Samsung) Genadi (Lenovo) provides comments. Suggests a way forward for a revision. Xiaowen (vivo) responses Xiaowen (vivo) provides r01 Peter Hedman (Ericsson) provides comments Xiaowen (vivo) responses to Peter Hedman (Ericsson) and provide r02. Haiyang (Huawei) provides comments Genadi (Lenovo) provides r03. Jinguo(ZTE) comments that this CR is not agreeable. Xiaowen (vivo) is ok for r03 provided by Genadi (Lenovo). Xiaowen (vivo) responses to Jinguo (ZTE) and Haiyang (Huawei) Dongeun (Samsung) agrees with ZTE and propose to note the CR. Xiaowen (vivo) replies to Dongeun (Samsung) Alessio(Nokia) comments and proposes that a choice is made between NSSF availability approach and this approach for now we assume the standing agreement is NSSF availability service is the way NSSF plays a reole and this CR therefore is conflicting with that Jinguo(ZTE) replies to Xiaowen Xiaowen (vivo) responses to Nokia Alessio(Nokia) asks whether this is to address a limited amount of time when the request came in before the notify arrived at aMF? I guess that update of the UEs already registered can happen anyhow so we do not need this to cover this corner case. Xiaowen (vivo) replies and provide R04 ==== Revisions Deadline ==== Jinguo(ZTE) comments that r04 is still unclear. Jinguo(ZTE) suggest to postpone this paper, i.e. no revision is acceptable. Alessio(Nokia) cna make oit easier for yannik to conclude on this : this CR seems to introduce a new way for NSSF to be used in a reactive (request response) way rather than proactive (notify). This was not discussed so far and it creates confusion . we propose to not and if this makese sens ewe will see down the road. Xiaowen (vivo) replies.I'm fine to postpone it this meeting ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2304596 | CR | Approval | 23.501 CR4354 (Rel-18, 'C'): Explicit subscription to NSSF for network slice instance replacement | LG Electronics | Rel-18 | Postponed | Haiyang (Huawei) provides r01 Dongeun (Samsung) comments Myungjune (LGE) is ok with r01 and replies to Dongeun (Samsung) Myungjune (LGE) replies to Dongeun (Samsung) Peter Hedman (Ericsson) provides comments Myungjune (LGE) replies to Peter Hedman (Ericsson) Jinguo(ZTE) comments Myungjune (LGE) replies to Jinguo(ZTE) and provides r02: ==== Revisions Deadline ==== Jinguo(ZTE) comments on r02 Myungjune (LGE) replies to Jinguo (ZTE) Peter Hedman (Ericsson) ok with r02 or to postpone to find better place for the text Jinguo(ZTE) suggests to postpone and find better place for the text at next meeting. Myungjune (LGE) suggests to techinically endorse Jinguo(ZTE) is ok to techinically endorse ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2304520 | CR | Approval | 23.502 CR4024 (Rel-18, 'B'): Change of Network Slice instance for PDU sessions | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306037. | George Foti (Ericsson) provides comments Myungjune (LGE) provides comments Haiyang (Huawei) provides r01 George (Ericsson) provides comments Myungjune (LGE) asks question for clarification Haiyang (Huawei) provides r02 George (Ericsson) not OK with r02. Additional comments below. Haiyang (Huawei) comments to George (Ericsson) George (Ericsson) provides respobse Myungjune (LGE) comments Haiyang (Huawei) provides r03 Haiyang (Huawei) responds to George (Ericsson) ==== Revisions Deadline ==== Myungjune (LGE) proposes to postpone this CR. Jinguo(ZTE) suggest to remove the changes in clause 5.2.16.3.4 to avoid overlapping with 4563. Myungjune (LGE) is ok with Jinguo (ZTE)'s suggestion, i.e. remove the changes in clause 5.2.16.3.4 to avoid overlapping with 4563. Haiyang (Huawei) provides r04 (which is r03 + removing the changes in clause 5.2.16.3.4) based on previous discussion. Alessio(Nokia) provides r05 which is on top of r04 to remove the normative statement the AMF REPALCES slices if NSI are not available (it may replace) and fixes text in Notify operation Peter Hedman (Ericsson) provides comments whether clause 4.3.2.2.x should be on 4..3.x level as not only establishment? Haiyang (Huawei) clarifies to Peter Hedman (Ericsson) , is also OK with r05 (which is r03 + removing the changes in clause 5.2.16.3.4) + makes slice replacement a 'MAY'+ fixes text in notify operation clause) Peter Hedman (Ericsson) provides reply Haiyang (Huawei) responds to Peter Hedman (Ericsson) George (Ericsson) asks question ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306037 | CR | Approval | 23.502 CR4024R1 (Rel-18, 'B'): Change of Network Slice instance for PDU sessions | Huawei, HiSilicon | Rel-18 | Revision of S2-2304520r03. Approved | Agreed | |
| 9.11.2 | S2-2304703 | CR | Approval | 23.502 CR4059 (Rel-18, 'B'): Support of determining Alternative S-NSSAI | Samsung, NEC, Verizon | Rel-18 | r05 agreed. Revised to S2-2306038. | Haiyang (Huawei) comments Dongeun (Samsung) provides r01 Jinguo(ZTE) provides comment and provide r02 Dongeun (Samsung) replies to Jinguo (ZTE) and provides r03 Alessio(Nokia) can live with r03. The AMF preference to select SMFs supporting slice replacement is noted. The only question is whether this can prevent selection of a SMF (will a note be needed to state that tis may be problematic e.g. for home routed?). of course this can be subject of CAT F down the road. Peter Hedman (Ericsson) provides comments and r04 Dongeun (Samsung) is ok with r04 Jinguo(ZTE) provides r05 with cleanup Dongeun (Samsung) is fine with r05 ==== Revisions Deadline ==== Peter Hedman (Ericsson) r05 is ok ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306038 | CR | Approval | 23.502 CR4059R1 (Rel-18, 'B'): Support of determining alternative S-NSSAI | Samsung, NEC, Verizon, ZTE | Rel-18 | Revision of S2-2304703r05. Approved | Agreed | |
| 9.11.2 | S2-2305143 | CR | Approval | 23.502 CR4113 (Rel-18, 'B'): Support of network slice replacement for non roaming case | ZTE, LG Electronics, NEC | Rel-18 | r08 agreed. Revised to S2-2306039. | George Foti (Ericsson) provides comments Jinguo(ZTE) provides r01 Myungjune (LGE) comments Dongeun (Samsung) comments Jinguo(ZTE) replies and provides r02 George (Ericsson) provides comments Myungjune replies to Jinguo (ZTE) Jinguo(ZTE) replies to Dongeun, Myungjune and George, provide r03 Jinguo(ZTE) replies to George(Ericsson) Jinguo(ZTE) provides r04 Dongeun (Samsung) provides comments Alessio(Nokia) agrees with Dongeun (Samsung) to postpone the CR. It is not clear why so many %01 overlapping pieces of text need to be in here. Jinguo(ZTE) suggest to approve this 502 CR at this meeting. Dongeun (Samsung) provides r05 Genadi (Lenovo) provides r06 including some clarifications. Jinguo(ZTE) is fine with r06. George (Ericsson) provides 407. Added Ericsson as consigner alessio (nokia) provides r08 George (Ericsson) Ask what are the changes ==== Revisions Deadline ==== Jinguo(ZTE) is fine with r08. George Foti (Ericsson) Ericsson can accept r08 Myungjune (LGE) comments on r08. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306039 | CR | Approval | 23.502 CR4113R1 (Rel-18, 'B'): Support of network slice replacement for non roaming case | ZTE, LG Electronics, NEC, Samsung, Ericsson | Rel-18 | Revision of S2-2305143r08. Approved | Agreed | |
| 9.11.2 | S2-2304773 | CR | Approval | 23.502 CR4067 (Rel-18, 'B'): Support of slice replacement for new PDU Sessions | Samsung | Rel-18 | r10 agreed. Revised to S2-2306040. | George Foti (Ericsson) provides comments Iskren (NEC) provides comments. Dongeun (Samsung) provides comments. Yannick (Convenor): To record that r01 was provided by Dongeun (Samsung). George (Ericsson) provides comments Genadi (Lenovo) provides comments to r01. Myungjune comments Alessio(nokia) comments that for us if a slice replacement is occurring the PDU session shall include the soriginal and alternative slice S-NSSAIs so this is clear it is a replacement slice session. This can be used for charging purposes and differentiation from native sessions Iskren (NEC) comments Jinguo(ZTE) provides r04, and ask to ignore r02/r03. Alessio(nokia) can accept r04 as a baseline Iskren (NEC) provides r05 with some editorial corrections. Dongeun (Samsung) comments George Foti (Ericsson) provides r06. Added Ericsson and minor editorial. The old S-NSSAI can be used in charging records or stats. Dongeun (Samsung) provides r07. alessio (Nokia) provides r09 to support the paper and provide some small changes. Dongeun (Samsung) provides r10 George (Ericsson) agree with Jinguo. George (Ericsson) We are only Ok with r06 . Additional comments below. ==== Revisions Deadline ==== George Foti (Ericsson) proposes to postpone the CR. See comments below Dongeun (Samsung) replies to George Foti (Ericsson) and suggest to agree r10 Myungjune (LGE) is ok with r07. Myungjune (LGE) is ok with r10 and wants to cosign. Dongeun (Samsung) replies to Myungjune (LGE) Jinguo(ZTE)suggests to approve r10 Alessio(Nokia) ok to approve r10 with the changes : If the AMF determined to replace the S-NSSAI received from the UE with an Alternative S-NSSAI and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends the S-NSSAI value of the Alternative S-NSSAI to the SMF. If the Alternative S-NSSAI and the S-NSSAI is provided by the UE and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends both the S-NSSAI value of the Alternative S-NSSAI and the S-NSSAI value of the S-NSSAI received from the UE to the SMF. To If the AMF determined to replace the S-NSSAI received from the UE with an Alternative S-NSSAI and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends the S-NSSAI and the Alternative S-NSSAI to the SMF. If the Alternative S-NSSAI and the S-NSSAI is provided by the UE and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends both the S-NSSAI value of the Alternative S-NSSAI and the S-NSSAI value of the S-NSSAI received from the UE to the SMF. And The S-NSSAI value of the Alternative S-NSSAI if the SMF has received the Alternative S-NSSAI from the AMF. Changed to The S-NSSAI value of the Alternative S-NSSAI is also included if the AMF determined to replace the S-NSSAI with an Alternative S-NSSAI Dongeun(Samsung) replies to Alession (Nokia) and provides r11 which is r10 + AMF sends both the Alternative S-NSSAI and the S-NSSAI to the SMF (in the changes in step 3 of 4.3.2.2.1) George (Ericsson) Ericsson would accept r10. Please add Ericsson as co-signer. Alessio(nokia) also asks this other missed thing to be corrected in r11 (already mentioned for r10) Dongeun (Samsung) replies to Alessio (Nokia) and suggest to approve r11 Dongeun (Samsung) replies to Iskren (NEC) George (Ericsson) I agree. Not OK in a specification. Alessio(nokia) comments that then we should remove the whole text so r11 without the text 'The S-NSSAI value of the Alternative S-NSSAI if the SMF has received the Alternative S-NSSAI from the AMF' because it is unclear whether the original S-NSSAI is also there or not in the paragraph the text is in. also a verb is missing . Iskren (NEC) suggests 'S-NSSAI value of the Alternative S-NSSAI' to be replaced with 'Alternative S-NSSAI' Alessio(Nokia) then with the clarification the text becomes technically unacceptable as the mapping becomes invisible in the RAN. So let's remove this. Dongeun (Samsung) replies to Alessio(Nokia) that the text that is requested to be removed is simply an alignment with the 501 description Jinguo(ZTE) agree with Dongeun. Further work on the EN are needed at next meeting. George (Ericsson) Asks a question,. We keep updating after the deadline, So which one is it now that we should look at. Alessio(Nokia) then can accept R11 in drafts folder and remove the text 'The S-NSSAI value of the Alternative S-NSSAI if the SMF has received the Alternative S-NSSAI from the AMF.' + instead of removed text to add an editor's note stating: ' Editor's note: which S-NSSAI(s) are sent to the NG-RAN in N2 information is subject to further discussion in TS 23.501' George (Ericsson) We object to r11. Now we are sending both old slices and alternative slice to NGRAN impacting NGAP and without any explanation what RAN would do with it. So not even an EN is acceptable. George (Ericsson) Ericsson accepts only r10 Dongeun (Samsung) provides r12 and replies to George (Ericsson) George (Ericsson) we can accept r12; the text in step 2 can be much better restructured and simplified. But we can do that at the next meeting. When one have too any Ifs in a clause it becomes hard to follow. Alessio(Nokia) I am starting to get lost in the revisions. Really can you just do what I had asked to do on top of R11? If you want I can give you the revision in drafts. Jinguo(ZTE) suggest to approve r10 for this meeting and further clarify at next meeting. Please note May meeting will be very busy. We can't start from scratch.. Alessio(Nokia) asks just to update r11 as requested. It seems fais to indicate as open issue in 502 open issues in 501 Dongeun (Samung) agrees with Jinguo(ZTE) and suggest to agree on r10 and work further in the next meeting. Alessio(Nokia) objects to r10. Dongeun (Samsung) provides r13 (r11 + removal of what to be included in the N2 SM message) George (Ericsson) asks question. SO now the alternative slice is not sent to NGRAN or what am I Missing. Dongeun (Samsung) replies to George (Ericsson) that it is right for r13 as the text is removed. George (Ericsson) we are Ok with r13. But no more revisions. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306040 | CR | Approval | 23.502 CR4067R1 (Rel-18, 'B'): Support of slice replacement for new PDU Sessions | Samsung, ZTE, NEC, Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304773r10. Approved | Agreed | |
| 9.11.2 | S2-2304563 | CR | Approval | 23.502 CR3825R3 (Rel-18, 'B'): Introduction of Alternative S-NSSAI replacement determined by NSSF | Lenovo, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2302800 from S2#155. r01 agreed. Revised to S2-2306041. | Peter Hedman (Ericsson) provides r01 Jinguo(ZTE) provides comment Peter Hedman (Ericsson) provides comments Genadi (Lenovo) provides comment to Peter Hedman (Ericsson) and Jinguo(ZTE). Jinguo(ZTE) thinks r01 is ok. Jinguo (ZTE) provides reply ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r01, but thinks more work needed (can be fixed in May) ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306041 | CR | Approval | 23.502 CR3825R4 (Rel-18, 'B'): Introduction of Alternative S-NSSAI replacement determined by NSSF | Lenovo, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304563r01. Approved | Agreed | |
| 9.11.2 | S2-2305044 | CR | Approval | 23.502 CR3857R2 (Rel-18, 'B'): Alternative S-NSSAI provision to the UE | NEC | Rel-18 | Revision of S2-2302452 from S2#155. r09 agreed. Revised to S2-2306042. | Jinguo(ZTE) corrects the tdoc number in title. The comment from Genadi is for 5044, not 5144. Genadi (Lenovo) re-sends the comments to 5044 due to wrong paper reference. Iskren (NEC) answers comments by Genadi (Lenovo) and provides r01. George (Ericsson) provides questions on r01. Myungjune (LGE) comments and provides r02. Iskren (NEC) answers comments. Genadi (Lenovo) provides comments and r03. Iskren (NEC) provides comments. Dongeun (Samsung) comments Myungjune (LGE) questions on r03. George (Ericsson) provides comments Genadi (Lenovo) responds to Myungjune (LGE). Genadi (Lenovo) responds to Iskren (NEC) on the Mapping Of Configured Alternative NSSAI. Genadi (Lenovo) provides comments to George (Ericsson) and new suggestion. Genadi (Lenovo) provides comments to Dongeun (Samsung). George (Ericsson) provides comments inline Iskren (NEC) provides r04 Iskren (NEC) comments Jinguo(ZTE) comments and provide r05 based on r02 Iskren (NEC) provides r06 Iskren (NEC) provides r07 Alessio (NEC) provides r07 Iskren (NEC) is OK with r07. Genadi (Lenovo) provides comments to Jinguo(ZTE), Alessio (Nokia) and r08. George (Ericsson) is OK with r08. Genadi is right. We have to support both cases. That's what we have defined. Jinguo(ZTE) provides r09 Alessio(Nokia) not enthusiast to use the encoding as a way to describe the stage two but I can live with r09. I normally prefer to include the conceptual level description of info rather than the encoding. Genadi (Lenovo) is fine with r09. George (Ericsson) asks a question. Can someone explain what will RAN do with the alternative slice. We don't pass thing around without explaining the behavior. If there is none specified than why are we passing it. And this must be stated o 23.501 to have it now here. ==== Revisions Deadline ==== George Foti (Ericsson) Can accept r09 Myungjune (LGE) is ok with r09 Dongeun (Samsung) is ok with r09 and asks to co-sign. Iskren (NEC) is ok with r09. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306042 | CR | Approval | 23.502 CR3857R3 (Rel-18, 'B'): Alternative S-NSSAI provision to the UE | NEC, LG Electronics, ZTE, Lenovo, Samsung | Rel-18 | Revision of S2-2305044r09. Approved | Agreed | |
| 9.11.2 | S2-2304704 | CR | Approval | 23.503 CR0991 (Rel-18, 'B'): Support of determining Alternative S-NSSAI | Samsung, NEC, Verizon | Rel-18 | r04 agreed. Revised to S2-2306043. | Haiyang (Huawei) provides questions. Dongeun (Samsung) replies to Haiyang (Huawei) Haiyang (Huawei) provides comments. Dongeun (Samsung) provides r01 Peter Hedman (Ericsson) provides comments Jinguo(ZTE) provides comments Haiyang (Huawei) comments Jinguo(ZTE) provides r02 Dongeun (Samsung) provides r03 Alessio(Nokia) can accept r02 only at this meeting. at a future meeting we can discuss whether the option the AMF provides the candidate S-NSSAIs is needed. Dongeun (Samsung) replies to Alessio(Nokia) Peter Hedman (Ericsson) provides comments that r03 seems not to include AMF sending the candidate S-NSSAI to PCF Alessio(Nokia) can be ok with R03 Dongeun (Samsung) provides r04 just to clean-up ==== Revisions Deadline ==== Peter Hedman (Ericsson) r04 ok, but there is some wording that may benefiit from updates that can be done at the next meeting. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306043 | CR | Approval | 23.503 CR0991R1 (Rel-18, 'B'): Support of determining alternative S-NSSAI | Samsung, NEC, Verizon | Rel-18 | Revision of S2-2304704r04. Approved | Agreed | |
| 9.11.2 | S2-2305144 | CR | Approval | 23.503 CR1023 (Rel-18, 'B'): SM policy for network slice replacement | ZTE | Rel-18 | r06 agreed. Revised to S2-2306044. | Myungjune (LGE) comments. Jinguo(ZTE) replies to Myungjune (LGE) Haiyang (Huawei) comments Dongeun (Samsung) comments Genadi (Lenovo) provides comments. George (Ericsson) provides comments. This is for 23.503 and not 23.502. Jinguo(ZTE) provides r01 Jinguo(ZTE) provides r03 and requests to ignore r02 Dongeun (Samsung) provides concerns Peter Hedman (Ericsson) provides comments Jinguo(ZTE) provides r04 Dongeun (Samsung) provides r05 Jinguo(ZTE) provides r06 ==== Revisions Deadline ==== Dongeun (Samsung) is ok with r06 and requests to add Samsung in the co-source list. Peter Hedman (Ericsson) ok with r06 ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306044 | CR | Approval | 23.503 CR1023R1 (Rel-18, 'B'): SM policy for network slice replacement | ZTE,Samsung | Rel-18 | Revision of S2-2305144r06. Approved | Agreed | |
| 9.11.2 | - | - | - | KI#3 | - | - | Docs:=14 | - | |
| 9.11.2 | S2-2304702 | DISCUSSION | Discussion | Connected mode support when a slice is not uniformly supported in a RA or not uniformly available in a TA | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Stefano (Qualcomm) provides comments Alessio(Nokia) yes it is related and we should adopt this proposal as the alternative is not efficient and probably not going to work. The Handover working will rely on the knowledge of the partially allowed slices and allowed slices so we can retain sessions for partially allowed slices in the UE context to enable the resumption when goes into areas of availability. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2303958 | LS In | Action | LS from RAN WG3: Reply LS on Support of network slices which have area of service not matching deployed tracking areas | RAN WG3 (R3-230899) | Rel-18 | Response drafted in S2-2304197. Final response in S2-2306045 | Replied to | |
| 9.11.2 | S2-2304197 | LS OUT | Approval | [DRAFT] Reply LS on Support of network slices which have area of service not matching deployed tracking areas | Ericsson | Rel-18 | Response to S2-2303958. r02 agreed. Revised to S2-2306045. | Alessio(nokia) cannot agree to the r00 version and provides r01 to indicate how the system should behave without the overhead of systematically and universally use AoI indications for all procedures in connected mode where partially allowed slices at TA level or any allowed or partially allowed slices at NS-AoS smaller than TA level are involved. Peter Hedman (Ericsson) provides comments and cannot agree on r01. Alessio(Nokia) comments that this is how the feature can work and in line with the SA plenary guidance to have efficient solutions . it seems indeed we are not complying with SA guidance if we systematically adopt inefficient solutions under your guidance. Jinguo(ZTE) suggest to conclude the CR first and update the LS accordingly Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== Jinguo(ZTE) is ok with r02 Alessio(Nokia) can live with r02 with the proposed update in drafts folder to clarify that the CN is informed during handover in an efficient manner Haiyang (Huawei) is OK with r02 Ashok (Samsung) comments on r02 Peter Hedman (Ericsson) provides comments and ok with r00, r02 and object to r01 Ashok (Samsung) responds to Peter Alessio(Nokia) accepts only r02 with changes in DRAFTS Peter Hedman (Ericsson) propose to agree r02 + remove second paragraph in answer. Haiyang (Huawei) is OK with r02 + remove second paragraph in answer. Alessio(Nokia) is ok with 'agree r02 + remove second paragraph in answer' as this is factual. But of course there was a lot of value to 3GPP and the community to ensure the solution we are aiming for should be efficient and also explain what it looks like. But we can contribute our ideas as individual companies I guess. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306045 | LS OUT | Approval | Reply LS on Support of network slices which have area of service not matching deployed tracking areas | SA WG2 | Rel-18 | Revision of S2-2304197r02. Approved. This LS OUT was approved | Approved | |
| 9.11.2 | S2-2304196 | CR | Approval | 23.501 CR4236 (Rel-18, 'C'): Resolving open issues for Network Slices with Network Slice Area of Service not matching deployed TAs | Ericsson, Apple | Rel-18 | r01 agreed. Revised to S2-2306046. | Stefano (Qualcomm) provides comments and suggests we first address the issues related to the RFSP for the Partially Allowed NSSAI. Alessio(Nokia) asks why this is more realistic... in fact we have the opposite view. Alessio(Nokia) comments that this CR takes us backwards from the agreements reached at last meeting by bundling together the partially allowed and allowed NSSAI slices handling. Also the Target NSSAI scope should not be changed by this feature. The CR itself says this is useful only if RFSP does not take into account the Partially allowed S-NSSAIs. but the RAN gets the partially allowed S-NSSAIs and the RFSP can take this into account no problem. Also now the target NSSAI seems to be applicable not only inside the RA but even inside the RA. This is to us not needed at all and will also conflict with other usage outside the RA. Alessio(Nokia) comments that this CR takes us backwards from the agreements reached at last meeting by bundling together the partially allowed and allowed NSSAI slices handling. Also the Target NSSAI scope should not be changed by this feature. The CR itself says this is useful only if RFSP does not take into account the Partially allowed S-NSSAIs. but the RAN gets the partially allowed S-NSSAIs and the RFSP can take this into account no problem. Also now the target NSSAI seems to be applicable not only to cause redirection inside the RA but even inside the TA. This is to us not needed at all and will also conflict with other usage to cause redirection outside the RA. In short we see this enhancement of Target NSSAI not needed. Only say that it may include also partially allowed slices in addition to allowed slices when used to attempt to also use slices outside the RA. Peter Hedman (Ericsson) provides reply to Nokia Alessio(Nokia) cannot accept sending target NSSAI unless there is a Slice outside the RA. Inside RA the RFSP of the Allowed+partially allowed S-NSSAI is sufficient. We leave open sending the Partially rejected s-NSSAI as additional information for this meeting but also knowing what is partially rejected helps. Alessio(Nokia) replies that a UE with an allowed NSSAI is a cell where the S-NSSAI is not available is a change of current logic. If this was a good logic we should also have a rejected s-NSSAI in RA not being able to be requested even in an area where it is available. But Ericsson does not seem to want that . we need to keep a symmetric behaviour and therefore enable the UE to execute systematic MRU when an allowed NSSAI is not available in the new cell the UE has moved to. in short now the logic should remain as at TA support granularity level but at cell level availability for supporting UEs and we object to anything different than this. Ercisson approach is half hearted as it is at cell level for rejected but at TA level for allowed. Ashok (Samsung) provides comments Jinguo(ZTE) provides comemnt and provide r01 Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) provides replies to Nokia Ashok (Samsung) responds to Peter Alessio(Nokia) comments and explains why nokia prefer their CR and technical approach and find the Ericsson approach inconsistent ==== Revisions Deadline ==== Jinguo(ZTE) suggest to approve r01 which is provided before the deadline. Alessio(Nokia) asks to postpone the CR as there is no agreement on basic technical aspects (like using the availability info for the s-NSSAIs in Allowed NSSAI) and also on the need to now intorduce AoI as basic aspect of Handover in all slices that ahvae NS-AoS < TA (and also for aprtiallyallwoed NSSAI wuith TA level NS-AoS). The DP nokia provided has been ignored and clealy we need to have an efficiency evaluation. The RAN impact in Ue context is similar only we save many messages over NG-AP with Nokia solution. This will be a test case for seriousness of 3GPP to pursue efficient solutions Alessio(nokia) comments that technically speaking Ericsson is ok to have a virtual RA and TA for Rejected S-NSSAI in RA and partially rejected S-NSSAIs in Ra and Partilaly allowed S NSSAI in but not for S-NSSAIs in allowed NSSAI. This is problematic to us. We need a consistent approach across th borad. Cannot single out the allowed NSSAI! Peter Hedman (Ericsson) ok with r00 or r01. Jinguo(ZTE) suggest to approve r01 with the following change: Undo the change in step 1 of clause 5.15.18.3 and keep the EN Peter Hedman (Ericsson) also ok with r01 + 'Undo the change in step 1 of clause 5.15.18.3 and keep the EN' Alessio(Nokia) has more issues with 4196r01 that just AoI. R02 in the drafts folder we could agree with. (it removes the equalization of allowed an partially allowed NSSAI in text and keeps open the handling of allowed NSSAI, ) ==== Comments Deadline ==== Peter Hedman (Ericsson) ok, but I would then also need to keep the EN: 'Editor's note: Logic for when the S-NSSAI is in the Allowed NSSAI is FFS.' As the changes to the two bullets were remopved. | Revised |
| 9.11.2 | S2-2306046 | CR | Approval | 23.501 CR4236R1 (Rel-18, 'C'): Resolving open issues for Network Slices with Network Slice Area of Service not matching deployed TAs | Ericsson, Apple | Rel-18 | Revision of S2-2304196r01. Approved | Agreed | |
| 9.11.2 | S2-2304745 | CR | Approval | 23.501 CR4397 (Rel-18, 'C'): Clarification of the support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Stefano (Qualcomm) provides comments and suggests we first address the issues related to the RFSP for the Partially Allowed NSSAI. Alessio(nokia) comments this is related to solution 2 not solution 1. At lest this is our intention Alessio (Nokia) replies that 'the AMF is not aware of the specific cell the UE is located in wrt the Partially Allowed NSSAI and cannot provide an appropriate RFSP' is probably non existed case if I understand correctly as the RFSP is provide to the RAN when the UE is CM connected and the registration status is known (same as when the allowed NSSAI RFSP is provided) Peter Hedman (Ericsson) provides comments and proposes to use 04196 Alessio(Nokia) believes the comment on per UE behaviour by Peter Hedman (Ericsson) is unclear and not matching our understanding , the MRYU in and out the AoS for allowed and rejected slices is part of current standards and shall remain like that (byu the way we do dod a MRU entering a NS-AoS for a rejected or partially rejected slice so not sure why we cannot do MRYU when exiting for a Allowed slice. The not doing MRU is linked to the support of partial support in RA (allowed is uniformly supported and available in RA and the restriction with cell level info will restrict the availability ) Ashok (Samsung) requests for clarification Jinguo(ZTE) suggest to merge 4745 into 4196. Peter Hedman (Ericsson) provides reply to Alessio Alessio(Nokia) replies to peter Alessio(nokia) prefers to postpone the CRs if there is no agreement really, the issue is we cannot do a random design! Everything must have a consistent logic. we need also to discuss in SA2 the merits of AoI vs the embedded notification in Path switch and PDU SESSION RESOURCE NOTIFY NG-AP messages which is by far more efficient. We have responsibility for the design end to end unless snow we are a rubberstamping unit of RAN groups. No one has been able to say our DP has any problem. ==== Revisions Deadline ==== Peter Hedman (Ericsson) objects to the CR so postpne is ok ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2305111 | CR | Approval | 23.501 CR4487 (Rel-18, 'B'): Updates on S-NSSAI Location Availability information | Samsung | Rel-18 | r01 agreed. Revised to S2-2306047. | Peter Hedman (Ericsson) provides comments Ashok (Samsung) provides response Jinguo(ZTE) suggests to remove the NSSF part Peter Hedman (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306047 | CR | Approval | 23.501 CR4487R1 (Rel-18, 'B'): Updates on S-NSSAI Location Availability information | Samsung | Rel-18 | Revision of S2-2305111r01. Approved | Agreed | |
| 9.11.2 | S2-2304195 | CR | Approval | 23.501 CR4235 (Rel-18, 'F'): Resolving open issues for temporarily available network slices | Ericsson | Rel-18 | Approved | Stefano (Qualcomm) suggests to use 4195 as the basis for the way forward. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.11.2 | S2-2304727 | CR | Approval | 23.501 CR4387 (Rel-18, 'B'): Resolution of editors notes in clause 5.15.16 (temporary network slices) | Nokia Austria | Rel-18 | CR Cover sheet error! Noted | Stefano (Qualcomm) suggests to use 4195 as the basis for the way forward. Peter Hedman (Ericsson) provides comments that the proposal goes against the TR conclusion and the WID. Kundan(NEC) suggests to use 4195 as a baseline CR. Jinguo(ZTE) suggests to use 4195 as a baseline CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304198 | CR | Approval | 23.502 CR3848R2 (Rel-18, 'B'): Support of reduced network slice availability | Ericsson | Rel-18 | Revision of S2-2302973 from S2#155. r01 agreed. Revised to S2-2306048. | Krisztian (Apple) provides r01 to support. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306048 | CR | Approval | 23.502 CR3848R3 (Rel-18, 'B'): Support of reduced network slice availability | Ericsson, Apple | Rel-18 | Revision of S2-2304198r01. Approved | Agreed | |
| 9.11.2 | S2-2304523 | CR | Approval | 23.503 CR0977 (Rel-18, 'B'): URSP handling for legacy UEs | Huawei, HiSilicon, LG Electronics | Rel-18 | Noted | Peter Hedman (Ericsson) provides comments Haiyang (Huawei) replies to Peter Hedman (Ericsson) Peter Hedman (Ericsson) provides r01 Ashok (Samsung) provides r02 Alessio(Nokia) objects to this CR Jinguo(ZTE) also suggest to put the NOTE outside of the table Haiyang (Huawei) provides r03 Krisztian (Apple) shares the concern raised by Alessio (Nokia) and also objects to this CR. Peter Hedman (Ericsson) provides r04 ==== Revisions Deadline ==== Alessio(nokia) proposes to note this CR as it cannot be a CATEGORY B if this is not introducing a new feature. A NOTE cannot be CATEGORY B CR. What feature does this introduce? Haiyang (Huawei) proposes to go with r04 + changing the CAT into 'F' Alessio(Nokia) also has provided other grounds why the proposal is difficult to accept (beyond CR category). In short using the URSP validation criteria for this feature is not sounding possible to us on several grounds due to difficulty to apply this selectively also. Peter Hedman (Ericsson) ok with r04 or r04+change to CR category to F Alessio(Nokia) believes our statements to be true of course so on that basis we still do not agree to this CR. We object to any revision. Also since this is a NOTE not sure why this is needed to make something function at all. Haiyang (Huawei) comments to Alessio(Nokia). Haiyang (Huawei) requests to have a SoH in CC#4 on whether to approve r05(r04 + changing the CAT into 'F') as this issue has already been discussed for several meetings Alessio(Nokia) has fundamental technical issue with adding the note as outlined already, hence we will object and sustain objection to this CR till technical issues are addressed. ==== Comments Deadline ==== | Noted |
| 9.11.2 | - | - | - | KI#4 | - | - | Docs:=9 | - | |
| 9.11.2 | S2-2304957 | CR | Approval | 23.501 CR4442 (Rel-18, 'B'): Hierarchical NSAC Architecture for EPS counting | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306049. | George Foti (Ericsson) provides comments Fenqin (Huawei) provides r01 Iskren (NEC) comments on r01 Fenqin(Huawei) Provides feedback George Foti (Ericsson) provides r02 Fenqin (Huawei) is ok with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306049 | CR | Approval | 23.501 CR4442R1 (Rel-18, 'B'): Hierarchical NSAC Architecture for EPS counting | Huawei, HiSilicon | Rel-18 | Revision of S2-2304957r02. Approved | Agreed | |
| 9.11.2 | S2-2305189 | CR | Approval | 23.501 CR4520 (Rel-18, 'C'): ENS_KI#4_23501_Update of Hierarchical NSAC Architecture | Xiaomi, Samsung | Rel-18 | Noted | George Foti (Ericsson) Object to the CR. The threshold base does not support quota. The primary NSACF stores the info if it does not want to update the threshold, or rejects the request if it can store it or update the threshold. This is clear in 23.501 Jinhua (Xiaomi) replies to George, Jinhua (Xiaomi) replies to George, provides r01 George (Ericsson) propose to note the CR. The note is not needed. It is already explicitly stated in the clause before. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304006 | CR | Approval | 23.502 CR3946 (Rel-18, 'B'): KI#4: Support for Centralized NSACF in multi-service PLMN in non-roaming cases | Ericsson | Rel-18 | r02 agreed. Revised to S2-2306050. | Fenqin (Huawei) provides comments George (Ericsson) provides response Fenqin (Huawei) provides response to George. Alessio (nokia) is ok either way. The styles seem messed up (at least here I see some strange indentation of some paragraph) George (Ericsson) provides r01 considering comments from Alessio and Fenqin Fenqin (Huawei) provides r02 George (Ericsson) provides r01. The added text is confusing. This is centralized Architecture it goes without saying that this is against the PLMN. Fenqin (Huawei) clarify the issue to George. Ashok (Samsung) comments George (Ericsson) provides response. It is a single node. That's implicit. It just update the area in the UE entry. U bring implementation issues that are not needed because that why it is centralized. There is only one entry for a UE maintained. Fenqin (Huawei) clarify further this to George. ==== Revisions Deadline ==== Fenqin (Huawei) give a response to George. George (Ericsson) is OK with r02 at this meeting. George (Ericsson) responds. That correct. But some (privately) don't want r03. So in the interest of progress I am OK with r02. Fenqin (Huawei) suggest to go with r02 and object other version ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306050 | CR | Approval | 23.502 CR3946R1 (Rel-18, 'B'): KI#4: Support for Centralized NSACF in multi-service PLMN in non-roaming cases. | Ericsson | Rel-18 | Revision of S2-2304006r02. Approved | Agreed | |
| 9.11.2 | S2-2304959 | CR | Approval | 23.502 CR3918R1 (Rel-18, 'B'): Event exposure enhancement for enhanced NSACF architecture | Huawei, HiSilicon | Rel-18 | Revision of S2-2302781 from S2#155. Postponed | George Foti (Ericsson) provides comments Fenqin (Huawei) provides feedback Ashok (Samsung) agrees with Fenqin (Huawei) Fenqin (Huawei) provides feedback to Ashok George (Ericsson) provides response. NOT OK. Fenqin(Huawei) Provides feedback to George Fenqin(Huawei) Provides r01 George (Ericsson) asks a question since I am not onboard yet. Fenqin (Huawei) provides r02 Ashok (Samsung) is not OK with r02 George (Ericsson) provides comments. We have to agree on some principles I listed below before any update can be accepted. Fenqin (Huawei) provides feedback to Ashok and George and r03 Fenqin (Huawei) provides r04 ==== Revisions Deadline ==== George (Ericsson) provides comments. This one needs more work George Foti (Ericsson) proposes to postpone this CR Fenqin (Huawei) give a feedback to George. Ashok (Samsung) proposes to go with r04 George (Ericsson) provides responses inline Ashok (Samsung) responds to George (Ericsson) George (Ericsson) provides response inline Ashok (Samsung) explains to George (Ericsson) that in the Hierarchical architecture as only one Primary NSACF is present, it is the best NF suited to do aggregation and provides the notifications through NEF for untrusted AF case and directly for trusted AF case. If we use existing NEF aggregation it will be duplicate as Primary NSACF is anyway subscribing with NSACFs for other purposes ( not only when receive subscription from AF) which is already present in the specification. Fenqin (Huawei) provides way forward R04+ one editor's note 'the relation between the NEF collection and Primary NSACF collection is expected to be clarified' George (Ericsson) responds. Are U telling me that the existing exposure plus adding the primary reporting its own results does not workU assume that the Primary has to do the aggregation for other reasons. The same quota calculation can be achieved by other means. it is not necessary; It is one way. Has it been documented in such a fashion it would have been OK Jinguo(ZTE) agree with Ashok. Postpone to next meeting means there will be higher risk to complete both 501 and 502 CR in May meeting. George (Ericsson) provides response. I prefer to postpone and we do this offline. The exact wording and optionality/scope/purpose of this procedure and its relation to what exists is completely muddled now. This note does not help Ashok (Samsung) comments that NEF aggregation solution works but Primary NSACf aggregation is simple and energy efficient. That is what SA principle guides us to follow. Just to make progress both options have been kept . Still whatever modifications we can do in next meeting. If we postpone then again it will start from scratch and seems difficult to complete. George (Ericsson) lets work offline next week and we will have something co-signed. It is a documentation issue; but an important one Fenqin (Huawei) prefer to go with r04+ EN as listed below. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2305082 | CR | Approval | 23.502 CR3930R1 (Rel-18, 'B'): Hierarchical NSACF architecture procedures | Samsung, NEC, Xiaomi | Rel-18 | Revision of S2-2302925 from S2#155. r07 agreed. Revised to S2-2306051. | George Foti (Ericsson) provides r01. Please see additional comments Fenqin (Huawei) provides r02 and additional comments as follows. George (Ericsson) provides comments. We are Not Ok with r02 George (Ericsson) provides comments on r01 and provides r03 on top of r01 Ashok (Samsung) provides further comments Fenqin (Huawei) provides r04 George Foti (Ericsson) provides r05 Ashok (Samsung) thanks George Foti (Ericsson) for providing r05 and OK with it Fenqin (Huawei) provides r06 George (Ericsson) r06 NOT OK. Please see comments Ashok (Samsung) comments George (Ericsson) is OK with r06 after further reading Ashok (Samsung) comments on r06 Ashok (Samsung) provides r07 Fenqin (Huawei) is ok with r07 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306051 | CR | Approval | 23.502 CR3930R2 (Rel-18, 'B'): Hierarchical NSACF architecture procedures | Samsung, NEC, Xiaomi,Huawei | Rel-18 | Revision of S2-2305082r07. Approved | Agreed | |
| 9.11.2 | S2-2304960 | CR | Approval | 23.502 CR3769R2 (Rel-18, 'B'): Enhancement of NSAC for roaming case | Huawei, HiSilicon | Rel-18 | Revision of S2-2302783 from S2#155. Postponed | George Foti (Ericsson) provides r01. This CR has several thing missing such as how the VPLMN acquires the admission mode, the fetching of the quota for different admission modes, among other things. Fenqin (Huawei) provides r02. George (Ericsson) provides comments on r02. Fenqin (Huawei) provides comments on r03. George Foti (Ericsson) provides r04. Please see comments Fenqin (Huawei) provides r05. George (Ericsson) Not OK. provides comments Fenqin (Huawei) provides r06 ==== Revisions Deadline ==== George (Ericsson) proposes to postpone this CR. Additional comments. George Foti (Ericsson) proposes to postpone the CR Fenqin (Huawei) proposes a response to George. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | - | - | - | KI#5 | - | - | Docs:=13 | - | |
| 9.11.2 | S2-2304199 | DISCUSSION | Agreement | Usage of RFSP and Target NSSAI with Partially Allowed NSSAI | Ericsson | Rel-18 | Noted | Alessio(Nokia) requests to note this paper. We believe sending partially allowed and partially rejected S-NSSAIs to RAN is helpful for the RAN RRM. The RFSP can take into account both Peter Hedman (Ericsson) ok to note the DP, but there is no reason to require an update of the NGAP as suggested by Nokia ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2305326 | DISCUSSION | Agreement | Creating an RA when a Slice is Partially Supported in the RA | InterDigital Inc. | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2303959 | LS In | Action | LS from RAN WG3: Reply LS on Partially allowed/rejected NSSAI | RAN WG3 (R3-230923) | Rel-18 | Responses drafted in S2-2304201, S2-2304748. Final response in S2-2306254 | Replied to | |
| 9.11.2 | S2-2304201 | LS OUT | Approval | [DRAFT] Reply LS on Partially allowed/rejected NSSAI | Ericsson | Rel-18 | Response to S2-2303959. Merged into S2-2306254 Merge into (revision of) S2-2304748 | Stefano (Qualcomm) has common comment for 4201, 4748, 4200, and 4753. Proposes to use 4201 as basis. Alessio Nokia) proposes to note this and use 4748 instead. Peter Hedman (Ericsson) provides comments Alessio(Nokia) cannot agree to overload the Target NSSAI with the handling of partially allowed network slices. Hence this LS is not acceptable. Alessio(Nokia) comments Peter Hedman (Ericsson) provides r01 Alessio(Nokia) believes the only way we conclude is if Ericsson provides feedback on the DP we provided that clearly shows AOI approach is not workable as it is too frequently invoked and becomes a fundamental network feature that will be involved in many handovers intra and inter gNB. It is clear the awareness in rAN will avpoid large inefficiency. Also sending the partially allowed NSSAI and rejected S-NSSAI to rAN will not require updating the target NSSAI feature for the sole purpose to make the feature of non uniform support in rA work. These are SA2 level discussions really but we are forced always in the RAN3 / SA2 ping ponging when clearly a solution is superior and following SA guidelines on energy efficiency. hat regularly delays our features. Alessio (nokia) indicates r01 is not ok. ==== Revisions Deadline ==== Alessio(Nokia) would suggest to use the text in 4748r01 submitted for review after submission deadline based on the discussion so far and the text in specification. Als for question D it takes text from this LS r01 Peter Hedman (Ericsson) ok with r00 or r01 Alessio (nokia) Not ok with r00 or r01 Jinguo(ZTE) suggest to merge into 4748 ==== Comments Deadline ==== | Merged |
| 9.11.2 | S2-2304748 | LS OUT | Approval | [DRAFT] Reply LS on partially allowed/rejected S-NSSAI | Nokia, Nokia Shanghai Bell | Rel-18 | Response to S2-2303959. CC#4: r08 + changes agreed. Revised to S2-2306254, merging S2-2304201. Approve r04 or r05 in DRAFTS/eNS_Ph3 folder? For CC#4 | Stefano (Qualcomm) has common comment for 4201, 4748, 4200, and 4753. Proposes to use 4201 as basis, detailed comments provided for 4201 and apply also to 4748. Alessio(Nokia) proposes for load sharing to hold the pen for this one. Peter Hedman (Ericsson) provides comments that we prefer LS reply in 4201 ==== Revisions Deadline ==== Alessio(nokia) proposes to use the update in r01 in DRAFTS at link provided below, that relies only on text in our specification (including a single RFSP applies across Allowed + partially allowed in one is provided). Ashok (Samsung) comments on the LS OUT Peter Hedman (Ericsson) object to r00 and r01 (see reasoning below) provides reply to Ashok Peter Hedman (Ericsson) an acceptable version is provided in draft folder Alessio(Nokia) provides a r03 on top of r02 in draft folder Peter Hedman (Ericsson) provides comments that we then also should state that there is no agreement that NG-RAN needs to be impacted Alessio(nokia) replies to Peter Hedman (Ericsson) that we do not think they asked us about that. Let's keep the principle we reply to what they asked here too like in the other LS OUT. Peter Hedman (Ericsson) provides comments that we should try to progress and not add only side of the disagreements i.e. we object to the r02 + changes Peter Hedman (Ericsson) provides another proposal for compromise in draft folder r04 Alessio(Nokia) provides r05 that keeps the generic question to RAN3 to provide more feedback Ericsson had removed and puts in action confirmation of support of new IEs over the NG-AP. Removed the discussion on minimization of impacts that is not what SA2 can assess ==== Comments Deadline ==== Haiyang (Huawei) suggests to remove the 'requirement' to RAN3 Alessio (nokia) highlights the changes in r05 from r04 (from Peter): moved the request for input on Partially allowed NSSAI from a NOTE at beginning in Actions to rAN3 and added also same action for S-NSSAI rejected partially in RA. Also fixed the text on target NSSAI as in r04 it was as if there was no consensus in whether the Target NSSAI can include S-NSSAIs Rejected in RA which is the current behaviour (and removed the impact considerations as this is subjective as we will need to change the target NSSAI behaviour as we will need to forward between gNBs etc. exactly like partially allowed NSSAI stores in RAN: i.e: From There is no consensus on whether the target NSSAI can include S-NSSAIs rejected in the RA or S-NSSAIs of Partially Allowed NSSAI e.g. as to minimize or avoid NG-RAN impacts There is no consensus on whether the target NSSAI can not include S-NSSAIs rejected in the RA and include only e.g. S-NSSAIs of Partially Allowed NSSAI and Allowed NSSAI. We suggest to move forward with r05 as is. Peter Hedman (Ericsson) provides comments and suggests changes on top of r05 as there are more than one r04 Alessio(Nokia) provides r06 with text as clear and spec based. If anyone has any comments on this please make them on this cleaner revision (the others are cluttered now) Peter Hedman (Ericsson) Nokia keep insisting on the solution to impact NGAP with all IEs rather than add all options on the table for RAN3 to evaluate, r06 is not acceptable. r07 proposed. Alessio(Nokia) provides r08 removing all controversial aspects Peter Hedman (Ericsson) ok with r08 if the meeting minutes also states: 'SA2 has not yet confirmed the NGAP impacts for supporting Partially Allowed NSSAI and S-NSSAIs rejected for part of the RA feature i.e. even if Partially Allowed NSSAI is stated to be sent over N2 there is an Editor's note with FFS for getting RAN3 feedback on the NGAP impacts including whether NGAP is to be impacted.' Haiyang (Huawei) provides r09 to add Peter's proposal in the LS itself. | Revised |
| 9.11.2 | S2-2306254 | LS OUT | Approval | Reply LS on partially allowed/rejected S-NSSAI | SA WG2 | Rel-18 | Revision of S2-2304748r08 + changes, merging S2-2304201. CC#4: Approved | Approved | |
| 9.11.2 | S2-2304753 | CR | Approval | 23.501 CR4399 (Rel-18, 'C'): Clarifications of the Partial support of a network slice in a RA | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Stefano (Qualcomm) has common comment for 4201, 4748, 4200, and 4753. Jinguo(ZTE) sugguest that this paper focus on the NSSAA part and remove other changes. Peter Hedman (Ericsson) provides comments and r01 Alessio(Nokia) provides r02 but will not agree to settle the other aspects at this meeting in a way different than what we propose as it means we go for very inefficient approach as in our DP has been highlighted. We provided revision to allow an efficient approach in 4200r03 and soon update it with remove NSSAA aspects Peter Hedman (Ericsson) provides comments that r02 bundles NSSAA (EAP) with MM in a way that is not acceptable ==== Revisions Deadline ==== Myungjune (LGE) comments and provides suggestion Peter Hedman (Ericsson) ok with r01, but objects to r02. The principles of leaving this to AMF would be fine but not restrict the AMFs logic wrt to simply execute NSSAA/EAP Alessio(Nokia) comments on technical remark and of course objects to r01 Peter Hedman (Ericsson) provides proposal Ashok (Samsung) provides comments on the proposal Alessio(nokia) proposes to agree r02 after we remove this bullet - If the S-NSSAI is subject to NSSAA, then the AMF should send this S-NSSAI as rejected partially in the RA in the Registration Accept message, unless the AMF stores authentication and authorization status for the UE for the related specific S-NSSAI of the HPLMN for this S-NSSAI indicating this was successfully Authorized (in which case it can be sent in the Partially Allowed NSSAI), unless it intends to execute NSSAA in which case it would initiate NSSAA and include the s-NSSAI in the Pending NSSAI. And we come back in the future for this aspect. (too late in meeting to discuss more). Ulises (InterDigital) provides comments - We are OK with either r01 or r02 if the bullet is not removed. This is closer to current behaviour. Alessio(nokia) disagree with the proposal by Ericsson as it forces NSSAA to be executed irrespective of support in TA for the slice (i.e. the NSSAA is executed u nless the UE was already authorize in which case it says it is partially rejected... Peter Hedman (Ericsson) repeats the proposal and ask Nokia why 'it forces NSSAA to be executed irrespective of support in TA for the slice' as in english either or should mean that the AMF got an option or? Jinguo(ZTE) suggests to approve r02 with undo the change in clause 5.15.17, and update the coversheet. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2304200 | CR | Approval | 23.501 CR4237 (Rel-18, 'C'): Resolving open issues for partial Network Slice support in a Registration Area | Ericsson | Rel-18 | Postponed | Stefano (Qualcomm) has common comment for 4201, 4748, 4200, and 4753. Jinguo(ZTE) suggests that this paper focus on the RFSP part and remove other changes. Ashok (Samsung) comments Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) provides comments and r01 Haiyang (Huawei) provides questions Ashok (Samsung) provides comments Alessio (Nokia) provides r03, r02 was uploaded by mistake please disregard Ashok (Samsung) provides comments on r03 Haiyang (Huawei) provides r04 Jinguo(ZTE) provides r05 Peter Hedman (Ericsson) provides r06 Alessio(Nokia) provides r07 which is the only update of the Target NSSAI feature we can accept. the target NSSAI has to remain with the original intent to provide support for redirection outside the RA. Inside the RA the awareness of Partially allowed NSSAI and rejected in the RAN is sufficient and necessary (the purpose to achieve a successful registration for the s-NSSAIs is achieved without target NSSAI, which was the intent of the Target NSSAI feature!). ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r06, objects to r07 and r03, r04, r05 i.e. we better POSTPONE the CR until we agreed on the NG-RAN support Alessio (nokia) now can only see the way forward is the one Peter proposes in 'we better POSTPONE the CR until we agreed on the NG-RAN support' ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2305106 | CR | Approval | 23.501 CR4485 (Rel-18, 'B'): Addressing EN and updates on UP activation policy | Samsung, Xiaomi | Rel-18 | Merged into S2-2306052 | Jinguo(ZTE) suggest this paper to merge into 5329. Ashok (Samsung) comments that it can be marked as merged into 5329. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.11.2 | S2-2305329 | CR | Approval | 23.501 CR4553 (Rel-18, 'C'): Creating an RA when a Slice is Partially Supported in the RA | InterDigital Inc. | Rel-18 | r06 agreed. Revised to S2-2306052, merging S2-2305106 | Jinguo(ZTE) suggests to use this paper as basis to update clause 5.15.17, and merge the similar changes from 5106,4753 and 4200 Ashok (Samsung) request for clarification Genadi (Lenovo) has comments similar to Ashok (Samsung). Peter Hedman (Ericsson) provides comments and r01 Ashok (Samsung) provides r02 Ulises (InterDigital) provides replies to comments and r03 Peter Hedman (Ericsson) provides r0x Ashok ( Samsung) provides comments on r0x Yannick (Convenor): To record that r04 was provided by Peter Hedman (Ericsson). Ashok ( Samsung) provides r05 and the only change is removal of back-off timer Genadi (Lenovo) provides r06 to include a reference to another slicing feature. ==== Revisions Deadline ==== Myungjune (LGE) is ok with r05, r06. Alessio can live with r06 if this is removed - the S-NSSAI is included in neither the Partially Allowed NSSAI nor the Allowed NSSAI, the AMF may reject the S-NSSAI partially in the RA, or it may reject the S-NSSAI for the RA. If an S-NSSAI is rejected partially in the RA the UE is not allowed to attempt to register to the S-NSSAI rejected partially in the RA until the UE enters a TA supporting the S-NSSAI. Editor's Note: It is FFS what other mechanisms can be used to enable the UE to register to S-NSSAI that has been partially rejected in a TA where the S-NSSAI is supported, e.g., in order to account for situations where the UE does not move out of the TA for a long period of time. Peter Hedman (Ericsson) ok with r06 + removal of text as suggested by Alessio Ulises (InterDigital Inc.) replies to Alessio (Nokia), the 'strange' case you are mentioning is precisely what we are trying to address, the list of supported TA is independent from whether the AMF decides to reject the slice or not. Ulises (InterDigital Inc.) provides comments - we don't agree on removing the text. We identified and issue that is addressed with that text, and respectfully request that be left as is. We are OK with r06 as is, without removing the text. Jinguo(ZTE) ok with r06 + removal of text as suggested by Alessio. Ulises (InterDigital Inc.) provides comments - we don't want to stop progress, but we would like to add an editor's note that describes the problem. Ulises (InterDigital Inc.) provides comments - we are OK with r06 adding the editor's note that I provided: 'Editor's Note: It is FFS how to address when the S-NSSAI is included in neither the Partially Allowed NSSAI nor the Allowed NSSAI, and the AMF may reject the S-NSSAI partially in the RA, or it may reject the S-NSSAI for the RA, and what mechanisms can be used to enable the UE to register to S-NSSAI that has been partially rejected in a TA where the S-NSSAI is supported, e.g., in order to account for situations where the UE does not move out of the TA for a long period of time.'. Ashok (Samsung) comments on the proposal ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306052 | CR | Approval | 23.501 CR4553R1 (Rel-18, 'C'): Creating an RA when a Slice is Partially Supported in the RA | InterDigital Inc., Ericsson, Samsung | Rel-18 | Revision of S2-2305329r06, merging S2-2305106. Approved | Agreed | |
| 9.11.2 | S2-2304202 | CR | Approval | 23.502 CR3849R2 (Rel-18, 'B'): Support of partly rejected/allowed S-NSSAIs | Ericsson | Rel-18 | Revision of S2-2302975 from S2#155. r06 agreed. Revised to S2-2306053. | Alessio provides r01 Krisztian (Apple) provides r02. Jinguo(ZTE) provides r03 Peter Hedman (Ericsson) provides r04 Ashok (Samsung) provides r05 Alessio(nokia) provides r06 based on r04 to really keep the pro missed N2 impact as we have that already in 23.501. Peter Hedman (Ericsson) provides reply to Alessio that we do not yet have rejected partially in N2 in 23.501 i.e. r06 is not aligned with 23.501, right? ==== Revisions Deadline ==== Myungjune (LGE) supports r04 and wants to cosign. Alessio(Nokia) provides in drafts the text r06 where it is FFS if partially rejected S-NSSAI goes in N2 info. Peter Hedman (Ericsson) ok with r06+ add 'It is FFS if the N2 information also includes S-NSSAI rejected partially in RA' to 'Editor's Note: the Partially Allowed NSSAI support over N2 is to be confirmed. It is FFS if the N2 information also includes S-NSSAI rejected partially in RA.' + Remove 'and in the N2 message carrying the Registration Accept message.without this TAI List' above editor's note. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2306053 | CR | Approval | 23.502 CR3849R3 (Rel-18, 'B'): Support of partly rejected/allowed S-NSSAIs | Ericsson, Nokia, Nokia Shanghai Bell, Apple, LG Electronics | Rel-18 | Revision of S2-2304202r06. Approved | Agreed | |
| 9.11.2 | - | - | - | KI#6 | - | - | Docs:=6 | - | |
| 9.11.2 | S2-2304005 | CR | Approval | 23.501 CR4188 (Rel-18, 'B'): KI#6: Support for network control of the UE behaviour for a network slice while roaming | Ericsson | Rel-18 | Noted | Stefano (Qualcomm) has question for clarification and concerns. George (Ericsson) provides comments Fenqin (Huawei) share the same view as Stefano Ashok (Samsung) objects to the CR and shares the same concern as others George (Ericsson) provides response. Alessio(Nokia) objects to this CR and clarifies the Nokia CR does have a HPLMN controlled approach. Jinguo(ZTE) also believes that the NSAC is orthogonal with this feature. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304600 | CR | Approval | 23.501 CR4356 (Rel-18, 'B'): Support of roaming for Network Slice usage control | LG Electronics | Rel-18 | Merged into S2-2304961 (noted) | George Foti (Ericsson) objects to this CR Stefano (Qualcomm) has concerns, same comment as 4005 applies. Myungjune (LGE) replies to Stefano (Qualcomm) Ashok (Samsung) supports the CR Fenqin (Huawei) suggest to merge this paper to 4961. George (Ericsson) provides comments Myungjune is ok to merge this CR into S2-2304961 Alessio(Nokia) also has concerns, same comment as 4005 applies. The assumption only slices subject to NSAC can be subject of usage policy is not agreeable ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304750 | CR | Approval | 23.501 CR4398 (Rel-18, 'C'): Clarification on Configuration of UE with network Slice Usage Policy in Roaming | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2306240 | George Foti (Ericsson) objects to this CR Ashok (Samsung) support the CR. Same comment as 4600 to choose one paper as basis from 3 papers (4600, 4750, 4961) which propose the same thing Alessio(Nokia ) is happy to consider a merged paper. which CR is used as basis is not important. We are ok with any as long as the principles are agreed: 1. UDM provides info 2. UDM determines whether VPLMN AMF/SMF can change the info 3. If UDM provides no info then AMF/SMF can apply its own serving PLMN policy 4. In roaming the HPLMN may provide on demand slice indication only (in which case timer is set by VPLMN or left to AMF implementation as today), timer indication only (in which case slice is on demand) or both. Fenqin(Huawei) suggest to work on 4961 George (Ericsson) provides comments Jinguo(ZTE) suggest to merge this paper into 4961 and use one paper for UDM opotion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.11.2 | S2-2304961 | CR | Approval | 23.501 CR4443 (Rel-18, 'B'): Network control of the slice usage | Huawei, HiSilicon. | Rel-18 | Noted | George Foti (Ericsson) objects to this CR. See comments on 4750 Ashok (Samsung) support the CR. Same comment as 4600 to choose one paper as basis from 3 papers (4600, 4750, 4961) which propose the same thing Fenqin (Huawei) provides r01 George (Ericsson) objects to all revisions. This changes the HPLMN behavior as well putting the entire KI#6 at risk of being dropped out Fenqin (Huawei) ask for clarification Alessio(Nokia) is ok with r01 and comment on George's comments Ashok (Samsung) provides comments on r01 Alessio(nokia) replies to Ashok (Samsung) ==== Revisions Deadline ==== George Foti (Ericsson) is not OK with any revision including the original. Fenqin (Huawei) ask some clarification from George alessio(NoKia) is agreeing with Fenqin: we cannot understand the reason whey tis is not ok. George (Ericsson) provides responses. Fenqin (Huawei) provides responses to George. George (Ericsson) subscription is not control NSSRG is unrelated and the HPLMN has control in this case if the VPLMN does not support the feature. It know what is allowed or not. So lets not bring in NSSRG. We ended up with 3 admission modes for VPLMN in NSAC because we came up with something initially that operators did not want and with no requirements. We cant do that again. ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2305094 | CR | Approval | 23.501 CR4480 (Rel-18, 'B'): PDU session inactivity timer for MAPDU session | Samsung, Xiaomi | Rel-18 | Noted | George Foti (Ericsson) Objects to the CR. Myungjune (LGE) provides comments. Ashok (Samsung) explains to George (Ericsson) and Myungjune (LGE) Myungjune (LGE) replies to Ashok (Samsung) Fenqin (Huawei) provides comments Jinguo(ZTE) comments Ashok (Samsung) provides clarification George (Ericsson) provides response. There is much more to lose that gain by doing what U are proposing Ashok. I am NOT ok doing anything on this one. George (Ericsson) provides response. I would be OK with such a note Ashok (Samsung) responds Jinguo(ZTE) ask clarifications Myungjune replies to Ashok (Samsung) Ashok (Samsung) replies to Myungjune and Jinguo Fenqin (Huawei) responds to Ashok Ashok (Samsung) replies to Fenqin and provides r01 ==== Revisions Deadline ==== Jinguo(ZTE) is not convinced that per access inactive timer for MA PDU session is feasible. George Foti (Ericsson) objects to the original and all revisions. Myungjune (LGE) proposes to NOTE this CR. ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2304601 | CR | Approval | 23.502 CR4036 (Rel-18, 'B'): Improved network control of a network slice | LG Electronics, Huawei, NEC, Apple | Rel-18 | Postponed | George Foti (Ericsson) objects to the CR and provides comments Myungjune (LGE) replies to George Foti (Ericsson) and provides r01. Fenqin (Huawei) provides r02. Ashok (Samsung) provides r03. Ashok (Samsung) provides r03 with the link. George (Ericsson) provides comments Fenqin (Huawei) comments and provides r04 Myungjune (LGE) provides r05 Fenqin (Huawei) provides r06 Alessio(Nokia) asks to postpone this CR as we should stabilize 501 at this meeting ... I do not like to have two unstable CRs at the same time. George (Ericsson) We prefer r05. The operator policy is aligned with 23.501. The EN is ot needed. We already have that on 23.510. r05 is a perfect fit for what is in 23.501. This is all we can do in this meeting. ==== Revisions Deadline ==== George Foti (Ericsson) accepts only r05. Myungjune (LGE) proposes to agree r05. Fenqin (Huawei) proposes a response to Myungjune. Myungjune (LGE) replies to Fenqin (Huawei) Fenqin (Huawei) replies to Myungjune (LGE) George (Ericsson) I am OK r05++ removing operator policy. But as was mentioned we already have an EN in 23.501 Myungjune (LGE) proposes to agree r06 + change EN in 4.2.X to ' Roaming support can be revisited according to TS 23.501 progress.' Alessio(Nokia) believes this CR has no sufficient quality to be approved. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=26 | - | |
| 9.11.2 | S2-2304007 | CR | Approval | 23.502 CR3947 (Rel-18, 'B'): KI#4: Support for HPLMN admission mode while Roaming | Ericsson | Rel-18 | George Foti (Ericsson) provides r01 | NOT HANDLED | |
| 9.11.2 | S2-2304522 | CR | Approval | 23.502 CR4025 (Rel-18, 'B'): Support of network slice replacement for handover | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304524 | CR | Approval | 23.501 CR4336 (Rel-18, 'F'): Terminology alignment and further clarifications for partial network slice support in a RA | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304525 | CR | Approval | 23.502 CR4026 (Rel-18, 'B'): Procedure enhancement for partial network slice support in a RA | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304569 | CR | Approval | 23.501 CR4348 (Rel-18, 'F'): Correction to the mapping of the Alternative S-NSSAI | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304570 | CR | Approval | 23.501 CR4349 (Rel-18, 'F'): Clarifications to the NSAC architectures | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304571 | CR | Approval | 23.501 CR4350 (Rel-18, 'F'): Clarification on the list of TAs associated with S-NSSAI partially rejected in the RA | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304572 | CR | Approval | 23.502 CR4030 (Rel-18, 'B'): Introduction of Network Slice replacement in the NAS MM procedures | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304595 | CR | Approval | 23.501 CR4353 (Rel-18, 'B'): Resolving EN on using NG-RAN resource of replaced S-NSSAI | LG Electronics | Rel-18 | Dongeun (Samsung) comments | NOT HANDLED | |
| 9.11.2 | S2-2304597 | CR | Approval | 23.502 CR4035 (Rel-18, 'B'): Support of NSSF notification for Network Slice Replacement and Network Slice instance Replacement | LG Electronics | Rel-18 | Dongeun (Samsung) comments | NOT HANDLED | |
| 9.11.2 | S2-2304599 | CR | Approval | 23.501 CR4355 (Rel-18, 'F'): Clarification on applicability of slices with area of service not matching deployed TA boundary over non-3GPP access | LG Electronics | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304742 | CR | Approval | 23.502 CR4064 (Rel-18, 'B'): Update of the reasons to invoke the CN-initiated selective deactivation of UP connection of an existing PDU Session. | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304774 | CR | Approval | 23.502 CR4068 (Rel-18, 'B'): Support of the NS-AoS smaller than deployed TAs | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304914 | CR | Approval | 23.502 CR4088 (Rel-18, 'B'): 23502 Network slice replacement update for NSSF | vivo | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304958 | CR | Approval | 23.502 CR3768R2 (Rel-18, 'B'): Hierarchical NSAC Architecture Enhancement | Huawei, HiSilicon | Rel-18 | Revision of S2-2302779 from S2#155 | NOT HANDLED | |
| 9.11.2 | S2-2305009 | CR | Approval | 23.502 CR3749R2 (Rel-18, 'B'): Providing Alternative S-NSSAI to the UE via Registration and UCU | LG Electronics, ZTE | Rel-18 | Revision of S2-2302546 from S2#155 | NOT HANDLED | |
| 9.11.2 | S2-2305047 | CR | Approval | 23.502 CR3858R2 (Rel-18, 'B'): KI#1 New PDU Session transfer to an Alternative S-NSSAI | NEC | Rel-18 | Revision of S2-2302453 from S2#155 | NOT HANDLED | |
| 9.11.2 | S2-2305112 | CR | Approval | 23.501 CR4488 (Rel-18, 'B'): Storage of S-NSSAI validity time information | Samsung | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2305113 | CR | Approval | 23.501 CR4489 (Rel-18, 'B'): Registration status after S-NSSAI removal based on S-NSSAI validity time information | Samsung | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2305134 | CR | Approval | 23.501 CR4495 (Rel-18, 'F'): Clarification on Network Slice Area of Service | ZTE | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2305135 | CR | Approval | 23.501 CR4496 (Rel-18, 'F'): Clarification on network slice replacement | ZTE | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2305136 | CR | Approval | 23.501 CR4497 (Rel-18, 'F'): Clarification on Network Slice usage control | ZTE | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.11.2 | S2-2305137 | CR | Approval | 23.501 CR4498 (Rel-18, 'F'): Clarification on temporarily available network slices | ZTE | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2305191 | CR | Approval | 23.502 CR4122 (Rel-18, 'F'): Determination of partially allowed NSSAI by NSSF:KI#5 | NEC Corporation | Rel-18 | CR Cover sheet error!. Confirm Specification Number - CR states 23.501! | NOT HANDLED | |
| 9.11.2 | S2-2305142 | CR | Approval | 23.502 CR4112 (Rel-18, 'B'): Support of network slice replacement for roaming case | ZTE, LG Electronics, NEC | Rel-18 | NOT HANDLED | ||
| 9.11.2 | S2-2304560 | CR | Approval | 23.501 CR4344 (Rel-18, 'B'): Update of the NSSF service description for Network Slice replacement | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.12.1 | - | - | - | Study on XR (Extended Reality) and media services (FS_XRM) | - | - | Docs:=0 | - | |
| 9.12.2 | - | - | - | XR (Extended Reality) and media services (XRM) | - | - | Docs:=168 | - | |
| 9.12.2 | - | - | - | General | - | - | Docs:=14 | - | |
| 9.12.2 | S2-2304164 | LS OUT | Approval | [DRAFT] LS on introduction of support for L4S in 5GS | Ericsson | Rel-18 | r03 agreed. Revised to S2-2306183. CC#4: Noted | Dan (China Mobile) comments and think this LS is not needed, RAN3 will do the work by themselves Chris Joul (TMUS) Thinks an LS will be helpful. Dieter (Deutsche Telekom) also thinks that the LS would be helpful. Paul R (Charter) agrees that the LS would be helpful. Xiaowan Ke share Dan (China Mobile)'view to note the LS since no issue need to negotiation Shabnam (Ericsson) it is quite common for SA2 to inform RAN of the work impacts, as is done for other WIs such as ProSe, MBS etc. even in the presence of RAN WIs. I believe there have been other ones as well in various topics. Would request CMCC and Vivo reconsider. See comments Dan (China Mobile) generally OK to trigger the RAN do the alignment work early, with sending the LS to RAN Hugh (AT&T) also thinks that the LS is helpful for cross group alignment of new work item. Sudeep (Apple) supports sending this LS to RAN3. Mukesh (MediaTek) agrees sending this LS is useful. Chris (Vodafone) supports sending this LS to RAN3. Chunshan(CATT) thinks it is premature to send LS and proposes to note this LS. Rahil (CableLabs) supports sending this LS to RAN3. Paul (Ericsson) replies that it is not correct to hold back an LS because there is no response LS yet available related to a different functionality. It is the last Q for Rel-18 so we should work constructively to complete the work. Hui (Huawei) fine with sending the LS to RAN3. ==== Revisions Deadline ==== Xiaowan (vivo) disagrees the original version and provide r01. If we are urgent to send a LS this meeting, the LS should not only cover L4S but congestion information exposure, but also congestion information monitoring + exposure together. Since the QoS monitoring support both ECN marking for L4S and congestion information exposure. The two percentage need to be designed together. Hui (Huawei) support Xiaowan's proposal. Paul (Ericsson) provides r02. To avoid ambiguities, r02 clarifies the information that NG-RAN exposes. We ask to discuss this LS in CC#3 or CC#4. Hui (Huawei) objects to r02 due to the naming issue. Xiaowan (vivo) provides r03 and clarifies that the LS is related to three ongoing CRs in KI#3. ==== Comments Deadline ==== Paul (Ericsson) provides r04 and asks to take it at CC#4. Paul (Ericsson) objects to r01 and r03. Both were provided after the deadline. | Noted |
| 9.12.2 | S2-2306183 | LS OUT | Approval | [DRAFT] LS on introduction of support for L4S in 5GS | Ericsson | Rel-18 | Revision of S2-2304164r03. Approved. CC#4: WITHDRAWN | Withdrawn | |
| 9.12.2 | S2-2303922 | LS In | Action | LS from GSMA ENSWI: LS reply on a new SST value for Extended Reality and Media Services | GSMA ENSWI (ENSWI21_Doc007) | Revision of postponed S2-2302207 from S2#155. Postponed | Dan (China Mobile) suggest to postponed this LS, we can have some decision maybe in this meeting for SST. | Postponed | |
| 9.12.2 | S2-2303946 | LS In | Action | LS from RAN WG2: Reply LS on PDU Set Handling | RAN WG2 (R2-2302010) | Rel-18 | Noted | Hui (Huawei) proposes to note this LS in. Dan (China Mobile) agree to note this LS in. | Noted |
| 9.12.2 | S2-2303974 | LS In | Action | LS on the Design of RTP Header Extension for PDU set handling | SA WG4 (S4-230419) | Rel-18 | Responses drafted in S2-2304632, S2-2304717, S2-2304839, S2-2305026, S2-2305325. CC#4: Postponed | Dan(China Mobile)suggests to take the technical discussion in this email thread and decide using which LS as the baseline one Xiaowan Ke(vivo) provides analysis on the 5 LS replies and vivo's view. Hui(Huawei) replies. Saso (Intel) suggests to take 4839 as the basis for the reply. | Postponed |
| 9.12.2 | S2-2304632 | LS OUT | Approval | [DRAFT] LS on the Design of RTP Header Extension for PDU set handling | CATT | Rel-18 | Response to S2-2303974. Merge into S2-2304717 (Postponed). Postponed Merge into (revision of) S2-2304717 | Devaki (Nokia) comments that this DRAFT LS out can be merged with 4717 and its revisions. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2304717 | LS OUT | Approval | [DRAFT] LS reply on design of RTP header | Huawei | Response to S2-2303974. CC#4: Postponed r12? For CC#4 | Devaki (Nokia) comments that this DRAFT LS out can be used as the baseline, propose to consider other DRAFT LS out in 4632, 4839, 5026, 5325 as merged. Devaki (Nokia) comments that part of Q2 answer from 5325 will be useful to add as well. Xiaowan Ke(vivo) replies to Hui(Huawei) that I think you misunderstood Q2 of SA4 LS and Rapporteur requests technical discussion in the thread of 3974 firstly. Yali (OPPO) comments on r01. Hui(Huawei) provides r01. Hui (Huawei) responses to Yali (OPPO). Hui(Huawei) replies to Xiaowan(vivo). Yali (OPPO) responses to Hui (Huawei). Chunshan(CATT) provides r02 and clarifications. Dimitris (Lenovo) comments Chunshan(CATT) provides r03 to replace r02 since the 'not' needs to be removed in the r02. Xiaowan Ke(vivo) replies to Hui(Huawei) and comment Yali(OPPO) supports the view from Chunshan(CATT) Dan(China Mobile) provide comment and r04 Chunshan (CATT) provides r05. Mike (InterDigital) comments on r05 Saso (Intel) shares InterDigital's concerns on r05; points that Rapporteur's proposal was to use the 3974 thread for discussion first. Devaki (Nokia) comments. Hui (Huawei) provides r06. Zhuoyun (Tencent) comments. Chunshan(CATT) provides r07. Dan (China Mobile) reply Saso's comment. Saso (Intel) provides r08. Yali (OPPO) comments on r08. Chunshan(CATT) comments on the r08. Saso (Intel) replies to Chunshan. Chunshan (CATT) replies to Saso (Intel). Jinhua (Xiaomi) comments Mengzhen (China Telecom) comments. Dario (Qualcomm) comments. Curt (Meta) comments - mainly that it is too restrictive from AF's perspective if a single QoS flow can only carry PDUs related to PDU set. Curt (Meta) comments - agrees with Mike's (InterDigital) postulations below. Mukesh (MediaTek) provides r09. Paul (Ericsson) provides comments. Devaki (Nokia) objects to revisions r08, r09, ok with r07, r05, r00, r01. It seems we need SoH to determine whether QoS Flow comprises of PDU Sets only or it can comprise of both PDU Sets and PDUs. Clearly we have diverging views here. Dario (Qualcomm) provides r10. Hui(Huawei) provides r11. Dan (China Mobile) suggest to SoH for this Q1 in CC#3, and think the Q1 from SA4 is quite strange and unreasonable Yali(OPPO) is fine with r11. Mukesh (MediaTek) provides r12. Zhuoyun (Tencent) provides r13. Saso (Intel) provides r14. Yali(OPPO) comments on r14. Dan(China Mobile) provides r15. Saso (Intel) thinks r15 is incorrect. Devaki (Nokia) provides r16, objects to r14. Paul (Ericsson) provides r17. Saso (Intel) objects r16. Saso (Intel) provides r18 (completely different). Hui (Huawei) provides r19 for SoH. ==== Revisions Deadline ==== Dario (Qualcomm): r19 is not acceptable as is (it includes different options meant for a SoH). Dario (Qualcomm) is OK w/ r10, 11, 12. Objects to r16 (because ambiguous) and r17, r18 and r19 (because of addition to answer to 2nd question). Hui(Huawei): provides draft r20 Zhuoyun (Tencent) is fine with the SOH options listed in draft r20. Lei(Tencent) provides comments and suggest SoH as Hui suggested. Hui(Huawei) provides suggestion Devaki (Nokia) comments regarding SoH options. Saso (Intel) comments that the current wording in r20 is not helpful; suggests to consider r18 instead. Saso (Intel) replies to Devaki. Lei(Tencent) response and suggest to SoH over 3 options in 4174r20. Jari (NTT DOCOMO) comments Hui (Huawei) replies to saso. Hui (Huawei) replies to Jari Saso (Intel) proposes better wording for Option #1. Jinhua (Xiaomi) comments, fine with SoH go as r20 proposed by Hui or the OP1 rewording from Saso. Propose to remove the wording 'with only this PDU' in the LS, Hui (Huawei) provides r21 for discussion on CC#3 or CC#4.. Saso (Intel) replies to Yali Xiaowan Ke(vivo) request to add in the LS reply: 'SA2 kindly request SA4 to add PDU Set header(including PDU Set importance) for lone PDU when PDU Set header is applied to the XR stream'. Yali(OPPO) comments on r21. Curt (Meta) comments that response in R21 is clearer because it is pointing to GTP-U (i.e, N3/N9). S2's response must not give a wrong impression that this requirement can also be applied to N6. Mukesh (MediaTek) is supports r21 and keeping the text as is. John (Futurewei) supports text in r21. Dan (China Mobile) comment and support Jari Xiaowan Ke(vivo) replies to Hui(Huawei), another alternative is: no PS importance for such lone PDU. We Object Operator to set PS importance for lone PDB blindly. Dario (Qualcomm) comments and provides a simple answer in r22. Proposes to go with r22. Zhuoyun (Tencent) comments: if the EN in 5216 about the PSI is to be added, we need to ask SA4 in LS on their guidance on setting the PSI for this specific PDU Set. ==== Comments Deadline ==== Hui (Huawei) suggest to go with r22. Saso (Intel) provides r23. Saso (Intel) provides r24 based on Yali's text proposal. Hui (Huawei) provides r25. Saso (Intel) is OK with r25. Xiaowan think the related CR can be endorsed at most and remove CR related text and provide r26, in order avoid the CR impact the LS send out Saso (Intel) cannot accept r26. Dan(China Mobile) remove RAN 3 and RAN 2 in this LS, based on r26, I provide r27. Xiaowan(vivo) replies to Saso (Intel) Saso (Intel) replies to Hui to let's first handle 5216. If it is agreed, then there is no reason for not agreeing 4717r25. | Postponed | |
| 9.12.2 | S2-2306242 | LS OUT | Approval | [DRAFT] LS reply on design of RTP header | Huawei | - | Revision of S2-2304717 (not used). WITHDRAWN | Withdrawn | |
| 9.12.2 | S2-2304839 | LS OUT | Approval | [DRAFT] Reply LS on the Design of RTP Header Extension for PDU set handling | Lenovo | Rel-18 | Response to S2-2303974. Merge into S2-2304717 (Postponed). Postponed Merge into (revision of) S2-2304717 | Devaki (Nokia) comments that this DRAFT LS out can be merged with 4717 and its revisions. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2305026 | LS OUT | Approval | [DRAFT] LS reply on the Design of RTP Header Extension for PDU set handling | vivo | Rel-18 | Response to S2-2303974. Merge into S2-2304717 (Postponed). Postponed Merge into (revision of) S2-2304717 | Devaki (Nokia) comments that this DRAFT LS out can be merged with 4717 and its revisions. Xiaowan Ke(vivo) suggests Devaki (Nokia) to technical discussion firstly before rushing to merge papers; and provides analysis on the 5 LS replies Dan(China Mobile)suggests to take the technical discussion in S2-2303974 email thread and decide using which LS as the baseline one Dan(China Mobile)suggests to merge into 4717 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2305325 | LS OUT | Approval | [DRAFT] Reply LS on the Design of RTP Header Extension for PDU set handling | InterDigital Inc. | Rel-18 | Response to S2-2303974. Merge into S2-2304717 (Postponed). Postponed Merge into (revision of) S2-2304717 | Dan(China Mobile) this LS can be merged into 4717 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2305188 | LS OUT | Approval | [DRAFT] LS on PDU Set Discard Usage for XR and Media Services | Xiaomi | Rel-18 | Revision of S2-2303057 from S2#155. Noted | Devaki (Nokia) comments that this DRAFT LS out should be noted and/or postponed as in our first decision on need for RAN to report Discarded PDUs must be taken in SA2/SA5. Mukesh (MediaTek) agrees with Devaki (Nokia) to note this draft LS to RAN2/3. Jinhua (Xiaomi) replies to Mukesh and Devaki, Dan (China Mobile) also agree to note this LS to RAN2/3 Jinhua (Xiaomi) replies to Dan, with DL charging issue clarification when PDU set based QoS handling. John (Futurewei) comments this LS is not needed. Dario (Qualcomm) supports noting this LS. Jinhua (Xiaomi) replies, and provides r01, ==== Revisions Deadline ==== Dario (Qualcomm) objects to any version of this documet. Jinhua (Xiaomi) replies to Dario, ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304648 | CR | Approval | 23.503 CR0984 (Rel-18, 'B'): Policy update to support policy control enhancements for multi-modal services | China Telecom | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2306185. Correction: Noted | Dario (Qualcomm) asks questions for clarification. Xinpeng(Huawei) provides r01. Mengzhen (China Telecom) replies to Dario (Qualcomm). Shabnam (Ericsson) provides comments that some of the attributes need to be provided in proper location, r02 provided. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees with r02 Xinpeng(Huawei) is not ok with r02 and provides r03. Mengzhen (China Telecom) share Xinpeng's view and is ok with r03. Dario (Qualcomm) prefers r02. Mengzhen (China Telecom) replies to Dario (Qualcomm) and is OK with r02. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) r02 is much more clear Shabnam (Ericsson) supports r02, objects to other revisions as r02 is consistent with what the existing statement indicates, 'Following additional attributes are supported where the AF provides specific information for multi-modal applications:...' ==== Revisions Deadline ==== Xinpeng(Huawei) is ok with r01, r03, and objects to all other versions. Mengzhen (China Telecom) suggest to go with r02. Paul (Ericsson) can only accept r02 (E/// revision, accepted by others), object to any other revisions. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) accepts r02, objects any other revision. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2306185 | CR | Approval | 23.503 CR0984R1 (Rel-18, 'B'): Policy update to support policy control enhancements for multi-modal services | China Telecom | Rel-18 | Revision of S2-2304648r02. WITHDRAWN | Withdrawn | |
| 9.12.2 | - | - | - | KI#1,2 | - | - | Docs:=6 | - | |
| 9.12.2 | S2-2305321 | DISCUSSION | Agreement | Using the Traffic Descriptor for UPF Selection | InterDigital Inc. | Rel-18 | Noted | Hui(Huawei) proposes to note this discussion paper which was marked as 'for agreement' Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is of the same opinion, i.e. 'note' and for sure it must not be 'agreed' ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305180 | CR | Approval | 23.501 CR4516 (Rel-18, 'C'): The update of Policy control enhancements to support multi-modal services | Xiaomi | Rel-18 | r01 agreed. Revised to S2-2306184. | Dario (Qualcomm) comments that a NOTE should be used instead of normative text. Dan (China Mobile) comments for NOTE2 Paul (Ericsson) provides r01. Dan(China Mobile) ok with r01. Jinhua (Xiaomi) replies to Dario, Jinhua (Xiaomi) replies to Dan, Jinhua (Xiaomi) replies to Paul, provides r02. Shabnam (Ericsson) provides comments that the note in r02 is not correct and not acceptable, please see our explanation below, so propose to stick with r01. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) r02 is not accepted, r01 is Dario (Qualcomm) is OK with r01. Jinhua (Xiaomi) replies to Dario, Georgios and Shabnam, ==== Revisions Deadline ==== Dan(China Mobile) Agree with r01 Paul (Ericsson) can only accept r01 (E/// revision, accepted by others), object to r02 and any other revision. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) accepts only r01 and objects any other revision. Jinhua (Xiaomi) replies, propose to go with r01, accepted by all. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306184 | CR | Approval | 23.501 CR4516R1 (Rel-18, 'C'): The update of Policy control enhancements to support multi-modal services | Xiaomi | Rel-18 | Revision of S2-2305180r01. Approved | Agreed | |
| 9.12.2 | S2-2304649 | CR | Approval | 23.502 CR4045 (Rel-18, 'B'): Procedures update to support policy control enhancements for multi-modal flows | China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Samsung, China Mobile, Tencent, LG Electronics, ZTE | Rel-18 | CR Cover sheet error! r05 agreed. Revised to S2-2306186. | Xinpeng(Huawei) provides r01. Mengzhen (China Telecom) provide r02. Xinpeng(Huawei) replies to Mengzhen (China Telecom). Dan(China Mobile) provide r03. Mengzhen (China Telecom) replies to Xinpeng (Huawei). Xinpeng(Huawei) comments. Mengzhen (China Telecom) replies to Xinpeng (Huawei) and provide r04. Hyunsook (LGE) asks the clarification. Dan (China Mobile) reply. Shabnam (Ericsson) provides comments and r05 Xinpeng(Huawei) asks for clarification. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is fine with r05 Xinpeng(Huawei) is not ok with r05 and provides r06. Shabnam (Ericsson) does not believe single media has been proposed as text in the CR but rather explanation and it is meant to explain pre-XRM media services that are not multi-modal. Mengzhen (China Telecom) provides r07. Hyunsook (LGE) asks to add clarification 'NOTE' on MM ID. Hyunsook (LGE) provides r08. Dan (China Mobile) object the NOTE, so r08 is not acceptable, providing r09 with removing the NOTE. Shabnam (Ericsson) indicates that r05 is the only acceptable version. ==== Revisions Deadline ==== Xinpeng(Huawei) prefers r06, r07, r09, and can live with r08, objects to all other versions. Dan(China Mobile) suggest to go with r05. Mengzhen (China Telecom) proposes to go with: r10= r5+ below changes including: 1) undo the change for the 2th, 3th, 4th, 5th, 6th. 2) we only focus on the first change. for the first change, undo the change for step 1. Jinhua (Xiaomi) comments, Dan (China Mobile) agree and suggest to go with: r10= r5+ below changes including: 1) undo the change for the 2th, 3th, 4th, 5th, 6th. 2)only focus on the first change. for the first change, undo the change for step 1. Paul (Ericsson) can only accept r05 and objects to any other revisions. Dan(China Mobile) think we should close the discussion for KI#1&2 in this meeting, but there is an EN in 502, so we should have a version to be approved. So please double check whether r10(i.e. change based on r05) can be ok to move forward. Mengzhen (China Telecom) request for CC#3/CC#4 Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees as a compromise to proceed with r10 in order to make at least some progress Dan(China Mobile) provide r11 with removing the change over change based on r10. r11=r5+below: 1) undo the change for the 2th, 3th, 4th, 5th, 6th. 2)only focus on the first change. for the first change, undo the change for step 1. Hyunsook (LGE) can agree with r11. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306186 | CR | Approval | 23.502 CR4045R1 (Rel-18, 'B'): Procedures update to support policy control enhancements for multi-modal flows | China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Samsung, China Mobile, Tencent, LG Electronics, ZTE | Rel-18 | Revision of S2-2304649r05. Approved | Agreed | |
| 9.12.2 | S2-2304676 | CR | Approval | 23.502 CR4049 (Rel-18, 'F'): Clarification on Multi-modal Service ID update in this release | LG Electronics, Xiaomi | Rel-18 | Noted | Dan(China Mobile)suggests to merge this paper into S2-2304649 ==== Revisions Deadline ==== Hyunsook (LGE) asks to mark it as 'NOTED' ==== Comments Deadline ==== | Noted |
| 9.12.2 | - | - | - | KI#3 General | - | - | Docs:=5 | - | |
| 9.12.2 | S2-2304391 | DISCUSSION | Agreement | Discussion on the open issues in KI#3 | vivo | Rel-18 | Noted | Hui(Huawei) proposes to note this discussion paper which was marked as 'for agreement' ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305218 | CR | Approval | 23.501 CR4183R2 (Rel-18, 'B'): Support of extra traffic characteristics for alternative QoS profile | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2303134 from S2#155. Check Affected Clauses! r04 agreed. Revised to S2-2306187. | Dario (Qualcomm) comments and asks questions for clarification. Hui(Huawei) comments and provides r01 Youngkyo(Samsung) comments Hui(Huawei) replies to Youngkyo Youngkyo(Samsung) replies to Hui Devaki (Nokia) provides r02. Dario (Qualcomm) provides r03 ==== Revisions Deadline ==== Dario (Qualcomm) supports r04 (which, it seems, was provided and announced before the rev. deadline); is not OK with r0/1/2. Hui(Huawei) supports r04. Chunshan(CATT) supports r04. Paul (Ericsson) asks to take r04 to CC#3 or CC#4. Dan (China Mobile) r04 is provided before the revision deadline, but missing '>' so not captured in chairman note. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306187 | CR | Approval | 23.501 CR4183R3 (Rel-18, 'B'): Support of extra traffic characteristics for alternative QoS profile | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305218r04. Approved | Agreed | |
| 9.12.2 | S2-2304630 | CR | Approval | 23.501 CR4364 (Rel-18, 'F'): Update on Data rate Monitoring | CATT | Rel-18 | r05 agreed. Revised to S2-2306188. | Shabnam (Ericsson) provides comments with updated r01 Dario (Qualcomm) comments and support r01. Chunshan (CATT) comments and support r02. Mengzhen (China Telecom) comments. Chunshan(CATT) provides clarification to Mengzhen (China Telecom). Dan(China Mobile) do not agree the update of the EN. suggest to merge into 4392. Xiaowan Ke(vivo) provides r03 Chunshan(CATT) provides r04. Dan(China Mobile) have concern for this paper, especially the EN Hui (Huawei) asks to clarify the information rather than add a new one. Haley(Lenovo) comments and prefers available data rate. Paul (Ericsson) as already stated in r01, data rate related updates should be preferably postponed until RAN3 response is received. On the discussion concerning 'available data rate', such is not included in the conclusions and thus can't be progressed. Paul (Ericsson) provides r05 and comments. ==== Revisions Deadline ==== Dario (Qualcomm) is OK with r05 and r01. Is not OK with other revisions. Paul (Ericsson) we accept r01 and r05, we object to all other revisions. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306188 | CR | Approval | 23.501 CR4364R1 (Rel-18, 'F'): Update on Data Rate Monitoring | CATT | Rel-18 | Revision of S2-2304630r05. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#3 L4S | - | - | Docs:=9 | - | |
| 9.12.2 | S2-2304165 | CR | Approval | 23.501 CR4219 (Rel-18, 'C'): Resolution of EN for L4S | Ericsson | Rel-18 | r15 agreed. Revised to S2-2306189, merging S2-2305376 and S2-2304762 | Lei(Tencent) rapporteur proposes to take this paper as baseline 501 CR for L4S. Devaki (Nokia) provides r01. Lei(Tencent) provides comments to Devaki (Nokia). Youngkyo(Samsung) provides r02. Hui(Huawei) comments on r01. Hui(Huawei) provides r03. Boren (OPPO) comments. Paul (Ericsson) provides comments. Hui(Huawei) replies to Paul. Paul (Ericsson) replies. Paul (Ericsson) provides r04. Devaki (Nokia) provides r05. Devaki (Nokia) comments. Mukesh (MediaTek) provides r06. Youngkyo(Samsung) provides r08. Hui(Huawei) provides r09. Youngkyo(Samsung) provides comments to Hui. Hui(Huawei) replies to Youngkyo and provide r10. Youngkyo(Samsung) provides further comments to Hui. Boren (OPPO) provides comments on r11. Xiaowan Ke(vivo) provides r12 Paul (Ericsson) provides r13. Dario (Qualcomm) provides r14 and asks questions that currently do not seem addressed in the CR. Devaki (Nokia) proposes a way forward to address UE mobility scenario for UPF based L4S marking. Hui (Huawei) provides r15 Hui (Huawei) replies to Devaki. Paul (Ericsson) provides a way forward without RAN impacts. ==== Revisions Deadline ==== Hui (Huawei) replies.. Devaki (Nokia) asks a question for clarification. Dario (Qualcomm) cannot accept (= objects) any revision unless his questions are addressed or ENs are included. Devaki (Nokia) proposes that we could consider going with the latest version undoing the removal of the EN to continue discussion on this mobility topic until next week. This is to make progress but also allow time for consensus. Hui(Huawei) support r10 and r15, objects all other revisions and r00. Paul (Ericsson) support r00, 04,13 and can also accept r15. Hui(Huawei) replies to Devaki. Xiaowan Ke(vivo) think keep the EN is reasonable and propose to agree with r15 Devaki (Nokia) is fine with r15 (including the EN). Lei(Tencent) asks if need mark for CC#4 or go with r15 with EN? Paul (Ericsson) replies that there is an EN and asks to take r15 to CC#4. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306189 | CR | Approval | 23.501 CR4219R1 (Rel-18, 'C'): Resolution of EN for L4S | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Meta USA | Rel-18 | Revision of S2-2304165r15, merging S2-2305376 and S2-2304762. Approved | Agreed | |
| 9.12.2 | S2-2305376 | CR | Approval | 23.501 CR4526R1 (Rel-18, 'C'): Providing option for L4S congestion handle in the case of UE mobility and/or non-homogeneous deployment scenarios when some nodes in the 5G network do not support L4S | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305213. Merged into S2-2306189 | Lei(Tencent) rapporteur proposes to merge this paper to S2-2304165. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304762 | CR | Approval | 23.501 CR4402 (Rel-18, 'B'): Congestion exposure method change due to UE mobility | Samsung | Rel-18 | Merged into S2-2306189 | Lei(Tencent) rapporteur proposes to merge this paper to S2-2304165. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304629 | CR | Approval | 23.503 CR0897R1 (Rel-18, 'B'): Policy Control for L4S | CATT | Rel-18 | Revision of S2-2302241 from S2#155. CC#4: r11 + changes agreed. Revised to S2-2306241, merging S2-2305153. r11? For CC#4 | Shabnam (Ericsson) provides comments and r01 Youngkyo(Samsung) provides a comment Devaki (Nokia) comments. Lei(Tencent) rapporteur proposes to take this paper as baseline 503 CR for L4S. Hui (Huawei) comments. Chunshan(CATT) provides r02 and clarification. Hui(Huawei) provides r03 and ask question. Paul (Ericsson) provides comments. Xiaowan Ke(vivo) provides comments and r04 Curt (Meta) suggests some texts for better clarify... Chunshan(CATT) provides concerns on r04. Haley(Lenovo) asks for clarification. Devaki (Nokia) proposes r05. Chunshan(CATT) provides r06. Paul (Ericsson) provides r07 and comments. Chunshan(CATT) provides r08. Xiaowan Ke(vivo) provides r09 Xiaowan Ke(vivo) provides r10 Paul (Ericsson) provides r11 and comments. ==== Revisions Deadline ==== Hui(Huawei) can accept r03/r04/r05, objects all other revisions and r00. Devaki (Nokia) comments that we are also ok with r03/4/5, object to other revisions as the PCC rule is unnecessarily restrictive. Paul (Ericsson) provides r12 and asks to take it to CC#3 or CC#4. Chunshan(CATT) comments. Paul (Ericsson) replies. ==== Comments Deadline ==== Paul (Ericsson) proposes to discuss an updated version based on r11 in CC#4. Dan (China Mobile) can only accept to endorse this paper since new EN is added. Let's continue the discussion in next meeting. Chunshan(CATT) proposes to delete the EN since there is no such requirements in the TS23.501. Hui(Huawei) disagree with the EN. Paul (Ericsson) proposes a way forward. Dan (China Mobile) proposes to remove the EN and let's more forward with r12+removing the EN. Dan (China Mobile) proposes to remove the EN and let's more forward with r11+update+removing the EN. | Revised |
| 9.12.2 | S2-2306241 | CR | Approval | 23.503 CR0897R2 (Rel-18, 'B'): Policy Control for L4S | CATT, Samsung | Rel-18 | Revision of S2-2304629r11 + changes, merging S2-2305153. Approved | Agreed | |
| 9.12.2 | S2-2305153 | CR | Approval | 23.503 CR1024 (Rel-18, 'B'): Policy enhancement of ECN Marking for L4S | China Mobile | Rel-18 | Merged into S2-2306241 Merge into (revision of) S2-2304629 | Lei(Tencent) rapporteur proposes to merge this paper into S2-2304629. Dan(China mobile) agree to merge this paper into S2-2304629. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304619 | CR | Approval | 23.502 CR4041 (Rel-18, 'B'): Signalling procedures to support ECN marking for L4S. | OPPO | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2306190. | Lei(Tencent) rapporteur proposes to take this paper as baseline 502 CR for L4S. Dario (Qualcomm) asks question for understanding. Boren (OPPO) responses to Dario (Qualcomm). Hui (Huawei) comments. Boren (OPPO) responses to Hui (Huawei). Paul (Ericsson) provides comments and supports this CR. Xiaowan Ke(vivo) provides r01 Dario (Qualcomm) replies to Boren and proposes change in CR. Hui (Huawei) provides r02 Boren (OPPO) responses to all ==== Revisions Deadline ==== Hui (Huawei) can accept r02 and objects all other versions. Boren (OPPO) is fine with r02. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306190 | CR | Approval | 23.502 CR4041R1 (Rel-18, 'B'): Signaling procedures to support ECN marking for L4S. | OPPO, Samsung | Rel-18 | Revision of S2-2304619r02. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#3 API based | - | - | Docs:=5 | - | |
| 9.12.2 | S2-2305147 | CR | Approval | 23.501 CR4503 (Rel-18, 'C'): Update for network exposure for XR services | Tencent, Tencent Cloud | Rel-18 | r11 agreed. Revised to S2-2306191. | Shabnam (Ericsson) provides comments Shabnam (Ericsson) provides comments r01 provided as well. Youngkyo(Samsung) provides r02. Lei(Tencent) rapporteur proposes to take this paper as baseline 501 CR for API-based exposure. Dario (Qualcomm) asks question for clarification. Zhuoyun (Tencent) provides r03. Hui (Huawei) provides r04. Xiaowan Ke(vivo) comment and provides r05 Paul (Ericsson) asks questions for clarification. Haley(Lenovo) comments and provides r06 Xiaowan Ke(vivo) replies to Paul (Ericsson) Zhuoyun (Tencent) provides r07. Devaki (Nokia) provides r08, objects to earlier revisions. Object to introducing congestion reporting over N2 (which goes beyond TR conclusion). Zhuoyun (Tencent) comments. Hui (Huawei) provides r09. Paul (Ericsson) provides r10 based on r08. Zhuoyun (Tencent) provides r11. ==== Revisions Deadline ==== Paul (Ericsson) is ok with r01, r10 and r11, objects to other revisions. Hui (Huawei) is ok with r09 and r11. Objects other versions. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306191 | CR | Approval | 23.501 CR4503R1 (Rel-18, 'C'): Update for network exposure for XR services | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2305147r11. Approved | Agreed | |
| 9.12.2 | S2-2305214 | CR | Approval | 23.502 CR3718R2 (Rel-18, 'B'): Update TS23.502 to reflect conclusion of KI#3 for XRM in TR23.700-60 for the API based congestion exposure option | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2303130 from S2#155. r02 agreed. Revised to S2-2306192. | Shabnam (Ericsson) provides comments and r01 Lei(Tencent) rapporteur proposes to take this paper as baseline 502 CR for API-based exposure. Hui(Huawei) provides comments to r01 Hui(Huawei) provides r02 Devaki (Nokia) comments that we are ok with r02 to limit the scope of the CR for now. Paul (Ericsson) we are OK with r02. ==== Revisions Deadline ==== Chunshan(CATT) supports r02 and kindly asks for co-sign. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306192 | CR | Approval | 23.502 CR3718R3 (Rel-18, 'B'): Update TS23.502 to reflect conclusion of KI#3 for XRM in TR23.700-60 for the API based congestion exposure option | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305214r02. Approved | Agreed | |
| 9.12.2 | S2-2304783 | CR | Approval | 23.288 CR0786 (Rel-18, 'B'): NWDAF exposes the Average UE bitrate to AF | Huawei, HiSilicon | Rel-18 | Noted | Dario (Qualcomm) comments and asks questions for clarification. Xinpeng(Huawei) replies to Dario (Qualcomm). Xinpeng(Huawei) replies to LaeYoung (LGE). LaeYoung (LGE) provides comment. LaeYoung (LGE) asks a f/up Q. LaeYoung (LGE) asks further questions to Xinpeng (Huawei). Dario (Qualcomm) replies to Xinpeng. Xinpeng(Huawei) provides r02, and replies to Dario (Qualcomm). Xinpeng(Huawei) provides r03. LaeYoung (LGE) provides comment on r03. LaeYoung (LGE) is fine with r04. ==== Revisions Deadline ==== Dario (Qualcomm) objects to any revision of this paper. Xinpeng(Huawei) replies Dario (Qualcomm). ==== Comments Deadline ==== | Noted |
| 9.12.2 | - | - | - | KI#3 QoS monitoring | - | - | Docs:=4 | - | |
| 9.12.2 | S2-2304392 | CR | Approval | 23.501 CR4294 (Rel-18, 'B'): QoS Monitoring and 5GS information exposure update | vivo | Rel-18 | CC#4: Noted r12? For CC#4 | Lei(Tencent) rapporteur proposes to take this paper as baseline 501 CR for QoS monitoring, e.g. focusing on 5.45.X. Changes to 5.37.X are better to be merged into 5147. Xiaowan Ke(vivo) provides r01 Boren (OPPO) comments Mukesh (MediaTek) seek clarification from Xiaowan (vivo). Xiaowan Ke(vivo) replies to Mukesh (MediaTek) Dario (Qualcomm) comments and provides r02. Paul (Ericsson) provides comments and r03. Xiaowan(ke) replies to Paul (Ericsson), comments on r03, and provide r04 Chunshan(CATT) merges the S2-2304630 and provide r05. Boren (OPPO) provides r06. Paul (Ericsson) provides r07 and comments. Hui (Huawei) provides r08 as a way forward. Xiaowan Ke(vivo) provides r09 Boren (OPPO) comments. Xiaowan Ke(vivo) provides r10 Paul (Ericsson) provides r11 and comments. Dan (China Mobile) provides r12 based on r11 with only combine the second and third clause of 5.45.3. ==== Revisions Deadline ==== Hui (Huawei) can only accept r8 and r10, objects all other versions. Xiaowan(vivo) suggest to agree r12 and clause 5.37.3.3 with addition in of 'The 'percentage of congestion level for exposure' in clause 5.45.3 and 'percentage of packets that UPF uses for ECN marking for L4S' in clause 5.37.3.3 share same value. RAN only needs to report one percentage which is common for the both cases and need not to differentiate whether UPF use this percentage for congestion information exposure and/or for ECN marking for L4S in PSA UPF.', i.e. the same text as in clause 5.45.3. Hui (Huawei) : Xiaowan's proposal is workable to me as well. Paul (Ericsson) provides comments. Xiaowan Ke(vivo) replies to Paul (Ericsson) Paul (Ericsson) provides r14 clarifying that what the common, shared same value is, otherwise the text is ambiguous: ' share same value, namely, the percentage of packets that UPF uses for ECN marking for L4S.' Xiaowan(vivo) replies that Paul (Ericsson) Paul (Ericsson) can accept r03, r07, r11 and r14 and object to all other revisions. Xiaowan Ke (vivo) ask for CC#4 for this paper, and refine the clarification as: 'share same value, namely meaning: the percentage of packets that UPF uses for ECN marking for L4S and percentage of congestion level for exposure simultaneously.' Xiaowan Ke(vivo) asks for CC#4, provides r15: i.e. on top of r12 and clause 5.37.3.3 with addition in of 'The 'percentage of congestion level for exposure' in clause 5.45.3 and 'percentage of packets that UPF uses for ECN marking for L4S' in clause 5.37.3.3 share same value, namely meaning, the percentage of packets that UPF uses for ECN marking for L4S and percentage of congestion level for exposure simultaneously. RAN only needs to report one percentage which is common for the both cases and need not to differentiate whether UPF use this percentage for congestion information exposure and/or for ECN marking for L4S in PSA UPF. ', i.e. the same text as in clause 5.45.3. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304394 | CR | Approval | 23.503 CR0967 (Rel-18, 'B'): QoS monitoring enhancement | vivo, Lenovo, Tencent, Tencent Cloud, China Mobile | Rel-18 | r04 agreed. Revised to S2-2306193, merging S2-2304173 | Lei(Tencent) rapporteur proposes to take this paper as baseline 503 CR for QoS monitoring. Dan(China Mobile) proposes to take the PDV related discussion in S2-2304168 Paul (Ericsson) provides comments and questions. Dario (Qualcomm) asks questions for understanding. Hui (Huawei) provides comments. Xiaowan Ke(vivo) provides r01 Paul (Ericsson) provides comments and r02. Dario (Qualcomm) reinstates his questions. Xiaowan(vivo) replies Dario (Qualcomm) and provide r03. Paul (Ericsson) provides r04 and comments. ==== Revisions Deadline ==== Dario (Qualcomm) thanks Xiaowan for her reply. Chunshan(CATT) accepts r04 only after the 'two media flows' changed into 'one media flow'. Chunshan(CATT) accepts r03 and accepts r04 only after the 'two media flows' changed into 'one media flow'. Xiaowan(vivo) replies to Chunshan(CATT) that after 6.1.3.27.2 in 23503, two flows case exists in the spec and r04 is correct. Paul (Ericsson) asks Chunshan if, with Xiaowan explanation CATT can accept r04. Chunshan(CATT) replies to Xiaowan(vivo). Xiaowan propose to agree r03 Paul (Ericsson) provides a draft revision for CC#3 where RTT aspects are removed. Chunshan(CATT) replies to Paul (Ericsson). Paul (Ericsson) replies. Xiaowan(vivo) replies to Paul (Ericsson) and Chunshan(CATT) that it seems we have consensus on postpone multiple flows RT delay. Xiaowan(vivo) also agree r04 minus the changes for multiple flows RT delay detail ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306193 | CR | Approval | 23.503 CR0967R1 (Rel-18, 'B'): QoS monitoring enhancement | Vivo, Lenovo, Tencent, Tencent Cloud, China Mobile | Rel-18 | Revision of S2-2304394r04, merging S2-2304173. Approved | Agreed | |
| 9.12.2 | S2-2304173 | CR | Approval | 23.503 CR0956 (Rel-18, 'B'): AF can subscribe QoS parameters that PCF derives from QoS Monitoring reports from SMF | Ericsson | Rel-18 | Merged into S2-2306193 | Lei(Tencent) rapporteur proposes to merge this paper into S2-2304394. Paul (Ericsson) explains why 4173 can't be merged in 4394, and this is because these two papers follow very different principles. Before a decision can be made, Ericsson proposes to discuss and agree on the principles first. Lei(Tencent) replies to Paul (Ericsson) and clarifies ==== Revisions Deadline ==== Hui(Huawei): this paper should be either noted or merged. ==== Comments Deadline ==== | Merged |
| 9.12.2 | - | - | - | KI#4,5 General | - | - | Docs:=15 | - | |
| 9.12.2 | S2-2305184 | DISCUSSION | Information | KI#4_DP_Discussion on the Charging Issue of PDU Set Discard | Xiaomi, Lenovo | Rel-18 | Revision of S2-2303052 from S2#155. Noted | Dario (Qualcomm) comments. Dimitris (Lenovo) responds to Dario Yali(OPPO) comments Jinhua (Xiaomi) replies. Xiaowan Ke(vivo) provides views Jinhua (Xiaomi) replies, ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304719 | CR | Approval | 23.501 CR4383 (Rel-18, 'B'): Resolve ENs for support of PDU Set handling | Huawei, HiSilicon | Rel-18 | r20 agreed. Revised to S2-2306194, merging S2-2305230, S2-2305148, S2-2304297, S2-2304289 and part of S2-2304395 | Devaki (Nokia) provides r01. Youngkyo(Samsung) provides r02. Dan(China Mobile)suggests to use this paper as baseline for KI#4&5 501 CR. Hui(Huawei) provides r03. Yali(OPPO) provides comments. Jinhua (Xiaomi) comments, replies to Hui and Yali, Hui(Huawei) provides r04 and replies to Yali. Xiaowan Ke(vivo) provides comments and r05 Saso (Intel) supports keeping the PSIHI. Yali(OPPO) provides r06 Mukesh (MediaTek) provides comments and r07 Xiaowan(vivo) replies to Yali(OPPO) and seek further clarification on the reason SMF sends PSIHI to UE Yali(OPPO) replies to Xiaowan(vivo) Mike (InterDigital) comments Paul (Ericsson) provides comments. Dario (Qualcomm) comments, provides r09, asks to disregard r08. Curt (Meta) comments...mainly is aligned with r09 from Dario (Qualcomm). Yali (OPPO) provides r10 Hui (Huawei) provides comments Paul (Ericsson) provides r11. Xiaowan Ke(vivo) provides r12 Zhuoyun (Tencent) provides r13. Mukesh (MediaTek) provides r14. Paul (Ericsson) replies to Xiaowan. Dario (Qualcomm) comments and provides r15. Hui (Huawei) provides r16. Devaki (Nokia) provides r16. Hui (Huawei) clarify r16 is from Devaki. Provides r17 on top of r16. Yali (OPPO) comments. Xiaowan Ke(vivo) replies to Paul (Ericsson) Paul (Ericson) replies. Xiaowan(vivo) replies Paul (Ericson) Xiaowan Ke(vivo) provides r18 Yali(OPPO) provides r19 Hui(Huawei) provides r20 ==== Revisions Deadline ==== Dario (Qualcomm) is OK only with r09, objects to all other releases; if in 5.7.7.1 'SMF indication to RAN to activate PDU Set QoS Handling' is removed, then r15 or r20 are acceptable. Devaki (Nokia) can accept anything above r16...r20, objects to other versions. Devaki (Nokia) prefers r20. Hui(Huawei) clarify to Dario on r20 Paul (Ericsson) provides comments and can accept r20 and r11, objects to all other revisions. Zhuoyun (Tencent) can accept r09, r13-20, objects to other revisions. Paul (Ericsson) given all PDU Set QoS parameters are optional, can someone explain how they can be used to indicate PDU Set info? Hui (Huawei) replies Dario (Qualcomm) replies to Paul and is OK with r20 minus the indication as explained above. Paul (Ericsson) replies to Dario. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306194 | CR | Approval | 23.501 CR4383R1 (Rel-18, 'B'): Resolve ENs for support of PDU Set handling | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson | Rel-18 | Revision of S2-2304719r20, merging S2-2305230, S2-2305148, S2-2304297, S2-2304289 and part of S2-2304395. Approved | Agreed | |
| 9.12.2 | S2-2304289 | CR | Approval | 23.501 CR4262 (Rel-18, 'C'): QoS Flow level QoS parameter for PDU Set handling | OPPO | Rel-18 | Merged into S2-2306194 | Dan(China Mobile)suggests to merge this paper into 4719. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304297 | CR | Approval | 23.501 CR4265 (Rel-18, 'B'): Updates to PDU Set based handling | MediaTek | Rel-18 | Merged into S2-2306194 | Dan(China Mobile)suggests to merge this paper into 4719. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305216 | CR | Approval | 23.501 CR4527 (Rel-18, 'B'): Update TS23.501 for PDU Set and PDU Handling | Nokia, Nokia Shanghai Bell | Rel-18 | r05 agreed. CC#4: r11 + changes agreed. Revised to S2-2306239. r05?. For CC#4 | Devaki (Nokia) provides that this document is handled separately to capture the outcome of LS out in S2-2304717 (in reply to S2-2303974/S4-230419 from SA4). Rapporteur proposed to merge this with 4719 but the proposal in this paper is not covered by 4719. This document must be separately handled. Dan(China Mobile)suggests to merge this paper into 4719 if possible, or discussed individually Hui (Huawei) provides comments. Devaki (Nokia) comments that there is no overlap between 4719 and this paper at all, intention of this paper is totally different from 4719. Yali (OPPO) comments. Yinglin (China Telecom) asks for clarification. Dario (Qualcomm) comments. Paul (Ericsson) provides comments. Mukesh (MediaTek) comments on the use of Default PDU Set. Devaki (Nokia) replies and provides r01. Chunshan(CATT) provides concerns on this paper John (Futurewei) provides comments. Devaki (Nokia) replies. Jinhua (Xiaomi) comments. Saso (Intel) comments; does not see what problem is being solved; proposes to note the CR. Xiaowan Ke(vivo) provides comments Saso (Intel) comments on the underlying principle proposed by Devaki (Nokia). Devaki (Nokia) replies to Saso (Intel). Saso (Intel) replies to Devaki (Nokia). Devaki (Nokia) provides r02, r03. Yali(OPPO) is fine with r02. Dario (Qualcomm) supports r02. Dan(China Mobile) provide r04 based on r02, not ok with r03. Devaki (Nokia) provides r05 on top of r04. Saso (Intel) seeks clarification on r05 related to how PDU Set parameters are set by UPF for a lone PDU. Saso (Intel) replies to Devaki; provides r06. Yali(OPPO) comments. Chris (Vodafone) is OK with a PDU set having only one PDU. ==== Revisions Deadline ==== Devaki (Nokia) comments. Chunshan (CATT) questions on the 'only one PDU'. Dario (Qualcomm) is OK with r02 and r05; objects to other revisions. Devaki (Nokia) comments that we are fine with any revision except r06, r04. We believe that this CR must be considered as part of SoH along with LS out (to SA4) in 4717. Chunshan(CATT) prefers r05, objects r06,r04. Hui (Huawei is OK with r02 and r05; objects to other revisions. Yali(OPPO) is OK with r02, r04 and r05; objects to other versions. Dimitris (Lenovo) supports r05 Saso (Intel) can live with r05 + clarification on how PDU Set Importance is determined for a lone PDU. Chris (Vodafone) tries to answer Intel's questions. Xiaowan Ke(vivo) see whether the CR can be approved depends on 2304717 voting result Saso (Intel) replies to Chris. Devaki (Nokia) wonders about exact text proposal from Intel for r05 (thanks for the compromise proposal). Saso (Intel) replies to Devaki. Devaki (Nokia) proposes to go with r05 + NOTE: How the UPF determines the PDU Set Importance for a PDU that does not belong to a PDU Set based on classification rules is left to operator configuration. (as proposed by Saso). Xiaowan(vivo) comment the importance on the lone PDU Xiaowan Ke(vivo) object to 'r05 + NOTE: How the UPF determines the PDU Set Importance for a PDU that does not belong to a PDU Set based on classification rules is left to operator configuration. (as proposed by Saso).' Devaki (Nokia) wonders if we can agree r05 + Editor's note: How the UPF determines the PDU Set Importance for a PDU that does not belong to a PDU Set based on classification rules is left to operator configuration (FFS). Xiaowan Ke(vivo) can only live with 'r05 + Editor's note: it is FFS how the UPF determines the PDU Set Importance for a PDU that does not belong to a PDU Set based on classification rules.' Or 'r05 + NOTE: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules.' Dan(China Mobile) suggest we go with r04 with adding NOTE: 'in this release, only the PDUs with the RTP extension can be processed with PDU set QoS handling defined in 5.37.5' Devaki (Nokia) believes r04 + NOTE: 'in this release, only the PDUs with the RTP extension can be processed with PDU set QoS handling defined in 5.37.5' could almost render PDU Set mechanism useless as most applications will have multiplexed traffic thus not acceptable. Majority preference seems to be r05 thus let us stick to it. Devaki (Nokia) proposes r05 + NOTE: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules.' As a way forward to alleviate Xiaowan's and Saso's concerns. Jinhua (Xiaomi) comments, Jari (NTT DOCOMO) comments Paul (Ericsson) provides corrections to r05. Paul (Ericsson) comments. Jinhua (Xiaomi) comments, propose to go with Dan's proposal. The importance of alone PDUs, whether these alone PDUs will be too much, and how to encapsulate them, all of these issues need to make clear. Xiaowan Ke(vivo) replies to Jari (NTT DOCOMO) Devaki (Nokia) proposes to go with r05 + updated text from Paul 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' + 'NOTE: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules.' Devaki (Nokia) proposes to go with r05 + updated text from Paul 'the SMF determines a QoS Profile for the QoS Flow' + 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' + 'NOTE: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules.' Saso (Intel) comments that 'PDU Set Importance is not applied' is even worse because RAN would not know how to handle it for discarding relative to the other PDU Sets. Devaki (Nokia) proposes to go with r05 + updated text from Paul 'the SMF determines a QoS Profile for the QoS Flow' + 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' + 'Editor's note: How PDU Set Importance is applied to the PDU(s) that does not belong to a PDU Set based on Protocol Description is FFS.' Zhuoyun (Tencent) comments: if the EN is to be added, we need to ask SA4 in LS (4717) on their guidance on setting the PSI for this specific PDU Set. Saso (Intel) is OK with the latest proposal from Devaki + removal of 'based on Protocol Description is FFS.' ==== Comments Deadline ==== Dan (China Mobile) can only accept to endorse this paper for this meeting, the version as you proposed, otherwise let's postponed this to next meeting. Devaki (Nokia) indicates that the LS out to SA4 might also be delayed (and/or not sent) if this paper can only be endorsed. Resolution of this EN can also be considered as alignment with other groups during maintenance phase. Hui (Huawei) suggest to agree this CR without adding an EN. Yali(OPPO) also prefers to agree this CR without adding an EN. Xiaowan(vivo) replies to Yali(OPPO) and comment Dan (China Mobile) response and still suggest to remove the EN for the PDU set importance. Dan (China Mobile) provide another way forward, that is change the EN into a NOTE'How PDU Set Importance is applied to the PDU(s) that does not belong to a PDU Set based on Protocol Description is depending on UPF implementation' Devaki (Nokia) proposes that we agree to r05 + updated text from Paul 'the SMF determines a QoS Profile for the QoS Flow' + 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' Xiaowan(vivo) replies to Devaki (Nokia) , r05 need further add 'Note: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules. During congestion, whether and how to drop those PDU(s) without PDU Set Importance is RAN implementation' Dan(China Mobile) replies to Xiaowan, and Devaki, the r05+ 'Note: PDU Set Importance is not applied to the PDU(s) that does not belong to a PDU Set based on classification rules. ' Saso (Intel) is OK with either of these: 1) adding a NOTE: 'PDU Set Importance is determined based on UPF configuration' 2) Adding an EN: 'It is FFS how PDU Set Importance is determined...' Dan (China Mobile) provide r07=r05+updated text from Paul 'the SMF determines a QoS Profile for the QoS Flow' + 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' +'NOTE: In the above case, PDU Set Importance is determined based on UPF configuration' Devaki (Nokia) provides r08 in CC#4 folder. It is r05 + the SMF determines a QoS Profile for the QoS Flow. + Protocol Description for PDU Set identification + NOTE: UPF encapsulates it with the GTP-U header extensions containing PDU Set Information. Saso (Intel) clarifies that from the versions uploaded in the CC#4 folder, r07 provided by Dan is acceptable to Intel. R06 and r08 are not acceptable. Yali(OPPO) provides r09 based on r07. r09=r05+updated text 'the SMF determines a QoS Profile for the QoS Flow' + 'For a PDU that matches to a QoS Flow for PDU Set based QoS Handling, but does not belong to a PDU Set based on the Protocol Description for PDU Set identification, the UPF considers it as a PDU Set with only this PDU and encapsulates it with the GTP-U header extensions containing PDU Set information.' +'NOTE: In the above case, PDU Set Importance is determined based on UPF configuration'. R07 is also ok for me. Xiaowan(vivo) replies Saso (Intel) it is impossible PDU Set Importance is determined based on UPF implantation The PSA UPF can only identify the PDU Set Importance using the Protocol Description and the received packet protocol header (e.g. RTP/SRTP).' Xiaowan(vivo) provide r10 based on Yali's r09 and add 'the PSA UPF can only identify the PDU Set Importance using the Protocol Description and the received packet protocol header (e.g. RTP/SRTP).' Dan(China Mobile) based on all the comment today, in order to move forward, I can accept the EN, but this version should be NOTE in r07 changed into an EN: So the final change is : r05+ updated text from Paul 'the SMF determines a QoS Profile for the QoS Flow' + 'If the UPF receives a PDU that do not belong to a PDU Set based on Protocol Description for PDU Set identification, then the UPF still maps it to a PDU Set (e.g. it could be a PDU Set with just that PDU).' +'Editor's note: How PDU Set Importance is applied to the PDU(s) that does not belong to a PDU Set based on Protocol Description is FFS.' Saso (Intel) replies to Xiaowan to please note that Saso's proposal is that UPF determines PSI based on UPF configuration, not UPF implementation. Xiaowan(vivo) replies Saso (Intel) that I am also OK with an EN for this meeting, but the CR can be endorsed at most Jinhua (Xiaomi) support Dan's proposal, r05+updated text from Paul,+ ENs for working on the perfection next meeting. Devaki (Nokia) comments that I have uploaded Dan's revised proposal as r11 in CC#4 folder. | Revised |
| 9.12.2 | S2-2306239 | CR | Approval | 23.501 CR4527R1 (Rel-18, 'B'): Update TS23.501 for PDU Set and PDU Handling | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305216r11 + changes. CC#4: Technically Endorsed For CC#4 | Endorsed | |
| 9.12.2 | S2-2305148 | CR | Approval | 23.501 CR4504 (Rel-18, 'C'): Update for PDU Set handling support | Tencent, Tencent Cloud | Rel-18 | Merged into S2-2306194 | Dan(China Mobile)suggests to merge this paper into 4719. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305230 | CR | Approval | 23.501 CR4531 (Rel-18, 'B'): KI#5: Addressing open issues for support of PDU Set based handling | Qualcomm Incorporated | Rel-18 | Merged into S2-2306194 | Dan(China Mobile)suggests to merge this paper into 4719. Dario (Qualcomm) OK to merge this into 4179 (for the general part) and 5199 (for the non-homogenous deployment part). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304389 | CR | Approval | 23.502 CR3999 (Rel-18, 'B'): PDU Set information provisioning | KDDI, Futurewei, China Mobile, Tencent | Rel-18 | r01 agreed. Revised to S2-2306195. | Dan(China Mobile)suggests to use this paper as the baseline for KI#4&5 502 CR. Kenichi (KDDI) provides r01. ==== Revisions Deadline ==== Devaki (Nokia) supports the revision r01, wishes to cosign the final version of the paper as Nokia, Nokia Shanghai Bell. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306195 | CR | Approval | 23.502 CR3999R1 (Rel-18, 'B'): PDU Set information provisioning | KDDI, Futurewei, China Mobile, Tencent, Huawei, Samsung, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304389r01. Approved | Agreed | |
| 9.12.2 | S2-2305185 | CR | Approval | 23.501 CR4518 (Rel-18, 'B'): The update of PDU Set based QoS Handling | Xiaomi, Lenovo | Rel-18 | Noted | Devaki (Nokia) comments that the proposal to send back the PDUs to be discarded seems to be unnecessary overhead. Also, unclear where the requirement for this comes from. Dan(China Mobile)suggests to merge this paper into 4719. Boren (OPPO) comments. Jinhua (Xiaomi) replies to Dan, Jinhua (Xiaomi) replies to Devaki, Mukesh (MediaTek) agrees with Dan (China Mobile) to merge this CR into 4719. Dario (Qualcomm) points to his comments for 5184 and believes there is no problem to solve. John (Futurewei) does not think there is any issue on charging to solve. Jinhua (Xiaomi) replies to Boren, Jinhua (Xiaomi) replies to Mukesh, Jinhua (Xiaomi) replies to Dario, it is an issue to be addressed. when the PDU set based QoS handling introduced, it will make an avalanche of PDUs discarding, because of the Discarding is per Set not Per PDU again. Jinhua (Xiaomi) replies to John, Mukesh (MediaTek) responds to Jinhua (Xiaomi) John (Futurewei) replies why there are no additional packet drops, and hence no need for charging Dario (Qualcomm) replies to Jinhua Jinhua (Xiaomi) replies to John, and provides r01 Mukesh (MediaTek) replies to Jinhua (Xiaomi). Paul (Ericsson) provides comments. Jinhua (Xiaomi) replies to Paul, Mukesh and all, ==== Revisions Deadline ==== Dario (Qualcomm) objects to r01 and original version. Mukesh (MediaTek) Proposes to note this CR as there is no backing. Jinhua (Xiaomi) replies to Mukesh and Dario, ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304395 | CR | Approval | 23.501 CR4295 (Rel-18, 'B'): Fix ENs for PDU Set QoS and PDU Set handling | vivo | Rel-18 | Partially merged into S2-2306194 | Dan(China Mobile)suggests to merge this paper into 4719. Chris Joul (T-Mobile USA) Cannot agree to the baseline version of this CR and provides comments. Dan (China Mobile) further clarify that the SST related part should be merged into 5132, and let's take the slice related discussion in S2-2305132. Xiaowan Ke(vivo) replies Chris Joul (T-Mobile USA) that what you don't agree is where to capture the SST. Based on that, I am ok to merge 'the part not related to SST' to 4719. And consider SST discussion in 5132 ==== Revisions Deadline ==== Hui(Huawei): this paper is merged. ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305231 | CR | Approval | 23.503 CR0891R2 (Rel-18, 'B'): KI#5: Support for PDU Set QoS Framework | Qualcomm Incorporated | Rel-18 | Revision of S2-2302523 from S2#155. r13 agreed. Revised to S2-2306196. | Devaki (Nokia) provides r01. Xiaowan Ke(vivo) provides r02 Youngkyo(Samsung) asks questions. Chunshan(CATT) provides r03 Jinhua (Xiaomi) comments, Mike (InterDigital) comments Paul (Ericsson) provides comments. Dario (Qualcomm) replies and provides r04. Chunshan(CATT) provides r05. Youngkyo(Samsung) provides r06. Yali(OPPO) comments. Jari (NTT DOCOMO) comments Paul (Ericsson) provides r07 and comments. Mirko (Huawei) comments. Saso (Intel) seeks clarification on r07 and comments. Paul (Ericsson) replies to Saso. Dario (Qualcomm) replies, provides r08, r09 and asks questions about r07. Chunshan(CATT) comments; Chunshan(CATT) replies to Mirko (Huawei). Saso (Intel) supports r09; thinks r08 requires more discussion. Mirko (Huawei) provides r10. Chunshan(CATT) provides r11 based on r09 and R12 based r08. Dario (Qualcomm) provides r13 based on r10 ==== Revisions Deadline ==== Chunshan(CATT) supports r12, and r13(needs further to update the affected clauses in the cover page to remove 6.2.1.2 and 6.2.2.1). Devaki (Nokia) also supports, wishes to cosign r13, thanks for incorporating our feedback (especially avoiding duplication as much as possible) Paul (Ericsson) can accept r07 and r13 and objects to all other revisions. Ericsson wishes to be added to the list of sourcing companies. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306196 | CR | Approval | 23.503 CR0891R3 (Rel-18, 'B'): KI#5: Support for PDU Set QoS Framework | Qualcomm Incorporated, Apple, vivo, CATT, Samsung, Meta USA, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2305231r13. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#4,5 PDU set importance | - | - | Docs:=4 | - | |
| 9.12.2 | S2-2305101 | DISCUSSION | Agreement | PDU Set Importance across QoS Flows and Priority Level. | Intel | Rel-18 | Revision of S2-2302398 from S2#155. Noted | Hui(Huawei) proposes to note this discussion paper which was marked as 'for agreement' ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305107 | CR | Approval | 23.501 CR4486 (Rel-18, 'F'): PDU Set Importance spanning across QoS Flows | Intel | Rel-18 | CC#4: r07 + changes agreed. Revised to S2-2306243, merging S2-2304546. r07? +. the term 'relative' + add reference to Priority Level clause'. For CC#4 | Mukesh (MediaTek) seek clarification from Saso (Intel). Dario (Qualcomm) supports Mukesh's view and thinks that the PDU Set importance should apply only within a QoS Flow. Mengzhen (China Telecom) share the same view with Dario (Qualcomm) and Mukesh (MediaTek). Jinguo(ZTE) supports this paper Youngkyo(Samsung) shares the Mukesh/Dario's view. Curt (Meta), similarly to the reasons given by ZTE, we support this paper as well. Zhuoyun (Tencent) comments. Hui(Huawei) provides r01. Saso (Intel) provides r02. Sudeep (Apple) comments on r02. Saso (Intel) replies to Sudeep. Sudeep (Apple) proposes to remove the EN without any new NOTE. Saso (Intel) replies to Sudeep and Zhuoyun. Xiaowan Ke(vivo) seeks clarification Mengzhen (China Telecom) is ok with r02. Youngkyo(Samsung) comments for understanding. Devaki (Nokia) provides r03. Dario (Qualcomm) is not OK with any revision of this paper and supports 4546. Youngkyo(Samsung) shares Dario's view and supports 4546's change. Mengzhen (China Telecom) comments. Saso (Intel) provides replies. Provides r04 Sudeep (Apple) provides comments. Mengzhen (China Telecom) comments and provides r05. Saso (Intel) is OK with r05. Xiaowan(vivo) request to remove 'of different UE' from r05. Xiaowan Ke(vivo) provides r06 Saso (Intel) replies to Xiaowan. Xiaowan Ke(vivo) replies to Saso(Intel) Saso (Intel) replies to Xiaowan; provides r07. Devaki (Nokia) provides r08 (I had to use r06 as the baseline). ==== Revisions Deadline ==== Curt (Meta) can accept r07. Not okay with r08 because 'same UE' phase is kept. Devaki (Nokia) comments that we are not ok with r07 as it does not solve the issue when the importance values are different thus prefer r08. OK with either r08 as-is or r08 + different UE(s) re-instated or r07 + the term 'relative' + add reference to Priority Level clause. (to relate to existing priority level, otherwise, this remains unclear. Sudeep (Apple) responds to Saso (Intel). Curt (Meta) comments - 'r07 + the term 'relative' + add reference to Priority Level clause' is fine for me. Dario (Qualcomm) objects to any revision of this CR and proposes to agree 4546. Devaki (Nokia) comments. Hui (Huawei) objects to r00/r03/r04 and prefer to r01/r02. Xiaowan Ke(vivo) request to note this paper and let RAN to implement. Saso (Intel) provides r09 in DRAFTs folder based on r08 with removal of '(of the same UE)'. Requests to open it in CC#3 or CC#4. Magnus (Ericsson) objects r00 are ok with r02, but cover page needs to be fixed Jinhua (Xiaomi) comments, propose to go with r09=r08 with removal of '(of the same UE)', or r07 + the term 'relative', Magnus H (Ericsson) withdraws all my comments on this tdoc, wrong thread. Sudeep (Apple) can accept r08 without the new NOTE. Otherwise, we can agree on S2-2304546. Dario (Qualcomm) same view as Sudeep: for us either r08 w/o NOTE or 4546 is acceptable. Devaki (Nokia) agrees to go with r08 without NOTE to make progress. Dan(China Mobile) request this paper to be discussed for CC#4 Saso (Intel) comments that without the NOTE the CR is not clarifying anything. Curt (Meta) supports Saso (intel). Mike (InterDigital) agrees with Curt (Meta) and Saso (intel). ==== Comments Deadline ==== Saso (Intel) provides 5107r10 in CC#4 folder which is based on r07 + the term 'relative' + add reference to Priority Level clause'. Devaki (Nokia) is fine with r10. Since others had objections to this approach, I also propose another way forward that was proposed: r08 without the NOTE. Uploaded as r11 is CC4 folder. | Revised |
| 9.12.2 | S2-2306243 | CR | Approval | 23.501 CR4486R1 (Rel-18, 'F'): PDU Set Importance spanning across QoS Flows | Intel | Rel-18 | Revision of S2-2305107r07 + changes, merging S2-2304546. Approved | Agreed | |
| 9.12.2 | S2-2304546 | CR | Approval | 23.501 CR4339 (Rel-18, 'C'): Resolving EN on PDU Set importance | Apple | Rel-18 | Merged into S2-2306243 Merge into (revision of) S2-2305107 | Dan(China Mobile)suggests to merge this paper into 5107 for PDU set importance. Dario (Qualcomm) supports the original version of this CR. Devaki (Nokia) objects to the original version of this CR as we need to still clarify that priority applies across QoS Flows (even with PDU Sets) or simply keep EN open. ==== Revisions Deadline ==== Hui(Huawei) support this CR, in case a rev of 5107 cannot be approved. Curt (Meta) objects to this CR so we can just focus on the related discussion in xx5107. ==== Comments Deadline ==== | Merged |
| 9.12.2 | - | - | - | KI#4,5-Non-homogeneous | - | - | Docs:=5 | - | |
| 9.12.2 | S2-2305201 | DISCUSSION | Discussion | Discussion on the indication of supporting PDU set handling | Lenovo, Tencent | Rel-18 | Noted | Lenovo (Haley) suggests to discuss all the solutions for non-homogenous support of PDU set handling feature in this thread. Dario (Qualcomm) supports discussing here before agreeing any solution. He also comments that there are other alternatives in addition to the solutions mentioned by Haley and points out issues w/ the RAN capability indication signaling solutions. Jinguo(ZTE) provides replies to Dario(Qualcomm). Lenovo (Haley) replies and suggests to use 5199 thread instead. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305199 | CR | Approval | 23.501 CR4522 (Rel-18, 'B'): PDU set handling support indicator | Lenovo,Tencent, CATT, Xiaomi, Meta USA, Vodafone? | Rel-18 | CC#4: Noted | ZTE proivdes comments and suggest to use 5133 as basis Lenovo (Haley) provides revision and suggest to follow rapporteur's suggestion to use 5199 as the baseline. Dan (China Mobile) support to use 5199 as baseline paper. Jinguo(ZTE) provides r02 Paul (Ericsson) provides r03. Ellen (Google) provides r04 to merge 5292 and comments Dario (Qualcomm) fundamentally disagrees with any RAN capability signaling based solution and proposes r05 based on content of 5230. Devaki (Nokia) supports r05, has concerns with other revisions. Jinguo(ZTE) replies, has concerns on r01, r03, r04 and r05. Haley (Lenovo) replies to all. Request people to choose from option 1 and option 2 as listed in r01 and provide r06. Yali (OPPO) comments. Zhuoyun (Tencent) provides r07. Haley (Lenovo) replies to Yali(OPPO). Yali (OPPO) replies to Haley (Lenovo). Jinguo(ZTE) replies to Yali (OPPO) Yali (OPPO) replies to Jinguo(ZTE). Haley (Lenovo) comments and provides r08. Xiaowan Ke(vivo) provides comments Haley(Lenovo) reminds Mike (InterDigital) that r10 is the same as r09. Mike (InterDigital) thanks Haley (Lenovo) and points out that r11 from Jinguo (ZTE) resolved the issue. Dario (Qualcomm) replies to Haiyan Dario (Qualcomm) replies to Yali Haley(Lenovo) replies to Dario (Qualcomm). Yali(OPPO) replies to Dario (Qualcomm) Dan(China Mobile) replies Hui(Huawei) asks question. Jinguo(ZTE) comments that the SMF local configuration may not work, and provide r12. Haley(Lenovo) thanks Jinguo(ZTE) and replies to DAN(China Mobile) Paul (Ericsson) provides r13 and comments. Jinguo(ZTE) has conern on r13 Haley(Lenovo) also prefers r12. Paul (Ericsson) replies. Haley(Lenovo) replies and provides r14. Chris (Vodafone) and provides r15. ==== Revisions Deadline ==== Dario (Qualcomm) can only accept r05 and objects to other revisions. Haley (Lenovo) replies to Dario(Qualcomm). Jinguo(ZTE) prefers to approve r12, but can live with latest version r15. Ask for CC#3 or CC#4. Zhuoyun (Tencent) prefers r15, could accept r07-14, r00, objects to other versions. Hui(Huawei) replies to Jinguo. Chris (Vodafone) replies to Dario. Haley(Lenovo) prefers 15, ok with r08-14, objects to other versions. Haley(Lenovo) replies and ask for CC#3 or CC#4 too. Devaki (Nokia) comments Haley(Lenovo) replies to Devaki(Nokia) . It is a waste of signaling if SMF provides PDU set QoS parameters for every Xn based handover as it has no knowledge of whether PDU set QoS parameters has been forwarded from source RAN node to target RAN node via Xn interface or not. Jinguo(ZTE) repeat that the issue is not about providing PDU Set QoS parameters to the target RAN, rather on PDU Set marking over user plane Curt (Meta) comments R05 is a solution on how legacy RAN handles new feature interaction. It does not address the problem being stated in this CR (i.e, about UPF resources). Haley (Lenovo) agrees with Curt(Meta) r05 does not address the problem being stated in this CR (i.e, about UPF resources). Ellen (Google) supports the reason for changes of this CR and can accept r09-r15. Dario (Qualcomm) replies to Chris, Haley and Jinguo. Can only accept r05. ==== Comments Deadline ==== Haley (Lenovo) proposes to open it in CC#4 and SoH for r05 and r15. Chris (Vodafone) replies to Qualcomm. | Noted |
| 9.12.2 | S2-2305133 | CR | Approval | 23.501 CR4494 (Rel-18, 'B'): Non-homogenous support for PDU set based QoS handling | ZTE | Rel-18 | Merged into S2-2305199 (noted) | Dan(China Mobile)suggests to merge this paper into 5199 for Non-homogenous. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305292 | CR | Approval | 23.501 CR4542 (Rel-18, 'B'): NG-RAN Support for PDU Set Handling Capability | Rel-18 | Merged into S2-2305199 (noted) | Dan(China Mobile)suggests to merge this paper into 5199 for Non-homogenous. ZTE proivdes comments and suggest to use 5133 as basis Haley (Lenovo) suggests to use 5199 as basis, and we can discuss all the solutions in the thread of 5201 (or 5199?). Ellen (Google) agrees to merge 5292 into 5199 CR and keeps discussion in the thread of 5199/5201. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 9.12.2 | S2-2305200 | CR | Approval | 23.502 CR4127 (Rel-18, 'B'): PDU set handling support indicator | Lenovo, Tencent, CATT, Xiaomi, Meta USA, Vodafone? | Rel-18 | Merged into S2-2305199 (noted) | Dan(China Mobile) whether this paper can be further discussed based on result of 5199 . Jinguo(ZTE) suggests to focus on 501 CR at this meeting Dario (Qualcomm) supports Jinguo in focusing on 501 first. ==== Revisions Deadline ==== Hui(Huawei) proposes to postpone this CR. ==== Comments Deadline ==== | Noted |
| 9.12.2 | - | - | - | KI#6 | - | - | Docs:=8 | - | |
| 9.12.2 | S2-2304350 | CR | Approval | 23.501 CR4278 (Rel-18, 'F'): KI#6 text alignment text | Nokia, Nokia Shanghai Bell | Rel-18 | r05 agreed. Revised to S2-2306197, merging S2-2304722 | Lei(Tencent) rapporteur proposes to take this paper as baseline 501 CR for KI#6. Jinhua (Xiaomi) comments about the exposure notification. Saubhagya (Nokia) provides r01 Boren (OPPO) comments. Paul (Ericsson) we support r01. Xiaowan Ke(vivo) provides r02 Chunshan(CATT) provides r03. Dario (Qualcomm) comments and provides r04. Saubhagya (Nokia) asks for clarification on RT latency reporting Dario (Qualcomm) replies to Saubhagya. Jinhua (Xiaomi) comments, Hui (Huawei) provides r05 Saubhagya (Nokia) provides r06 Saubhagya (Nokia) provides the correct link for r06 Jinhua (Xiaomi) replies, R06 is OK Paul (Ericsson) provides comments. Saubhagya (Nokia) agrees to Paul's (Ericsson) comment and Ok with r05 ==== Revisions Deadline ==== Boren (OPPO) prefers r05, can also accept r06. Jinhua (Xiaomi) replies to Paul, Hui (Huawei) proposes to agree r05, and objects to all other versions Paul (Ericsson) can accept r04 or r05 (do not see the difference), object to any other revisions ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306197 | CR | Approval | 23.501 CR4278R1 (Rel-18, 'F'): KI#6 text alignment text | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304350r05, merging S2-2304722. Approved | Agreed | |
| 9.12.2 | S2-2304722 | CR | Approval | 23.501 CR4384 (Rel-18, 'B'): Updates on UL/DL policy control based on RT requirement | Huawei, HiSilicon | Rel-18 | Merged into S2-2306197 | Lei(Tencent) rapporteur proposes to merge this paper into S2-2304350. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305319 | CR | Approval | 23.501 CR4550 (Rel-18, 'C'): Adding a Maximum UL PDB and a Maximum DL PDB to the RT latency requirement | InterDigital Inc. | Rel-18 | Postponed | Lei(Tencent) rapporteur proposes to handle this 501 CR separately and provide comments Boren (OPPO) comments. Jinhua (Xiaomi) comments. The Maximum DL/UL PDB together with RT latency provided by AF is reasonable. And comment to seek clarification Mike (InterDigital) replies Dario (Qualcomm) comments. Lei(Tencent) comments Saubhagya (Nokia) shares the same view that this CR is not needed; further comments. Jinhua (Xiaomi) comments, supports the Maximum UL/DL PDB, Xiaowan Ke(vivo) provides comments Mike (InterDigital) replies and provides r01. Youngkyo(Samsung) questions. Dario (Qualcomm) replies to Mike. Boren (OPPO) provides comments on r01. Hui (Huawei) provides comments. Xiaowan Ke(vivo) comment and want to the note this paper Mike (InterDigital) replies and provides r02. ==== Revisions Deadline ==== Dario (Qualcomm) objects to all versions of this paper. Mike (InterDigital) replies to Dario (Qualcomm) Jinhua (Xiaomi) comments, support the proposal, r01/02 is OK, Boren (OPPO) objects to all versions of this paper. Hui (Huawei)proposes to note this paper Paul (Ericsson) cannot accept r01, r02 (no more revisions available), object to all revisions --> E/// proposes this paper to be noted as it is not supported by KI conclusions. Xiaowan Ke(vivo) share the view to note this paper Mike (InterDigital) replies and asks a question. Hui (Huawei) replies. Mike (InterDigital) proposes to POSTPONE. ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2304352 | CR | Approval | 23.503 CR0964 (Rel-18, 'F'): KI#6 text alignment | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Lei(Tencent) rapporteur proposes to take this paper as baseline 503 CR for KI#6. Jinhua (Xiaomi) comments and propose to merge the 2nd change of 4721 into 4352. Paul (Ericsson) provides r01. Dario (Qualcomm) supports r01. Chunshan (CATT) provides r02. Hui (Huawei) provides r03. Boren (OPPO) provides r04. Xiaowan Ke(vivo) provides r05 ==== Revisions Deadline ==== Boren (OPPO) can only accept r00, r01, r04, r05, object to other revisions. Chunshan (CATT) accepts r05 only after removing 'If the UL and DL traffic of the service have different traffic descriptions (e.g., different port numbers), the AF provides different traffic description for the UL and DL flows in the request.' Hui(Huawei) can only accept r03/04/05, objects all other versions. Paul (Ericsson) can accept r02, object to any other revisions. Saubhagya (Nokia) provide comments Dario (Qualcomm) prefers r01 Paul (Ericsson) can only accept r01, objects to other revisions, i.e. the previous objections was incorrect ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304721 | CR | Approval | 23.503 CR0994 (Rel-18, 'B'): Corrections on UL/DL policy control based on RT requirement | Huawei, HiSilicon | Rel-18 | Merged into S2-2304352 (noted) Merge into S2-2304352? | Lei(Tencent) rapporteur proposes to consider this paper as merged into S2-2304352. Jinhua (Xiaomi) comments. See the comment in 4352 thread, based on rapporteur's merge proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305187 | CR | Approval | 23.502 CR4121 (Rel-18, 'C'): Procedures update to support QoS monitoring for the correlated multi-modal flows | Xiaomi | Rel-18 | r00 agreed. Revised to S2-2306198. | Lei(Tencent) rapporteur proposes to take this paper as baseline 502 CR for KI#6. ==== Revisions Deadline ==== Paul (Ericsson) cannot accept r00 as it introduces the attribute RT Latency Indication in the update operations (Nnef_AFsessionWithQoS_Update, Npcf_PolicyAuthorization_Update). This was discussed in SA2 #154eAH meeting and finally it was agreed not to add this attribute Reasoning: RT latency indication can only be provided during AF session establishment. Adding this in the update operation means moving the data flows to separate UL & DL QoS flows, which may have impacts on end user experience Jinhua (Xiaomi) replies to Paul, and it will be more helpful if the first comments coming before revision DDL. Paul (Ericsson) replies. Jinhua (Xiaomi) replies to Paul, remove the 2nd and 3rd changes, and keep the 1st change only in R00 is fine? Jinhua (Xiaomi) ask for CC#4, propose to go with 'r00 + remove 2nd &3rd changes'. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306198 | CR | Approval | 23.502 CR4121R1 (Rel-18, 'C'): Procedures update to support QoS monitoring for the correlated multi-modal flows | Xiaomi | Rel-18 | Revision of S2-2305187r00. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#7 | - | - | Docs:=6 | - | |
| 9.12.2 | S2-2305150 | CR | Approval | 23.501 CR4506 (Rel-18, 'B'): Update about the Packet Delay Variation description and add PDV in QoS monitoring parameters | China moible, Samsung | Rel-18 | r02 agreed. Revised to S2-2306199. | Lei(Tencent) rapporteur proposes to take this paper as baseline 501 CR for KI#7. Paul (Ericsson) provides r01. Dan(China Mobile) ask. Paul (Ericsson) replies to Dan. Dario (Qualcomm) comments. Dan (China Mobile) OK with Paul's explanation. Dan (China Mobile) OK with r01 Saubhagya (Nokia) comments Dan (China Mobile) provide r02 based on Nokia comment ==== Revisions Deadline ==== Dario (Qualcomm): the cover page needs to be fixed (CN box needs to be ticked, no 502/503 associated CRs, etc). Dan (China Mobile) Thanks and I will fix the cover page for r02 Paul (Ericsson) can accept r01 and r02 ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306199 | CR | Approval | 23.501 CR4506R1 (Rel-18, 'B'): Update about the Packet Delay Variation description and add PDV in QoS monitoring parameters | China moible, Samsung | Rel-18 | Revision of S2-2305150r02. Approved | Agreed | |
| 9.12.2 | S2-2305045 | CR | Approval | 23.502 CR3729R2 (Rel-18, 'B'): AF Session procedure update to support 5GS Packet Delay Variation monitoring | Samsung, Tencent, Tencent Cloud | Rel-18 | Revision of S2-2302583 from S2#155. r02 agreed. Revised to S2-2306200. | Lei(Tencent) rapporteur proposes to take this paper as baseline 502 CR for KI#7. Saubhagya (Nokia) asks for clarification. Jaehyeon (Samsung) replies to Saubhagya (Nokia) and provides r01. Saubhagya (Nokia) asks to synchronize the text Jaehyeon (Samsung) replies to Saubhagya (Nokia) and provides r02. ==== Revisions Deadline ==== Paul (Ericsson) can accept r02, object to r01 and any other. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306200 | CR | Approval | 23.502 CR3729R3 (Rel-18, 'B'): AF Session procedure update to support 5GS Packet Delay Variation monitoring | Samsung, Tencent, Tencent Cloud | Rel-18 | Revision of S2-2305045r02. Approved | Agreed | |
| 9.12.2 | S2-2304168 | CR | Approval | 23.503 CR0955 (Rel-18, 'B'): Policy control support for Packet Delay Variation monitoring and reporting | Ericsson | Rel-18 | Approved | Lei(Tencent) rapporteur proposes to take this paper as baseline 503 CR for KI#7. Saubhagya (Nokia) provides r01. Provided comments/Questions Dan(China Mobile) would like to ask the question and whether we can remove the PDV related description in 503 Xiaowan Ke (vivo) comments the PDV should be one QoS Monitoring parameter from AF to PCF. Saubhagya (Nokia) responds to Xiaowan Ke (vivo) on PDV reporting event Paul (Ericsson) replies to Dan and provides technical justification for keeping the description of PDV in 23.503. Lei(Tencent) supports the CR and asks to co-sign. Saubhagya (Nokia) Supports keeping PDV reporting as a separate event and asks to co-sign jaehyeon (Samsung) supports the keeping the description of PDV in 23.503 and asks to co-sign. Dan (China Mobile) OK to keep the description of PDV in 503. ==== Revisions Deadline ==== Paul (Ericsson) can only accept r00 and objects to r01. Dan (China Mobile) OK to go with r00. ==== Comments Deadline ==== | Agreed |
| 9.12.2 | S2-2305262 | CR | Approval | 23.503 CR0975R2 (Rel-18, 'C'): Correction on Jitter and Alignment with PDV | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2305251. Approved | Lei(Tencent) rapporteur propose to handle this CR separately. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.12.2 | - | - | - | KI#8 general | - | - | Docs:=12 | - | |
| 9.12.2 | S2-2305317 | DISCUSSION | Agreement | Jitter for QoS flow with multiple SDFs | InterDigital Inc. | Rel-18 | Noted | Hui(Huawei) proposes to note this discussion paper which was marked as 'for agreement' Mike (InterDigital) agrees that this can be NOTED. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304479 | CR | Approval | 23.501 CR4322 (Rel-18, 'B'): EN resolving for KI#8 Except TSCAC and clarifications on AF inputs | Tencent, Tencent Cloud | Rel-18 | r08 agreed. Revised to S2-2306201. | Mike (InterDigital) provides comments Lei (Tencent) rapporteur propose to take this paper as baseline for KI#8 501 CR not including periodicity information transmission to SMF. Also provide response to Mike(InterDigital) Lei (Tencent) provides r01. Dario (Qualcomm) comments and provides r02. Hui (Huawei) comments and provides r03. Xiaowan Ke(vivo) provides r04 Lei(Tencent) provides comments Georgios Gkellas (Nokia, Nokia Shanghai-Bell) provides r05 Lei(Tencent) in general ok with r05 and make some editorial changes in r06. Dario (Qualcomm) provides r07. Lei(Tencent) is ok with r07. Xiaowan Ke(vivo) comments Lei(Tencent) replied to Xiaowan Ke(vivo) and provide r08 to fix the typo. ==== Revisions Deadline ==== Dario (Qualcomm) supports r08 Lei(Tencent) is also fine to go with r08. Hui(Huawei) prefer to r08, can accept r03-r07. Object to other versions.. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) is OK with r08 ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306201 | CR | Approval | 23.501 CR4322R1 (Rel-18, 'B'): EN resolving for KI#8 Except TSCAC and clarifications on AF inputs | Tencent, Tencent Cloud, Huawei, HiSilicon | Rel-18 | Revision of S2-2304479r08. Approved | Agreed | |
| 9.12.2 | S2-2304627 | CR | Approval | 23.501 CR4363 (Rel-19, 'F'): End of Data Burst reporting to the NG-RAN | CATT | Rel-19 | CR Cover sheet error! Should be a Rel-18 CR. Noted | Mike (InterDigital) asks questions and comments that individual handling (i.e. not merging) seems more appropriate for this paper. Boren (OPPO) asks question. Chunshan(CATT) supports this paper to be handled standalone and provides clarifications to Boren (OPPO) and Mike (InterDigital). Lei (Tencent) provides comments to Mike(InterDigital) and also fine to handle this paper separately. Boren (OPPO) replies to Chunshan(CATT). Chunshan(CATT) provides clarifications to Boren (OPPO). Chunshan (CATT) replies to Boren (OPPO). Boren (OPPO) replies to Chunshan (CATT). Mukesh (MediaTek) has concerns over dummy EoDB indication and seeks clarification. Jari (NTT DOCOMO) comments Chunshan(CATT) replies to Mukesh (MediaTek). Chunshan(CATT) replies to Jari (NTT DOCOMO) . Chunshan(CATT) replies to Jari (NTT DOCOMO). Dario (Qualcomm) comments. Chunshan(CATT) comments. Paul (Ericsson) provides comments. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) disagrees with a timer in UPF Chunshan(CATT) provides r01. ==== Revisions Deadline ==== Dario (Qualcomm) objects to any version of this paper. Mukesh (MediaTek) proposes to note this CR. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) objects to any revision of the CR including r00. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304851 | CR | Approval | 23.501 CR4418 (Rel-18, 'B'): Clarification of Data Burst in relation ot a PDU set. | Lenovo | Rel-18 | CR Cover sheet error! Postponed | Mike (InterDigital) comments that individual handling (i.e. not merging) seems more appropriate for this paper. Lei (Tencent) rapporteur propose to handle this paper separately as it is not related to EN resolving. Hui (Huawei) comments. Chunshan(CATT) comments. ==== Revisions Deadline ==== Hui (Huawei) proposes to postpone this paper. ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2305318 | CR | Approval | 23.501 CR4549 (Rel-18, 'C'): Jitter Reports for QoS flow with multiple SDFs | InterDigital Inc. | Rel-18 | Postponed | Lei (Tencent) rapporteur propose to handle this paper separately. Mukesh (MediaTek) seeks to understand why the calculation of jitter information is based on SDF. Youngkyo(Samsung) proposes to note it. Dario (Qualcomm) comments. Chunshan(CATT) comments. Paul (Ericsson) provides comments. Mike (InterDigital) replies. Mukesh (MediaTek) responds to Mike (InterDigital) Mike (InterDigital) replies and provides r01 Youngkyo(Samsung) comments. Youngkyo(Samsung) questions benefit of the proposal. Dario (Qualcomm) replies to Mike. Paul (Ericsson) asks question for clarification and provides comments. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) does not agree with this concept. Nokia needs at least time to think about it. We cannot accept it in this meeting ==== Revisions Deadline ==== Dario (Qualcomm) proposes to postpone this paper. Hui (Huawei) proposes to postpone this paper. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) proposes to postpone, too; objects to agree it Mike (InterDigital) comments and is ok to POSTPONE. ==== Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2304299 | CR | Approval | 23.502 CR3989 (Rel-18, 'B'): Procedure to acquire jitter information | MediaTek Inc. | Rel-18 | CR Cover sheet error! CC#4: r03 + changes agreed. Revised to S2-2306244, merging S2-2304390. r03? For CC#4 | Lei (Tencent) rapporteur propose to take this paper as baseline for KI#8 502. Please be noted that this 502 CR also need to reflect periodicity information transmission to SMF if any impacts in 502 is needed and agreed Dario (Qualcomm) assumes that, in light of CC#1 SoH results, now 5223 is the new baseline. Hui (Huawei) clarify this should be baseline of 23.502. Mukesh (MediaTek) provides r01. Dario (Qualcomm) replies Hui (Huawei) provides comments on r01. Mukesh (MediaTek) provides r02. Kenichi (KDDI) merge 4390 into this paper. ==== Revisions Deadline ==== Dario (Qualcomm) is fine w/ r02. Kenichi (KDDI) missing to indicate r03 in the e-mail. R03 was uploaded before the revision deadline to merge 4390 into this paper (r03). Hui (Huawei) supports r02 and r03, objects r00-r01. Paul (Ericsson) objects to this CR in all revisions. Mukesh (MediaTek): To be discussed in CC#4 ==== Comments Deadline ==== Lei(Tencent) agrees with Mukesh that need to be discussed in CC#4. Strongly hope people have objection also provide a potential agreeable version before CC#4. Paul (Ericsson) replies. Dan (China Mobile) provide r04=r03+update 4.4.2.2 with removing 'for a PDR', correct the reference, and removing'and indicate the corresponding PDR rule ID'. Mukesh (MediaTek) provides r05= r03 + update clause 4.4.2.2 step 10 by replacing: 'PDR' by 'QoS Flow'; 'and indicate the corresponding PDR rule ID' by 'for this QoS Flow' + correct 5.37.5.2 with 5.37.8.2 across all changes | Revised |
| 9.12.2 | S2-2306244 | CR | Approval | 23.502 CR3989R1 (Rel-18, 'B'): Procedure to acquire jitter information | MediaTek, KDDI, Futurewei, China Mobile, Tencent, Huawei | Rel-18 | Revision of S2-2304299r03 + changes, merging S2-2304390. Approved | Agreed | |
| 9.12.2 | S2-2304390 | CR | Approval | 23.502 CR4000 (Rel-18, 'B'): Periodicity information provisioning for PCF | KDDI, Futurewei, China Mobile, Tencent | Rel-18 | Merged into S2-2306244 Merge into S2-2304299? | Lei (Tencent) rapporteur propose to merge this paper into S2-2304299. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304725 | CR | Approval | 23.503 CR0995 (Rel-18, 'B'): Periodicity measurement and reporting for power saving | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306202. | Mike (InterDigital) asks a question Lei (Tencent) rapporteur propose to take this paper as baseline for KI#8 503 CR. Hui (Huawei) replies to Mike (InterDigital) asks a question Mike (InterDigital) replies to Hui (Huawei) and provides r01 Hui (Huawei) fine with r01 Jari (NTT DOCOMO) comments Xiaowan Ke(vivo) provides r02 Dario (Qualcomm) provides r03. Paul (Ericsson) provides comments. Boren (OPPO) provides comments. Xiaowan Ke(vivo) provides comments ==== Revisions Deadline ==== Dario (Qualcomm) prefers r03. Hui(Huawei) proposes to go with r03 Hui (Huawei) replies to Jari Boren (OPPO) is OK with r03. Xiaowan Ke(vivo) is OK with r03 ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2306202 | CR | Approval | 23.503 CR0995R1 (Rel-18, 'B'): Periodicity measurement and reporting for power saving | Huawei, HiSilicon, vivo | Rel-18 | Revision of S2-2304725r03. Approved | Agreed | |
| 9.12.2 | S2-2304881 | CR | Approval | 23.501 CR4425 (Rel-18, 'B'): Clarification on the TSCAI for the XR service | ZTE | Rel-18 | Postponed | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Zhendong (ZTE) provides r01. Dan (China Mobile) do not agree with r01, suggest to merge this paper into 5223. Xiaowan(vivo) share the view with Dan (China Mobile) to note this paper since it is not aligned with the way forward. Zhendong (ZTE) provides response. Lei(Tencent) provides comments Dario (Qualcomm) shares the view that this CR is not needed. Paul (Ericsson) asks question for clarification. Zhendong (ZTE) , mark this CR as postpone. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.12.2 | - | - | - | KI#8-Method of transfer periodicity from AF to SMF | - | - | Docs:=11 | - | |
| 9.12.2 | S2-2304396 | DISCUSSION | Agreement | Discussion on how to provide the traffic characteristics in KI#8 | vivo | Rel-18 | Noted | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. ==== Revisions Deadline ==== Hui (Huawei) proposes to note this discussion paper since it's for 'agreement'. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2304880 | DISCUSSION | Agreement | Discussion and proposal on the TSCAC for the KI#8 | ZTE | Rel-18 | Noted | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. ==== Revisions Deadline ==== Hui (Huawei) proposes to note this discussion paper since it's for 'agreement'. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2305196 | DISCUSSION | Discussion | Discussion for the KI#8 about how to transfer the periodicity from AF to SMF | China Mobile | Rel-18 | Noted | Noted | |
| 9.12.2 | S2-2304174 | CR | Approval | 23.501 CR4223 (Rel-18, 'B'): Introduction of traffic characteristics for TSC and XRM, N6 Jitter measurement EN resolution and clarifications | Ericsson | Rel-18 | Merged into S2-2306203 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dan (China Mobile) suggest to merge this paper into 5223. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304398 | CR | Approval | 23.501 CR4297 (Rel-18, 'B'): How provide traffic characteristics (Alt2) in KI#8 | vivo | Rel-18 | Merged into S2-2306203 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dan (China Mobile) suggest to merge this paper into 5223. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304399 | CR | Approval | 23.501 CR4298 (Rel-18, 'B'): How traffic characteristics are provided (Alt3) | vivo | Rel-18 | Merged into S2-2306203 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dan (China Mobile) suggest to merge this paper into 5223. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305223 | CR | Approval | 23.501 CR4529 (Rel-18, 'B'): PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8 | China moible | Rel-18 | r05 agreed. Revised to S2-2306203, merging S2-2305255, S2-2305232, S2-2304399, S2-2304398 and S2-2304174 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dario (Qualcomm) comments and provides r02 (please ignore r01). Dan(China Mobile) generally agree with r02. Lei(Tencent) comments that EN on UPF reporting to SMF is already in 4479 as baseline 501 CR. Also, we also need to update 5.27.2 accordingly. Provide r03. Jari (NTT DOCOMO) comments Dan(China Mobile) support r02, and agree that we should not touch TSC related clause. Lei(Tencent) is not ok with r02 due to duplicated changes with another CR, provide r04 without changes in TSC related clause. Georgios Gkellas (Nokia, Nokia Shanghai-Bell): No changes in 5.27.2 Dario (Qualcomm) provides r05 based on r04. Dan(China Mobile) ok with r04 and r05, prefer r05. ==== Revisions Deadline ==== Hui(Huawei) ok with r04 and r05, prefer r05. Jaehyeon (Samsung) ok with r04 and r05, prefer r05. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) prefers r05 Dario (Qualcomm) prefers r05 ==== Comments Deadline ==== Lei(Tencent) is fine with r05 and asks to co-sign the CR. | Revised |
| 9.12.2 | S2-2306203 | CR | Approval | 23.501 CR4529R1 (Rel-18, 'B'): PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8 | China moible | Rel-18 | Revision of S2-2305223r05, merging S2-2305255, S2-2305232, S2-2304399, S2-2304398, S2-2304174 and S2-2304723. Approved | Agreed | |
| 9.12.2 | S2-2305255 | CR | Approval | 23.501 CR4539 (Rel-18, 'B'): Enhancements to support power savings for XR services via the introduction of traffic assistance service | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2306203 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dan (China Mobile) suggest to merge this paper into 5223. Georgios Gkellas (Nokia, Nokia Shanghai-Bell) agrees to merge 5255 to 5223 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2305232 | CR | Approval | 23.501 CR4532 (Rel-18, 'B'): KI#8: Addressing open issues for power savings based on CDRX optimization | Qualcomm Incorporated | Rel-18 | Merged into S2-2306203 | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dan (China Mobile) suggest to merge this paper into 5223. Dario (Qualcomm) is ok with merging this into 5223. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | S2-2304723 | CR | Approval | 23.501 CR4385 (Rel-18, 'B'): Periodicity measurement and reporting for power saving | Huawei, HiSilicon | Rel-18 | Merged into S2-2306203 Merge into S2-2306203? | Lei (Tencent) rapporteur propose to handle this paper together with TSCAC related papers. Dario (Qualcomm) proposes to focus the discussion on 5223. Lei (Tencent) confirms that Dario's suggestion is correct. Suggest to mark this one as merged to 5223. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.12.2 | - | - | - | New SST | - | - | Docs:=1 | - | |
| 9.12.2 | S2-2305132 | CR | Approval | 23.501 CR4493 (Rel-18, 'B'): Introduction of a new standard SST for XRM | ZTE, China Mobile, Huawei, KDDI | Rel-18 | CC#4: Postponed r06?. +. Fix coversheet. For CC#4 | Dan(China Mobile) suggest to take this paper as baseline to discuss the slice related proposal . Chris Joul (T-Mobile USA) Cannot agree to the baseline version of this CR and provides comments. Curt (Meta) +1: agrees with Chris (T-Mobile USA). Jinguo(ZTE) provides r01 Dario (Qualcomm) comments and provides r02 Dan(China Mobile) provide r03 based on r01 and r02 Hui(Huawei) provide r04 Mengzhen (China Telecom) provides r05. Jinguo(ZTE) is ok with r05. Curt (Meta) provides r06. Ellen (Google) agrees with Chris (T-Mobile USA) that new SST type for XRM services cause confusion Jinguo(ZTE) replies to Ellen(Google) and is ok with r06 Lei(Tencent) is ok with r06 in general and plus minor editorial change and can co-sign the CR. Hui (Huawei) fine with r06. ==== Revisions Deadline ==== Hugh (AT&T) agrees with Chris (T-Mobile USA) and Ellen (Google) and is concerned about starting a precedence to define a new SST type for each individual services. Jinguo(ZTE) suggests to approve r06 Hugh(AT&T) still have concerns for 06 Chris Joul (TMUS) Can only accept r06 Dario (Qualcomm) supports approving r06. Cover page needs to be fixed (remove 5.37.5.1). Curt (Meta) okay with r06 or postpone the decision till next meeting - given the concerns from ATT and Google. Jinguo(ZTE) suggests to approve r06 with clean up the oversheet. Dan (China Mobile) supports r06. Mengzhen (China Telecom) is ok with r06 with clean up the oversheet. Ellen (Google) kindly objects to r00-r06 and proposes to postpone the decision till the next meeting. Dan (China Mobile) request to handle this paper for CC#4 Dan (China Mobile) clarify that the SST discussion already captured in XRM WID SP-221326, and request maybe Ellen to reconsider the value of this new SST Jinguo(ZTE) could not understand the reason of objection, and request to discuss at CC#4 Xinpeng(Huawei) proposes to agree r06. Mengzhen(China Telecom) support to go forward with r06. ==== Comments Deadline ==== | Postponed |
| 9.12.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=63 | - | |
| 9.12.2 | S2-2305258 | CR | Approval | 23.503 CR1031 (Rel-18, 'B'): Media Information to 5G System for trade-off of QoE and power saving requirements | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305320 | CR | Approval | 23.503 CR1037 (Rel-18, 'C'): Adding a Maximum UL PDB and a Maximum DL PDB to the RT latency requirement | InterDigital Inc. | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305195 | CR | Approval | 23.501 CR4521 (Rel-18, 'F'): General corrections for XRM related clause | China moible,Tencent | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305181 | CR | Approval | 23.502 CR4120 (Rel-18, 'C'): Procedures update to support policy control enhancements for multi-modal flows | Xiaomi | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305322 | CR | Approval | 23.501 CR4551 (Rel-18, 'C'): Update so that the URSP Enforcement Report can include an FQDN | InterDigital Inc. | Rel-18 | Check Affected Clauses! | NOT HANDLED | |
| 9.12.2 | S2-2305323 | CR | Approval | 23.503 CR1038 (Rel-18, 'C'): Update so that the URSP Enforcement Report can include an FQDN | InterDigital Inc. | Rel-18 | Check Affected Clauses! | NOT HANDLED | |
| 9.12.2 | S2-2305324 | CR | Approval | 23.502 CR4146 (Rel-18, 'C'): Update so that the URSP Enforcement Report can include an FQDN | InterDigital Inc. | Rel-18 | Check Affected Clauses! | NOT HANDLED | |
| 9.12.2 | S2-2304169 | CR | Approval | 23.502 CR3974 (Rel-18, 'B'): Signalling procedures to support policy control enhancements for multi-modal services | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304166 | CR | Approval | 23.503 CR0954 (Rel-18, 'B'): Policy Control for L4S support | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304171 | CR | Approval | 23.501 CR4222 (Rel-18, 'C'): Network exposure support for XR services and QoS Monitoring Policy | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304172 | CR | Approval | 23.502 CR3975 (Rel-18, 'B'): AF can subscribe new XRM measurements of QoS parameters that PCF derives using QoS Monitoring | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304170 | CR | Approval | 23.501 CR4221 (Rel-18, 'B'): Support for PDU Set Information | Ericsson | Rel-18 | Dario (Qualcomm) has issues with this CR. | NOT HANDLED | |
| 9.12.2 | S2-2304296 | CR | Approval | 23.501 CR4264 (Rel-18, 'B'): Updates to L4S ECN marking | MediaTek | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304393 | CR | Approval | 23.502 CR4001 (Rel-18, 'B'): QoS monitoring enhancement and UP based reporting | vivo, Lenovo, Tencent, Tencent Cloud | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.12.2 | S2-2304607 | CR | Approval | 23.501 CR4359 (Rel-18, 'C'): Resolve the EN on ECN marking for L4S during UE mobility. | OPPO | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304626 | CR | Approval | 23.502 CR3781R2 (Rel-18, 'B'): Support Requested Averaging Window from AF | CATT | Rel-18 | Revision of S2-2302232 from S2#155 | NOT HANDLED | |
| 9.12.2 | S2-2304718 | CR | Approval | 23.501 CR4382 (Rel-18, 'B'): Resolve ENs on 5GS Information Exposure | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304760 | CR | Approval | 23.501 CR4400 (Rel-18, 'C'): Correction on Network exposure for XR service | Samsung | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304948 | CR | Approval | 23.501 CR4441 (Rel-18, 'B'): Fix ENs in ECN marking for L4S | vivo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305149 | CR | Approval | 23.501 CR4505 (Rel-18, 'C'): Update for UPF function and ECN marking for L4S for XR services | Tencent, Tencent Cloud | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305151 | CR | Approval | 23.501 CR4507 (Rel-18, 'F'): Resolving the EN of KI#3 in clause 5.37.3.1, 5.37.4 and 5.45.5 | China moible | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305152 | CR | Approval | 23.502 CR4114 (Rel-18, 'F'): Policy enhancement for ECN marking for L4S | China moible | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305159 | CR | Approval | 23.502 CR4116 (Rel-18, 'B'): Update QoS monitoring procedure via the Control Plane Path | CATT | Rel-18 | Source modified on 4/7/2023. Original source : CATT | NOT HANDLED | |
| 9.12.2 | S2-2305182 | CR | Approval | 23.501 CR4517 (Rel-18, 'C'): The Update of Network Exposure to Support XR and Interactive Media Services | Xiaomi, Tencent, Tencent Cloud | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305183 | CR | Approval | 23.503 CR1025 (Rel-18, 'C'): The Update of Network Exposure to Support XR and Interactive Media Services | Xiaomi, Tencent, Tencent Cloud | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305202 | CR | Approval | 23.501 CR4523 (Rel-18, 'C'): API based exposure of congestion level information | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305203 | CR | Approval | 23.502 CR4128 (Rel-18, 'F'): Enhancement of QoS monitoring | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305204 | CR | Approval | 23.502 CR4129 (Rel-18, 'F'): 23.502_Policy enhancement for ECN marking for L4S | lenovo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305213 | CR | Approval | 23.501 CR4526 (Rel-18, 'C'): Providing option for L4S congestion handle in the case of UE mobility and/or non-homogeneous deployment scenarios when some nodes in the 5G network do not support L4S | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Revised to S2-2305376 | Revised | |
| 9.12.2 | S2-2305215 | CR | Approval | 23.503 CR0828R2 (Rel-18, 'B'): Update TS23.503 to reflect conclusion of KI#3 for XRM in TR23.700-60 with respect to API based exposure option | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2303131 from S2#155 | NOT HANDLED | |
| 9.12.2 | S2-2304290 | CR | Approval | 23.501 CR4263 (Rel-18, 'C'): PDU Set based QoS Handling requested by UE | OPPO | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304615 | CR | Approval | 23.501 CR4361 (Rel-18, 'C'): Resolve the EN on the definition of PSER | OPPO | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304628 | CR | Approval | 23.503 CR0896R1 (Rel-18, 'B'): Policy Control for PDU Set QoS Control | CATT | Rel-18 | Revision of S2-2302234 from S2#155 | NOT HANDLED | |
| 9.12.2 | S2-2304660 | CR | Approval | 23.501 CR4371 (Rel-18, 'B'): Resolving EN on PDU Set importance | China Telecom | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.12.2 | S2-2304720 | CR | Approval | 23.503 CR0993 (Rel-18, 'B'): Support of PDU Set handling | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304761 | CR | Approval | 23.501 CR4401 (Rel-18, 'C'): Correction on PDU Set QoS handling mechanism | Samsung | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305186 | CR | Approval | 23.501 CR4519 (Rel-18, 'C'): Remove the ENs about whether PDU Set Importance can span across QoS Flows | Xiaomi | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305217 | CR | Approval | 23.501 CR4528 (Rel-18, 'B'): Update TS23.501 for PDU Set Importance | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304167 | CR | Approval | 23.501 CR4220 (Rel-18, 'C'): Editors note on QoS monitoring for PDV | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304351 | CR | Approval | 23.501 CR4279 (Rel-18, 'F'): EN removal on KI#7 | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304353 | CR | Approval | 23.503 CR0965 (Rel-18, 'B'): 5GS Packet Delay Variation monitoring | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304466 | CR | Approval | 23.501 CR4320 (Rel-18, 'B'): EN Removing and Clarifications of PDV for KI#7 | Tencent, Tencent Cloud | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304477 | CR | Approval | 23.503 CR0975 (Rel-18, 'C'): Correction on Jitter and Alignment with PDV | Tencent, Tencent Cloud | Rel-18 | CR Cover sheet error! Revised to S2-2305251 | Revised | |
| 9.12.2 | S2-2305251 | CR | Approval | 23.503 CR0975R1 (Rel-18, 'C'): Correction on Jitter and Alignment with PDV | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2304477. CR Cover sheet error! Revised to S2-2305262 | Revised | |
| 9.12.2 | S2-2305027 | CR | Approval | 23.501 CR4463 (Rel-18, 'B'): Updates to 5GS Packet Delay Variation monitoring and reporting | Samsung | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304298 | CR | Approval | 23.501 CR4266 (Rel-18, 'B'): Jitter information to enhance power saving | MediaTek | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304397 | CR | Approval | 23.501 CR4296 (Rel-18, 'B'): How provide traffic characteristics (Alt1) in KI#8 | vivo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304400 | CR | Approval | 23.501 CR4299 (Rel-18, 'B'): KI#8: Aspects except for TSCAC | vivo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304401 | CR | Approval | 23.502 CR4002 (Rel-18, 'B'): KI#8: Power Saving Related Aspects | vivo | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.12.2 | S2-2304402 | CR | Approval | 23.503 CR0968 (Rel-18, 'B'): KI#8: Power Saving Related Aspects | vivo | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304501 | CR | Approval | 23.501 CR4331 (Rel-18, 'B'): EN resolving on TSCAC for KI#8 - Option 1: Separate parameter from container | Tencent, Tencent Cloud | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304502 | CR | Approval | 23.501 CR4332 (Rel-18, 'B'): EN resolving on TSCAC for KI#8 - Option 2: Generalizing TSCAC for XRM and TSN | Tencent, Tencent Cloud | Rel-18 | CR Cover sheet error! Revised to S2-2305253 | Revised | |
| 9.12.2 | S2-2305253 | CR | Approval | 23.501 CR4332R1 (Rel-18, 'B'): EN resolving on TSCAC for KI#8 - Option 2: Generalizing TSCAC for XRM and TSN | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2304502 | NOT HANDLED | |
| 9.12.2 | S2-2304503 | CR | Approval | 23.501 CR4333 (Rel-18, 'B'): EN resolving on TSCAC for KI#8 - Option 3: Introduce Separate Container for XRM | Tencent, Tencent Cloud | Rel-18 | CR Cover sheet error! Revised to S2-2305259 | Revised | |
| 9.12.2 | S2-2305259 | CR | Approval | 23.501 CR4333R1 (Rel-18, 'B'): EN resolving on TSCAC for KI#8 - Option 3: Introduce a new container for XRM | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2304503 | NOT HANDLED | |
| 9.12.2 | S2-2304724 | CR | Approval | 23.502 CR4063 (Rel-18, 'B'): Periodicity measurement and reporting for power saving | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304882 | CR | Approval | 23.501 CR4426 (Rel-18, 'F'): Clarification on EN on the TSCAC and Periodicity report. | ZTE | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2304883 | CR | Approval | 23.502 CR4082 (Rel-18, 'F'): Clarification on the N6 jitter measurement and Periodicity | ZTE | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.12.2 | S2-2304884 | CR | Approval | 23.503 CR1008 (Rel-18, 'F'): Clarification on TSCAC and N6 jitter measurement | ZTE | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305233 | CR | Approval | 23.502 CR4132 (Rel-18, 'B'): KI#8: Enhancements to power savings based on CDRX optimization | Qualcomm Incorporated | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305256 | CR | Approval | 23.502 CR4136 (Rel-18, 'B'): Traffic Assistance Container and N6 Jitter reporting support | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305257 | CR | Approval | 23.503 CR1030 (Rel-18, 'B'): Traffic Assistance Container for providing Periodicity information | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.12.2 | S2-2305273 | CR | Approval | 23.501 CR4540 (Rel-18, 'B'): Enhancements to support power savings for XR services via reusing the TSCAC | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.13.1 | - | - | - | Study on RedCap Phase 2 (FS_RedCAP_Ph2) | - | - | Docs:=0 | - | |
| 9.13.2 | - | - | - | RedCap Phase 2 (NR_RedCAP_Ph2) | - | - | Docs:=28 | - | |
| 9.13.2 | - | - | - | Paging Policy Information for Network Triggered Connection Resume | - | - | Docs:=8 | - | |
| 9.13.2 | S2-2303936 | LS In | Action | LS on Paging Policy Information for Network Triggered Connection Resume | CT WG4 (C4-230533) | Rel-18 | Responses drafted in S2-2304088, S2-2304188, S2-2304277, S2-2304438. Final response in S2-2305617 | Replied to | |
| 9.13.2 | S2-2304186 | CR | Approval | 23.502 CR3976 (Rel-18, 'C'): Paging differentiation support for network triggered resume | Ericsson | Rel-18 | Merged into S2-2305618 Merge into S2-2304437 | Qian (Ericsson) proposes to merge this paper into 4437 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2304188 | LS OUT | Approval | [DRAFT] Reply LS on Paging Policy Information for Network Triggered Connection Resume | Ericsson | Rel-18 | Response to S2-2303936. r04 agreed. Revised to S2-2305617, merging S2-2304438 and S2-2304277 Use as base | Steve (Huawei) comments on contents Qian (Ericsson) comments and provide r01 Saso (Intel) provides r02 Steve (Huawei) provides r03 Miguel (Qualcomm) provides r04 ==== Revisions Deadline ==== Qian (Ericsson) propose to go with r04 Saso (Intel) is OK with r04 Steve (Huawei) is ok with r04 ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305617 | LS OUT | Approval | Reply LS on Paging Policy Information for Network Triggered Connection Resume | SA WG2 | Rel-18 | Revision of S2-2304188r04, merging S2-2304438 and S2-2304277. Approved | Approved | |
| 9.13.2 | S2-2304437 | CR | Approval | 23.502 CR4007 (Rel-18, 'B'): Support of Paging Policy Differentiation for CN based MT communication handling | Huawei, HiSilicon | Rel-18 | r07 agreed. Revised to S2-2305618, merging S2-2304186 Use as base for PPD | Qian (Ericsson) provides comments and r01 Lars (Sony) ask a question Steve (Huawei) comments. Qian (Ericsson) provides comments. Lars (Sony) responds to Steve and Qian. Saso (Intel) comments. Saso (Intel) provides r02 Qian (Ericsson) provides comments and r03 Saso (Intel) provides r04 Lars (Sony) provides r05 Qian (Ericsson) provides info. Saso (Intel) provides r06. Lars (Sony) provides info. Steve (Huawei) comments, provides r07 ==== Revisions Deadline ==== Qian (Ericsson) supports to go with r07 Lars (Sony) supports to go with r07 Saso (Intel) is OK with r07; will also provide a draft revision of the complementary CR in 4000 to fix duplicate text. Steve (Huawei) is ok with r07. ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305618 | CR | Approval | 23.502 CR4007R1 (Rel-18, 'B'): Support of Paging Policy Diffentiation for CN based MT communication handling | Huawei, HiSilicon, Ericsson, Intel | Rel-18 | Revision of S2-2304437r07, merging S2-2304186. Approved | Agreed | |
| 9.13.2 | S2-2304438 | LS OUT | Approval | [DRAFT] LS Reply on Paging Policy Information for Network Triggered Connection Resume | Huawei, HiSilicon | Rel-18 | Response to S2-2303936. Merged into S2-2305617 Merge into S2-2304188 | Qian (Ericsson) proposes to merge this paper into 4186 Qian (Ericsson) corrects that this paper is proposed to merge into 4188 Steve (Huawei) comments on merge, sending 1 LSout in this topic makes sense. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2304277 | LS OUT | Approval | [DRAFT] Reply LS on Paging Policy Information for Network Triggered Connection Resume INACTIVE | Intel | Rel-18 | Response to S2-2303936. Merged into S2-2305617 Merge into S2-2304188 | Qian (Ericsson) proposes to merge this paper into 4188 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | - | - | - | RRC_INACTIVE eDRX above 10.24s and SDT | - | - | Docs:=9 | - | |
| 9.13.2 | S2-2303947 | LS In | Action | LS from RAN WG2: LS on INACTIVE eDRX above 10.24sec and SDT | RAN WG2 (R2-2302082) | Rel-18 | Responses drafted in S2-2304088, S2-2304187, S2-2304275. Final response in S2-2305619 | Replied to | |
| 9.13.2 | S2-2304187 | LS OUT | Approval | [DRAFT] Reply LS on INACTIVE eDRX above 10.24s and SDT | Ericsson | Rel-18 | Response to S2-2303947. Merged into S2-2305619 Merge into S2-2304275 | Qian (Ericsson) proposes to merge this paper into 4275 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2304275 | LS OUT | Approval | [DRAFT] Reply LS on INACTIVE eDRX above 10.24sec and SDT | Intel | Rel-18 | Response to S2-2303947. r03 agreed. Revised to S2-2305619, merging S2-2304187 Use as base For SDT | Qian (Ericsson) provides comments and r01 Saso (Intel) provides r02 Steve (Huawei) provides r03 Saso (Intel) is OK with r03 ==== Revisions Deadline ==== Qian (Ericsson) supports r03 ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305619 | LS OUT | Approval | Reply LS on INACTIVE eDRX above 10.24sec and SDT | SA WG2 | Rel-18 | Revision of S2-2304275r03, merging S2-2304187. Approved | Approved | |
| 9.13.2 | S2-2303999 | DISCUSSION | Agreement | Co-existence of SDT and CN buffering in RRC_Inactive state | Intel | Rel-18 | Noted | Noted | |
| 9.13.2 | S2-2304000 | CR | Approval | 23.502 CR3944 (Rel-18, 'C'): Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE | Intel, Qualcomm Inc. | Rel-18 | CR Cover sheet error! r06 agreed. Revised to S2-2305620. PPD part is covered in S2-2304437 | Qian (Ericsson) provides comments and r01 Lars (Sony) provides r02 Steve (Huawei) comments. Lars (Sony) comments. Saso (Intel) comments on the removal of the proposed ENs. Lars (Sony) responds to Saso. Qian (Ericsson) provides comments. Saso (Intel) replies to Lars, Qian. Qian (Ericsson) replies to Saso. Saso (Intel) replies to Qian. Qian (Ericsson) provides further comments. Qian (Ericsson) comments. Lars (Sony) comments to Qian (Ericsson). Qian (Ericsson) comments to Lars (Sony). Saso (Intel) replies to Lars and Qian. Seeks confirmation for a common understanding. Hannu (Nokia) supports the interpretation given by Lars and Saso. Qian (Ericsson) provides further info. Jinguo(ZTE) provides comment Lars (Sony) provides comments Saso (Intel) replies to Jinguo. Further question to Qian. Jinguo(ZTE) provides further comment. Qian (Ericsson) replies to Saso (Intel). Lars (Sony) ask if second change is merged into 4437? Saso (Intel) provides r03 Miguel (Qualcomm) provides r04 Saso (Intel) replies to Miguel Lars (Sony) clarify to Miguel Miguel (Qualcomm) understands, but then we probably should link this CR with 4437 in Cover Sheet under Other Comments. Saso (Intel) provides r05. Steve (Huawei) provides r06 ==== Revisions Deadline ==== Qian (Ericsson) is ok with r06. But there may be some text duplication. Lars (Sony) is ok with r06. In the 'other comments' field it is stated the relation to CR4007 and the overlapping text is the same in both CRs. Saso (Intel) is ok with r06 + undoing of change in clause 4.8.2.2b step 2 (to avoid duplicated change with complementary CR in 4437r07). Steve (Huawei) is ok with r06 + change (aka r07) Miguel (Qualcomm) ok with Saso's proposal: r06 + undoing of change in clause 4.8.2.2b step 2 (to avoid duplicated change with complementary CR in 4437r07). ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305620 | CR | Approval | 23.502 CR3944R1 (Rel-18, 'C'): Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE | Intel, Qualcomm Inc. | Rel-18 | Revision of S2-2304000r06. Approved | Agreed | |
| 9.13.2 | S2-2304155 | CR | Approval | 23.501 CR4218 (Rel-18, 'C'): Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE | Intel, Qualcomm Inc. | Rel-18 | r01 agreed. Revised to S2-2305621. | Qian (Ericsson) provides comments and r01 ==== Revisions Deadline ==== Qian (Ericsson) propose to go with r01 Lars (Sony)is fine with r01 Saso (Intel)is OK with r01 Steve (Huawei) is ok with r01. ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305621 | CR | Approval | 23.501 CR4218R1 (Rel-18, 'C'): Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE | Intel, Qualcomm Inc. | Rel-18 | Revision of S2-2304155r01. Approved | Agreed | |
| 9.13.2 | - | - | - | MT communication capability | - | - | Docs:=8 | - | |
| 9.13.2 | S2-2304184 | CR | Approval | 23.501 CR4230 (Rel-18, 'F'): CN based MT communication capability | Ericsson | Rel-18 | r00 agreed. Revised to S2-2305622. CC#4: Merged into S2-2305625 Merge into S2-2305138 | Qian (Ericsson) proposes to merge this paper into 5138 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2305622 | CR | Approval | 23.501 CR4230R1 (Rel-18, 'F'): CN based MT communication capability | Ericsson | Rel-18 | Revision of S2-2304184r00. CC#4: WITHDRAWN | Withdrawn | |
| 9.13.2 | S2-2304364 | CR | Approval | 23.501 CR4285 (Rel-18, 'F'): AMF support of CN to handle mobile terminated (MT) communication when UE is in RRC-Inactive state. | Sony | Rel-18 | r00 agreed. Revised to S2-2305623. CC#4: Merged into S2-2305625 Merge into S2-2305138 | Qian (Ericsson) proposes to merge this paper into 5138 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2305623 | CR | Approval | 23.501 CR4285R1 (Rel-18, 'F'): AMF support of CN to handle mobile terminated (MT) communication when UE is in RRC-Inactive state. | Sony | Rel-18 | Revision of S2-2304364r00. CC#4: WITHDRAWN | Withdrawn | |
| 9.13.2 | S2-2304436 | CR | Approval | 23.501 CR4308 (Rel-18, 'B'): CN based MT communication capability negotiation | Huawei, HiSilicon | Rel-18 | r00 agreed. Revised to S2-2305624. CC#4: Merged into S2-2305625 Merge into S2-2305138 | Qian (Ericsson) proposes to merge this paper into 5138 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.13.2 | S2-2305624 | CR | Approval | 23.501 CR4308R1 (Rel-18, 'B'): CN based MT communication capability negotiation | Huawei, HiSilicon | Rel-18 | Revision of S2-2304436r00. Approved. CC#4: WITHDRAWN | Withdrawn | |
| 9.13.2 | S2-2305138 | CR | Approval | 23.501 CR4499 (Rel-18, 'F'): CN based MT communication capability | ZTE, Nokia, Nokia Shanghai Bell | Rel-18 | r07 agreed. Revised to S2-2305625, merging S2-2304184, S2-2304436 and S2-2304364. Use as base | Lars (Sony) provides r01 Steve (Huawei) comments. Jinguo(ZTE) replies to Steve and Lars, and provide r02 Qian (Ericsson) comments and provides r03 Jinguo(ZTE) replies to Steve (Huawei) Hannu (Nokia) proposes to re-use HLcom via as clean reference as possible (=without unjustified additions). Lars (Sony) comments. Hannu (Nokia) provides r04 and explains. Hannu (Nokia) answers to Lars on NOTE 1 after uploading r04. Jinguo(ZTE) replies. Hannu (Nokia) replies to Jinguo. Lars (Sony) provides r05. Qian (Ericsson) provides comments related to the NOTE. Lars (Sony) responds to Jinguo(ZTE). Jinguo(ZTE) replies to Lars (Sony) . Qian (Ericsson) provides further clarification. Qian (Ericsson) provides comments and r06. Hannu (Nokia) can also live with r05 Hannu (Nokia) prefers r05 as it's cleaner with less notes. Jinguo(ZTE) is fine with both r05 and r06 Miguel (Qualcomm) cannot accept any revision that removes the NG RAN sending the indication to CN when it receives DL NAS message, i.e. up r06 so far. Jinguo(ZTE) replies to Muguel that the DL NAS message handling is captured in 502 Qian (Ericsson) provides comment. Miguel (Qualcomm) provides r07 Lars (Sony) Responds to Miguel Miguel (Qualcomm) responds to Lars ==== Revisions Deadline ==== Qian (Ericsson) is ok with either r07 or r06 Jinguo(ZTE) is ok with either r07 or r06 Lars (Sony) is ok with r07, but the cover page need update to remove the part that RAN sends indication after receiving DL data. Steve (Huawei) objects to r06, can live with r07 Jinguo(ZTE) ok will update the coverpage Lars (Sony) It is ok to agree r07 + update the cover sheet to remove 'But if DL data is received for the UE, then the NG-RAN should inform the AMF that the UE is in eDRX, either immediately or delayed e.g. until MT data or signalling is received for the UE.' Miguel (Qualcomm) agrees with Lars proposal Hannu (Nokia) supports r07 with the suggested cover page update. ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305625 | CR | Approval | 23.501 CR4499R1 (Rel-18, 'F'): CN based MT communication capability | ZTE, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2305138r07, merging S2-2304184, S2-2304436 and S2-2304364. Approved | Agreed | |
| 9.13.2 | - | - | - | Others | - | - | Docs:=3 | - | |
| 9.13.2 | S2-2304185 | CR | Approval | 23.501 CR4231 (Rel-18, 'F'): N2 release handling for RRC_INACTIVE | Ericsson | Rel-18 | r02 agreed. Revised to S2-2305626. | Lars (Sony) provides r01 Steve (Huawei) comments. Qian (Ericsson) provides comments. Lars (Sony) responds to Qian Qian (Ericsson) provides further comments Lars (Sony) provides further comments Qian (Ericsson) comments further Lars (Sony) provides r02 Hannu (Nokia) supports r02 Miguel (Qualcomm) provides r03 ==== Revisions Deadline ==== Qian (Ericsson) propose to go with r03 Lars (Sony) propose to go with r02 Qian (Ericsson) considers it's ok to go with r02 as well + change 'and have' to 'has' Lars (Sony) supporting the additional change to r02 as suggested by Qian (Ericsson) Miguel (Qualcomm) ok with Qian's proposal (approve r02 + change 'and have' to 'has') Hannu (Nokia) also supports Qian's proposal to approve r02 with editorial update. ==== Comments Deadline ==== | Revised |
| 9.13.2 | S2-2305626 | CR | Approval | 23.501 CR4231R1 (Rel-18, 'F'): N2 release handling for RRC_INACTIVE | Ericsson | Rel-18 | Revision of S2-2304185r02. Approved | Agreed | |
| 9.13.2 | S2-2303954 | LS In | Action | LS from RAN WG3: Reply LS on long eDRX support for RRC_INACTIVE | RAN WG3 (R3-230803) | Rel-18 | Noted | Qian (Ericsson) proposes to NOTE this paper | Noted |
| 9.14.1 | - | - | - | Study on evolution of IMS multimedia telephony service (FS_NG_RTC) | - | - | Docs:=0 | - | |
| 9.14.2 | - | - | - | Evolution of IMS multimedia telephony service (NG_RTC) | - | - | Docs:=53 | - | |
| 9.14.2 | - | - | - | General issues | - | - | Docs:=1 | - | |
| 9.14.2 | S2-2303966 | LS In | Action | LS from SA WG1: Reply LS on PS Data Off for IMS Data Channel Service | SA WG1 (S1-230590) | Rel-19 | Noted | Leo (Deutsche Telekom) proposes to NOTE the LS, as there is no action for SA2 in Rel-18. Rainer (Nokia) is ok to note the LS. | Noted |
| 9.14.2 | - | - | - | KI#1 | - | - | Docs:=33 | - | |
| 9.14.2 | S2-2304008 | CR | Approval | 23.228 CR1278 (Rel-18, 'C'): Clarification on IMS Data Channel Service | Ericsson | Rel-18 | r09 agreed. Revised to S2-2306054, merging S2-2304971 | Yi (China Mobile) ask questions for clarification. Rainer (Nokia) asks for clarification. George (Ericsson) provides comments George Foti (Ericsson) provides r01. Removed third party registration. Now the good file Yi (China Mobile) procides r02. Mu (Huawei) provides r03 Rainer (Nokia) provides r04 George (Ericsson) provides comments r05 George Foti (Ericsson) provides r6 Rainer (Nokia) comments Mu (Huawei) provide the correct link Rainer (Nokia) provides r07 Rainer (Nokia) replies Mu (Huawei) provide r08, adding repository data back. George (Ericsson) provides r09. I made it an example. HSS is already stated as optional. So I don't really understand the issue. And precisely repository data is an implementation thing so all what U have is already there. Removing this will mean that stage 3 will have to standardize it completely opposite to our objective. We agree with U. Rainer (Nokia) ok with r08 George (Ericsson) That has always been the case from the original ?? Rainer (Nokia) got it Rainer (Nokia) is ok with r09. ==== Revisions Deadline ==== Yi (China Mobile) accpets r09. Yi (China Mobile) please add China Mobile in source when yo submit since 4791 is merged into this one. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306054 | CR | Approval | 23.228 CR1278R1 (Rel-18, 'C'): Clarification on IMS Data Channel Service | Ericsson | Rel-18 | Revision of S2-2304008r09, merging S2-2304971. Approved | Agreed | |
| 9.14.2 | S2-2304971 | CR | Approval | 23.228 CR1304 (Rel-18, 'B'): Removal of editor s note on DC service profile | China Mobile | Rel-18 | Merged into S2-2306054 | George Foti (Ericsson) provides comments. Merge into Ericsson CR 4008 Chris Joul (TMUS) agrees that CR in Tdoc 4008 should be baseline Kenny (Qualcomm) provides comments, and proposed to merge into Ericsson CR 4008 Yi (China Mobile) we need to discuss the way forward before merging the contributions. Mu (Huawei) propose to use 4971 as way forward Rainer (Nokia) comments. George (Ericsson) provides comments Rainer (Nokia) replies. George (Ericsson) provides response Chris Joul (TMUS) provides comments Yi (China Mobile) replies and provides r01. ==== Revisions Deadline ==== George Foti (Ericsson) This is Merged in 4008. Rainer (Nokia) agrees to merge into 4008 Yi (China Mobile) is ok to merge into 4008. ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2304087 | CR | Approval | 23.228 CR1290 (Rel-18, 'C'): Data Channel service profile | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Yi (China Mobile) ask questions for clarification. George Foti (Ericsson) objects to this CR Hao (ZTE) comments. Yi (China Mobile) share the same concern with George. Rainer (Nokia) provides r01 Mu (Huawei) comments Rainer (Nokia) replies ==== Revisions Deadline ==== George Foti (Ericsson) proposes o postpone this CR. Rainer (Nokia) ok to postpone ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304972 | CR | Approval | 23.228 CR1305 (Rel-18, 'B'): Reference point between HSS and DCSF | China Mobile | Rel-18 | r01 agreed. Revised to S2-2306055. | George Foti (Ericsson) provides comments Kenny (Qualcomm) provides comments Chunhui (Xiaomi) provides comments and suggests a NOTE. Rainer (Nokia) comments. Mu (Huawei) comments Rainer (Nokia) replies. Yi (China Mobile) replies. Chris Joul (TMUS) Agrees with Rainer and provides comments Yi (China Mobile) replies to Chris. George (Ericsson) provides comments Yi (China Mobile) provides r01. ==== Revisions Deadline ==== George Foti (Ericsson) accepts r01 Rainer (Nokia) ok with r01 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306055 | CR | Approval | 23.228 CR1305R1 (Rel-18, 'B'): Reference point between HSS and DCSF | China Mobile | Rel-18 | Revision of S2-2304972r01. Approved | Agreed | |
| 9.14.2 | S2-2304009 | CR | Approval | 23.228 CR1279 (Rel-18, 'F'): IMS DC Session setup Clarification | Ericsson | Rel-18 | Merged into S2-2306056 | Rainer (Nokia) proposes to mark this as merged into 4083r01. Rainer (Nokia) replies George (Ericsson) responds. These 2 don't collide. So they progress independently. I don't see the issue. Nothing overrides anything. They just happen to delete the same EN. That's OK. ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2304988 | CR | Approval | 23.228 CR1310 (Rel-18, 'B'): Trigger and Control of DC Media Negotiation | Huawei, HiSilicon, CMCC | Rel-18 | Noted | George Foti (Ericsson) provides comments Kenny (Qualcomm) provides comments Mu (Huawei) replies and provide r01 George (Ericsson) provides comments Rainer (Nokia) comments Yi (China Mobile) comments. ==== Revisions Deadline ==== George Foti (Ericsson) objects to all revisions and original Rainer (Nokia) proposes to note and use 4083r01. Rainer (Nokia) replies Yi (China Mobile) support go with r01. ==== Comments Deadline ==== | Noted |
| 9.14.2 | S2-2304083 | CR | Approval | 23.228 CR1286 (Rel-18, 'C'): UE trigger for IMS Data Channel setup | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2306056, merging S2-2304009 | Yi (China Mobile) comments. George Foti (Ericsson) provides comments Mu (Huawei) asks for clarification Rainer (Nokia) provides r01 Mu (Huawei) propose to merge this into 4988 ==== Revisions Deadline ==== George Foti (Ericsson) accepts r01 Yi (China Mobile) is ok with r01. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306056 | CR | Approval | 23.228 CR1286R1 (Rel-18, 'C'): UE trigger for IMS Data Channel setup | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304083r01, merging S2-2304009. Approved | Agreed | |
| 9.14.2 | S2-2304011 | CR | Approval | 23.228 CR1281 (Rel-18, 'C'): Update to IMS AS SBA Services | Ericsson | Rel-18 | Approved | Yi (China Mobile) comments. George (Ericsson) provides comments Rainer (Nokia) asks for clarification George (Ericsson) provides response ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.14.2 | S2-2304574 | CR | Approval | 23.228 CR1292 (Rel-18, 'B'): KI#1_Provide stream id to DCSF | vivo | Rel-18 | r03 agreed. Revised to S2-2306057. | George Foti (Ericsson) Not OK with this CR. Please see Ericsson CR 4011 Yi (China Mobile) ask question. James Jin (vivo) replies to questions from George Foti (Ericsson) and Yi (China Mobile). Kenny (Qualcomm) provides comments. Yi (China Mobile) replies to James. Mu (Huawei) comments James Jin (vivo) replies to questions from Kenny (Qualcomm),Yi (China Mobile) and Mu (Huawei) Mu (Huawei) makes a proposal George (Ericsson) provides a response James Jin (vivo) replies to questions from Mu (Huawei) and George Foti (Ericsson) Rainer (Nokia) comments. George (Ericsson) provides comments James Jin (vivo) provide r01 and replies to Rainer (Nokia) and George Foti (Ericsson) James Jin (vivo) provide r02 and replies to George Foti (Ericsson) Rainer (Nokia) asks for clarification James Jin (vivo) replies to Rainer (Nokia) Rainer (Nokia) provides r03 ==== Revisions Deadline ==== George Foti (Ericsson) while r03 is OK. It has a linguistic mistake. These attributes needs to be replaced with this attribute, It is only one. James Jin (vivo) replies. Rainer (Nokia) ok with r03 Yi (China Mobile) is ok with r03. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306057 | CR | Approval | 23.228 CR1292R1 (Rel-18, 'B'): Provide stream id to DCSF | Vivo | Rel-18 | Revision of S2-2304574r03. Approved | Agreed | |
| 9.14.2 | S2-2304012 | CR | Approval | 23.228 CR1282 (Rel-18, 'F'): Update to DCMF services | Ericsson | Rel-18 | Postponed | Chris Joul (TMUS) Cannot agree to this CR at this meeting and proposes postponing discussion. Chris Joul (TMUS) withdraws disagreement, IE discussion and revision should occur at this meeting Mu (Huawei) comments. Propose to change the MF name to UMF (Unified Media Function) George (Ericsson) provides comments Mu (Huawei) provide r01, change the name to UMF (Unified Media Function). ==== Revisions Deadline ==== George Foti (Ericsson) not OK with r01. It introduces terminology changes and other things not agreed to. Mu (Huawei) accept r01, or r00 + change all ASF to DCSF. Rainer (Nokia) cannot accept r00. ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304970 | CR | Approval | 23.228 CR1303 (Rel-18, 'B'): Update of DCMF service to support media processing | China Mobile | Rel-18 | Postponed | George Foti (Ericsson) is not OK with this CR. Chris Joul (TMUS) Cannot agree to this CR at this meeting and proposes postponing discussion. Rainer (Nokia) has similar concerns as E/// and TMO US, proposes to postpone. Yi (China Mobile) replies. George (Ericsson) provides comments Chris Joul (TMUS) withdraws disagreement, IE discussion and revision should occur at this meeting ==== Revisions Deadline ==== George Foti (Ericsson) proposes to postpone the CR ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304987 | CR | Approval | 23.228 CR1309 (Rel-18, 'B'): Update of DCMF service to support media processing | Huawei, HiSilicon | Rel-18 | Postponed | George Foti (Ericsson) This can merge in Ericsson CR 4012 if needed. Chris Joul (TMUS) Cannot agree to this CR at this meeting and proposes postponing discussion. Mu (Huawei) replies to Chris Chris Joul (TMUS) withdraws disagreement, IE discussion and revision should occur at this meeting ==== Revisions Deadline ==== George Foti (Ericsson) proposes to postpone this CR ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304968 | CR | Approval | 23.228 CR1301 (Rel-18, 'B'): Update of Bootstrap and application data channel setup procedures | China Mobile, Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306058, merging S2-2304940 | George Foti (Ericsson) provides r01 Yi (China Mobile) comments. Hao (ZTE) provides r02 which merges part of changes in S2-2304940. George (Ericsson) provides response Rainer (Nokia) comments Yi (China Mobile) provides r03. ==== Revisions Deadline ==== George Foti (Ericsson) accepts r03 Rainer (Nokia) ok with r03 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306058 | CR | Approval | 23.228 CR1301R1 (Rel-18, 'B'): Update of Bootstrap and application data channel setup procedures | China Mobile, Huawei, HiSilicon, ZTE | Rel-18 | Revision of S2-2304968r03, merging S2-2304940. Approved | Agreed | |
| 9.14.2 | S2-2304084 | CR | Approval | 23.228 CR1287 (Rel-18, 'C'): Establishing data channel before 200 OK | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2306059. | George Foti (Ericsson) provides comments Mu (Huawei) ask for clarification and propose to merge into 4986 Rainer (Nokia) replies. George (Ericsson) provides response Mu (Huawei) propose to merge this into 4968 George (Ericsson) provides comments George (Ericsson) provides response. Yes, otherwise no one will notice that. It is the IMS-AGW. It should be understood by stage 3 Rainer (Nokia) provides r01. ==== Revisions Deadline ==== George Foti (Ericsson) OK with r01 Yi (China Mobile) propose to mark this as merged into 4968 based on comments. Yi (China Mobile) is ok with the proposal. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306059 | CR | Approval | 23.228 CR1287R1 (Rel-18, 'C'): Establishing data channel before 200 OK | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304084r01. Approved | Agreed | |
| 9.14.2 | S2-2304940 | CR | Approval | 23.228 CR1296 (Rel-18, 'F'): Bootstrap Data Channel Set up Signalling Procedure Update | ZTE | Rel-18 | Merged into S2-2306058 | Yi (China Mobile) propose to merge this doc into 4968. Hao (ZTE) is fine to merge this CR into S2-2304968. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2304085 | CR | Approval | 23.228 CR1288 (Rel-18, 'C'): Relationship between P2A2P and P2A/A2P procedures | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2306060, merging S2-2304943 | Rainer (Nokia) provides r01 Hao (ZTE) comments. James Jin (vivo) provides comments. Rainer (Nokia) replies ==== Revisions Deadline ==== George Foti (Ericsson) accepts r01 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306060 | CR | Approval | 23.228 CR1288R1 (Rel-18, 'C'): Relationship between P2A2P and P2A/A2P procedures | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304085r01, merging S2-2304943. Approved | Agreed | |
| 9.14.2 | S2-2304943 | CR | Approval | 23.228 CR1299 (Rel-18, 'F'): Modification of P2A2P Procedure | ZTE | Rel-18 | Merged into S2-2306060 | George Foti (Ericsson) Merge in Nokia CR 4085 George Foti (Ericsson) Please merge in Nokia CR 4085 Hao (ZTE) responds and proposes to use this paper as baseline for P2A2P procedure modification. Yi (China Mobile) comments. Hao (ZTE) comments. Rainer (Nokia) comments, cannot accept 4943 as is. Hao (ZTE) responds. Hao (ZTE) provides r01 based on comments received. George (Ericsson) prefers 4085. Hao (ZTE) proposes to go with 4943. ==== Revisions Deadline ==== George Foti (Ericsson) This is merged in 4085. Rainer (Nokia) agrees to mark this as merged into 4085 ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2304974 | CR | Approval | 23.502 CR3906R1 (Rel-18, 'B'): Enhancements to NRF services to support DCMF discovery and selection | China Mobile | Rel-18 | Revision of S2-2302639 from S2#155. r01 agreed. Revised to S2-2306061. | Yi (China Mobile) provides r01 to align with 4975. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306061 | CR | Approval | 23.502 CR3906R2 (Rel-18, 'B'): Enhancements to NRF services to support DCMF discovery and selection | China Mobile | Rel-18 | Revision of S2-2304974r01. Approved | Agreed | |
| 9.14.2 | S2-2304975 | CR | Approval | 23.228 CR1307 (Rel-18, 'B'): DCMF service registration and discovery | China Mobile | Rel-18 | CR Cover sheet error! r03 agreed. Revised to S2-2306062. | Hao (ZTE) provides r01. George Foti (Ericsson) Not OK with this CR. George (Ericsson) provides comments. This revision did not address my comments. Rainer (Nokia) comments Hao (ZTE) responds. Yi (China Mobile) replies. George (Ericsson) provides comments. The P-CSCF has to be out of the picture. Rainer (Nokia) provides r02 Yi (China Mobile) provides r03 by adding a editor's note on IP address. Rainer (Nokia) replies George (Ericsson) Yes. ==== Revisions Deadline ==== George Foti (Ericsson) OK with r01 George Foti (Ericsson) we can accept r03 PLUS replacing the existing EN with this new one: Editor's Note: Usage of IP address and IP address ranges is FFS George Foti (Ericsson) we can accept r03 PLUS replacing the existing EN with this new one: Editor's Note: Usage of IP address and IP address ranges is FFS Rainer (Nokia) is ok to approve r03 and change the EN. Yi (China Mobile) is ok with the proposal. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306062 | CR | Approval | 23.228 CR1307R1 (Rel-18, 'C'): DCMF service registration and discovery | China Mobile, ZTE | Rel-18 | Revision of S2-2304975r03. Approved | Agreed | |
| 9.14.2 | S2-2304010 | CR | Approval | 23.228 CR1280 (Rel-18, 'C'): Support for Application Signalling Function | Ericsson | Rel-18 | Postponed | Mu (Huawei) propose to note 4010 George (Ericsson) provides response Mu (Huawei) explains the difference between 4010 and 5060, and propose to forward with 5060. Mu (Huawei) replies George (Ericsson) provides comments Mu (Huawei) further replies Kenny (Qualcomm) provides comments Mu (Huawei) comments Mu (Huawei) replies that DCMF and DCSF are two separate entity. George (Ericsson) Lets do that at this meeting. Rainer (Nokia) comments, does not accept changing the architecture at this stage. George (Ericsson) provides r01. I just kept MF and removed ASF. George (Ericsson) provides additional comments Mu (Huawei) replies to Rainer Mu (Huawei) provides r02, change the MF name to UMF. Rainer (Nokia) replies Mu (Huawei) explains the logic of UMF Yi (China Mobile) comments. Mu (Huawei) propose to separate the two issue. George (Ericsson) The we have to update the DC1 and DCMF services next time. They don't follow 3GPP rules. ==== Revisions Deadline ==== George Foti (Ericsson) accepts r0 or r01 ONLY Mu (Huawei) only accept r01 and r02 Rainer (Nokia) does not accept r01 or any other version including original. Mu (Huawei) propose to approve r01 as we agreed to use MF in other email thread. Rainer (Nokia) still prefers to postpone. George (Ericsson) provides answers. ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304641 | CR | Approval | 23.228 CR1295 (Rel-18, 'C'): Further update on the usage of DC App-ID | Qualcomm Incorporated | Rel-18 | r02 agreed. Revised to S2-2306063. | George Foti (Ericsson) provides comments Kenny (Qualcomm) replies George Foti (Ericsson) comments and provides r01. Yi (China Mobile) propose to remove the last two changes. Kenny (Qualcomm) replies Yi (China Mobile) comments. Rainer (Nokia) comments Kenny (Qualcomm) replies Rainer (Nokia) comments and provides r02 ==== Revisions Deadline ==== George Foti (Ericsson) OK with r02 Rainer (Nokia) ok with r02 ==== Comments Deadline ==== Kenny (Qualcomm) proposed comment for editor's aware for the harmonization with 4085r01. | Revised |
| 9.14.2 | S2-2306063 | CR | Approval | 23.228 CR1295R1 (Rel-18, 'C'): Further update on the usage of DC App-ID | Qualcomm Incorporated | Rel-18 | Revision of S2-2304641r02. Approved | Agreed | |
| 9.14.2 | S2-2304576 | CR | Approval | 23.228 CR1294 (Rel-18, 'B'): KI#1_Provide application list based on UE DC capabilities | vivo | Rel-18 | r01 agreed. Revised to S2-2306064. | Rainer (Nokia) comments James Jin (vivo) provide r01 and replies to Rainer (Nokia) Rainer (Nokia) is ok with r01 ==== Revisions Deadline ==== George Foti (Ericsson) OK with r01 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306064 | CR | Approval | 23.228 CR1294R1 (Rel-18, 'B'): Provide application list based on UE DC capabilities | Vivo | Rel-18 | Revision of S2-2304576r01. Approved | Agreed | |
| 9.14.2 | - | - | - | KI#2 | - | - | Docs:=6 | - | |
| 9.14.2 | S2-2304013 | CR | Approval | 23.228 CR1283 (Rel-18, 'B'): Supporting Network Centric AR Telephony Communication | Ericsson | Rel-18 | Postponed | Mu (Huawei) provides r01 George (Ericsson) provides comments Mu (Huawei) replies to George Mu (Huawei) provides r02 ==== Revisions Deadline ==== George Foti (Ericsson) Ok with r02 Rainer (Nokia) proposes to postpone. Rainer (Nokia) comments George (Ericsson) responds. I did object to 4968r02 as it is headed in the wrong direction; mainly the architecture. The 4013/4014 is the architecture that Ericsson is willing to accept. That has not been carried over in 4968r02. Rainer (Nokia) replies Mu (Huawei) comment Mu (Huawei) is only OK with 4013r02 if it aligns the annex clause with 4014 r02. Reject other revision and original Mu (Huawei) propose the following: Approve 4013r02 + two changes of the title: 'XX.2.2 -> AC.X.2.2', 'XX.3.2 -> AC.x.3.2', and also update the figure label. George (Ericsson) That works as well. Rainer (Nokia) proposes to postpone 4013 Yi (China Mobile) ask if we can endorse r02. Mu (Huawei) support to endorse the 4013r02 with the proposed change. ==== Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2304014 | CR | Approval | 23.228 CR1284 (Rel-18, 'B'): Supporting UE centric AR Telephony Communication | Ericsson | Rel-18 | r02 agreed. Revised to S2-2306065, merging S2-2304986 and S2-2304944 | Rainer (Nokia) asks for clarification George (Ericsson) provides response Rainer (Nokia) replies George (Ericsson) provides r01 Mu (Huawei) comments Rainer (Nokia) provides r02 ==== Revisions Deadline ==== George Foti (Ericsson) OK with r02 Mu (Huawei) OK with r02 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306065 | CR | Approval | 23.228 CR1284R1 (Rel-18, 'B'): Supporting UE centric AR Telephony Communication | Ericsson | Rel-18 | Revision of S2-2304014r02, merging S2-2304986 and S2-2304944. Approved | Agreed | |
| 9.14.2 | S2-2304944 | CR | Approval | 23.228 CR1300 (Rel-18, 'B'): UE Rendering AR Communication Procedure | ZTE | Rel-18 | Merged into S2-2306065 | George Foti (Ericsson) This can be merged in Ericsson CR 4013 and 4014 Kenny (Qualcomm) provides comments Hao (ZTE) responds. Rainer (Nokia) comments ==== Revisions Deadline ==== Rainer (Nokia) proposes to mark as merged into 4014 ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2304986 | CR | Approval | 23.228 CR1308 (Rel-18, 'B'): Supporting AR Telephony Communication | Huawei, HiSilicon | Rel-18 | Merged into S2-2306065 | George Foti (Ericsson) Not Ok with this CR. Please see 2 Ericsson CRs 4013 and 4014. Mu (Huawei) replies and propose to merge 4013 and 4014 into 4986 George (Ericsson) provides response. Mu (Huawei) provides r01 Rainer (Nokia) asks for clarification George (Ericsson) provides comments Mu (Huawei) provides r02, merging 4013 and 4014. ==== Revisions Deadline ==== Yi (China Mobile) propose to agree 4986 from this meeting as the base of further work. Rainer (Nokia) can accept r02. George (Ericsson) Ericsson objects with r02. The architecture is incorrect. Yi (China Mobile) ask question to George. George (Ericsson) please check again Rainer (Nokia) comments Mu (Huawei) comments, isn't 4014r02 and 4013r02 use the same architecture? George (Ericsson) They do. But then why do we have 4986 as well. This created confusion. This has only MF. If folks are not happy with MF then we can call it ARMF. That's what it will be and we need 2 new reference points replacing MDC1, and DC2. We will not agree that DCMF can be enhanced to support ARMF. They are separate logical entities. The only way we can do that if we call this MF. We can then enhance MDC1, and DC2. Mu (Huawei) ask do we have consensus of using MF now? I am OK with both 4013r02 and 4014r02. George (Ericsson) The TR clearly had DCMF and ARMF as separate. There may be other media in the future so we cant call everything DCMF. We provided a simple definition of MF in 4010 that says it provides functional services such as DCMF and ARMF. There is no architectural change or anything, It is documentation issue. George (Ericsson) It will be a major step forward if we agree to 1404r02. We can build on that Rainer (Nokia) replies George (Ericsson) responds. ==== Comments Deadline ==== | Merged |
| 9.14.2 | S2-2305060 | CR | Approval | 23.228 CR1314 (Rel-18, 'B'): IMS AS Service | Huawei, HiSilicon | Rel-18 | Postponed | George Foti (Ericsson) We are not OK with this approach. We resolved this in CR 4011. Mu (Huawei) asks for clarification George (Ericsson) provides comments Mu (Huawei) replies Mu (Huawei) further replies George (Ericsson) provides response Mu (Huawei) comments, we have call flow, SA4 only responsible for media negotiation, AR need audio/video flow, this is very basic function and do not need SA4. It's all basic SDP that already supported in 24.229, please see 4986 for detail call flow. Rainer (Nokia) asks for clarification Mu (Huawei) answers James Jin (vivo) provides comments. ==== Revisions Deadline ==== George Foti (Ericsson) proposes to postpone this CR as it is addressed. Rainer (Nokia) ok to postpone ==== Comments Deadline ==== | Postponed |
| 9.14.2 | - | - | - | KI#4 | - | - | Docs:=4 | - | |
| 9.14.2 | S2-2304212 | CR | Approval | 23.228 CR1265R1 (Rel-18, 'B'): KI#4 Describe option to support MRF registration and discovery using NRF | T-Mobile USA INC | Rel-18 | Revision of S2-2302505 from S2#155. r02 agreed. Revised to S2-2306066. | George Foti (Ericsson) provides comments Chris Joul (TMUS) Replies to George's Questions Rainer (Nokia) comments. George (Ericsson) provides comments Rainer (Nokia) replies. George (Ericsson) provides response Chris Joul (TMUS) Provides comments. Chris Joul (TMUS) supplies r01 Rainer (Nokia) provides r02 Chris Joul (TMUS) Supplies r03 ==== Revisions Deadline ==== Chris Joul (TMUS) Suggests using R02 George Foti (Ericsson) Ok with r02 Rainer (Nokia) ok to go with r02 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306066 | CR | Approval | 23.228 CR1265R2 (Rel-18, 'B'): KI#4 Describe option to support MRF registration and discovery using NRF | T-Mobile USA INC | Rel-18 | Revision of S2-2304212r02. Approved | Agreed | |
| 9.14.2 | S2-2304213 | CR | Approval | 23.502 CR3895R1 (Rel-18, 'B'): KI4 Enhancements to NRF services to support IMS-MRF registration and discovery | T-Mobile USA INC | Rel-18 | Revision of S2-2302506 from S2#155. r01 agreed. Revised to S2-2306067. | George Foti (Ericsson) provides comments Yi (China Mobile) ask question. Rainer (Nokia) asks for clarification. Chris Joul (TMUS) supplies r01 ==== Revisions Deadline ==== George Foti (Ericsson) OK with r01 Yi (China Mobile) is ok with r01. Rainer (Nokia) ok with r01 ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2306067 | CR | Approval | 23.502 CR3895R2 (Rel-18, 'B'): KI4 Enhancements to NRF services to support IMS-MRF registration and discovery | T-Mobile USA INC | Rel-18 | Revision of S2-2304213r01. Approved | Agreed | |
| 9.14.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=9 | - | |
| 9.14.2 | S2-2304015 | CR | Approval | 23.228 CR1285 (Rel-18, 'B'): Support for IMS Data Channel Data Off exemption | Ericsson | Rel-18 | CR Cover sheet error! Revised to S2-2304568 | Revised | |
| 9.14.2 | S2-2304568 | CR | Approval | 23.228 CR1285R1 (Rel-18, 'B'): IMS Data Channel Data Off Exempt Service | Ericsson | Rel-18 | Revision of S2-2304015 | NOT HANDLED | |
| 9.14.2 | S2-2304969 | CR | Approval | 23.228 CR1302 (Rel-18, 'B'): Procedures on Data Channel termination and QoS requirement | China Mobile | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.14.2 | S2-2304941 | CR | Approval | 23.228 CR1297 (Rel-18, 'F'): Clarification on NF Service Registration and Discovery | ZTE | Rel-18 | NOT HANDLED | ||
| 9.14.2 | S2-2304211 | CR | Approval | 23.228 CR1291 (Rel-18, 'B'): KI#1 Clarification on IMS-AS usage and removal of EN | T-Mobile USA INC | Rel-18 | NOT HANDLED | ||
| 9.14.2 | S2-2304942 | CR | Approval | 23.228 CR1298 (Rel-18, 'F'): Clarification on Service Based Interfaces and Reference Points | ZTE | Rel-18 | NOT HANDLED | ||
| 9.14.2 | S2-2304086 | CR | Approval | 23.228 CR1289 (Rel-18, 'C'): Roaming support for IMS Data Channel service | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.14.2 | S2-2304973 | CR | Approval | 23.228 CR1306 (Rel-18, 'B'): Support IMS data channel in roaming case | China Mobile | Rel-18 | NOT HANDLED | ||
| 9.14.2 | S2-2304575 | CR | Approval | 23.228 CR1293 (Rel-18, 'B'): KI#1_Help DCSF to decide whether to anchor in DCMF/MRF in P2P scenario | vivo | Rel-18 | NOT HANDLED | ||
| 9.15.1 | - | - | - | Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) | - | - | Docs:=0 | - | |
| 9.15.2 | - | - | - | Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | - | - | Docs:=35 | - | |
| 9.15.2 | S2-2303914 | LS In | Action | LS from BBF: BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) | BBF (LIAISE-542-5G-RG-Hybrid-Access-Requirements-00) | Revision of postponed S2-2302174 from S2#155. Response drafted in S2-2304221. Final response in S2-2305428 | Replied to | ||
| 9.15.2 | S2-2304221 | LS OUT | Approval | [DRAFT] Reply LS on BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) | Qualcomm Incorporated | Response to S2-2303914. r00 agreed. Revised to S2-2305428. | Revised | ||
| 9.15.2 | S2-2305428 | LS OUT | Approval | Reply LS on BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) | SA WG2 | - | Revision of S2-2304221r00. Approved | Approved | |
| 9.15.2 | - | - | - | RSM | - | - | Docs:=12 | - | |
| 9.15.2 | S2-2304079 | CR | Approval | 23.501 CR4200 (Rel-18, 'F'): Clarifications to the Redundant Steering Mode | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Rainer (Nokia) provides r01. Yuxin (Xiaomi) comments. Dario (Qualcomm) asks question about NOTE 3. Rainer (Nokia) replies Rainer (Nokia) provides r02 Rainer (Nokia) is ok with r03 Yuxin (Xiaomi) provides r03 Guanzhou (InterDigital) comments and proposes to adopt the approach in 4557. Dario (Qualcomm) replies to Rainer. Guanzhou (InterDigital) provides r04. Rainer (Nokia) is ok with r03 or r04 depending whether 4557 is agreed Rainer (Nokia) replies to Dario. Yishan (Huawei) comments ==== Revisions Deadline ==== Dario (Qualcomm) prefers r04 and discuss the NOTE in 4557. Myungjune (LGE) is only accepts r02, r03. Tao(VC) Let's check r03 agreeable or not. Yuxin(Xiaomi) is ok with r03. Yishan (Huawei) is ok with r03 Guanzhou (InterDigital) can only accept r04 and objects to other versions. ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304222 | CR | Approval | 23.501 CR4245 (Rel-18, 'B'): Clarifications on ATSSS-LL functionality support with respect to Redundant Steering Mode and MPQUIC functionality | Qualcomm Incorporated | Rel-18 | Merged into S2-2304079 (noted) | Rainer (Nokia) proposes to merge 4222 into 4079. Dario (Qualcomm) is fine with Rainer's proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304497 | CR | Approval | 23.501 CR4330 (Rel-18, 'F'): Clarification on Redundant Steering Mode | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305467. | Stefan (Ericsson) provides r01 Rainer (Nokia) is ok with r01 Yishan (Huawei) is ok with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305467 | CR | Approval | 23.501 CR4330R1 (Rel-18, 'F'): Clarification on Redundant Steering Mode | Huawei, HiSilicon | Rel-18 | Revision of S2-2304497r01. Approved | Agreed | |
| 9.15.2 | S2-2304556 | CR | Approval | 23.501 CR4342 (Rel-18, 'F'): Clarification of RTT measurement for RSM | InterDigital | Rel-18 | Approved | Agreed | |
| 9.15.2 | S2-2304557 | CR | Approval | 23.501 CR4343 (Rel-18, 'F'): Additional information in PMF-Suspend Duplication Request message | InterDigital | Rel-18 | Noted | Yishan (Huawei) asks for clarification Rainer (Nokia) proposes to merge into 4079. Myungjune (LGE) comments Rainer (Nokia) replies. Stefan (Ericsson) comments Guanzhou (InterDigital) replied to comments and explains why the change is necessary. Yishan (Huawei) replies and asks for clarification Yishan (Huawei) replies to Rainer (Nokia) Guanzhou (InterDigital) provides further comments. Yuxin(Xiaomi) comments. Dario (Qualcomm) asks question for clarification. Rainer (Nokia) comments Yuxin (Xiaomi) comments Guanzhou (InterDigital) provides r01. Rainer (Nokia) is ok with r01 Guanzhou (InterDigital) responds to Rainer (Nokia) Dario (Qualcomm) comments on the 2nd part of NOTE 3. Guanzhou (InterDigital) responds to Dario (Qualcomm) Guanzhou (InterDigital) provides r02. Yuxin (Xiaomi) comments and provides r03. Rainer (Nokia) proposes rewording of the note Yishan (Huawei) comments Guanzhou (InterDigital) responds to Rainer and provides r03 Guanzhou (InterDigital) responds to Yishan (Huawei) Yuxin (Xiaomi) reminds Guanzhou (InterDigital) the wrong r03 link Rainer (Nokia) comments that r03 does not include the changed Note. Guanzhou (InterDigital) provides r04 and asks to ignore r03. Guanzhou (InterDigital) provides R05 Rainer (Nokia) provides r06 ==== Revisions Deadline ==== Myungjune (LGE) proposes to NOTE this CR. Dario (Qualcomm) prefers r02, can live w r06, but needs clarification. Guanzhou (InterDigital) responds to Myungjune and suggests to approve R06. Yishan (Huawei) propose to note this CR Myungjune (LGE) cannot accept any revision including original version. ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304558 | DISCUSSION | Agreement | Procedures for Suspend/Resume Traffic Duplication | InterDigital Inc. | Rel-18 | Noted | Noted | |
| 9.15.2 | S2-2304909 | CR | Approval | 23.502 CR4087 (Rel-18, 'B'): Clarifications on Network initiated service request procedure | China Telecom | Rel-18 | r04 agreed. Revised to S2-2305468. | Stefan (Ericsson) provides comments Rainer (Nokia) comments. Yubing (China Telecom) replies to Stefan (Ericsson) and Rainer (Nokia). Dario (Qualcomm) comments. Yubing (China Telecom) provides r01. Dario (Qualcomm) provides r02. Yubing (China Telecom) is ok with r02. Myungjune (LGE) comments Yubing (China Telecom) replies to Myungjune (LGE) Myungjune (LGE) replies to Yubing (China Telecom) Rainer (Nokia) agrees with Myungjune (LGE) Stefan (Ericsson) also supports to postpone Yubing (China Telecom) replies to Myungjune (LGE), Rainer (Nokia), and Stefan (Ericsson), Yishan (Huawei) provides comments and supports to address the issue in ATSSS first. Rainer (Nokia) replies Stefan (Ericsson) replies Yubing (China Telecom) replies to Rainer (Nokia), and Stefan (Ericsson) Rainer (Nokia) replies. Apostolis (Lenovo) supports Rainer's (Nokia) proposal for an EN. Yubing (China Telecom) replies and provides r04. Rainer (Nokia) is ok with r04 Stefan (Ericsson) ok with r04 ==== Revisions Deadline ==== Dario (Qualcomm) is OK w/ r04. Myungjune (LGE) is OK with r04. ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305468 | CR | Approval | 23.502 CR4087R1 (Rel-18, 'B'): Clarifications on Network initiated service request procedure | China Telecom | Rel-18 | Revision of S2-2304909r04. Approved | Agreed | |
| 9.15.2 | S2-2304910 | CR | Approval | 23.501 CR4431 (Rel-18, 'B'): Clarifications the Redundant Steering Mode for GBR SDF | China Telecom | Rel-18 | r02 agreed. Revised to S2-2305469. | Rainer (Nokia) comments. Myungjune (LGE) comments. Dario (Qualcomm) asks questions for clarification. Yubing (China Telecom) replies to Rainer (Nokia), Myungjune (LGE), Dario (Qualcomm). Rainer (Nokia) replies Myungjune (LGE) replies to Yubing (China Telecom) Yubing (China Telecom) replies to Myungjune (LGE) and Rainer (Nokia) Stefan (Ericsson) provides comments Yubing (China Telecom) responses to Rainer (Nokia), Stefan (Ericsson), Myungjune (LGE), and provides r01 Yishan (Huawei) asks for clarification Yubing (China Telecom) provides r02 Rainer (Nokia) is ok with r02 ==== Revisions Deadline ==== Stefan (Ericsson) is ok with r02 ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305469 | CR | Approval | 23.501 CR4431R1 (Rel-18, 'B'): Clarifications the Redundant Steering Mode for GBR SDF | China Telecom | Rel-18 | Revision of S2-2304910r02. Approved | Agreed | |
| 9.15.2 | S2-2304924 | CR | Approval | 23.501 CR4436 (Rel-18, 'F'): Redundant traffic steering clarification | Xiaomi | Rel-18 | Merged into S2-2304079 (noted) | Dario (Qualcomm) thinks that this should be merged into 4557 or 4079. Rainer (Nokia) agrees to merge into 4079 Yuxin (Xiaomi) agrees to merge 4924 into 4079 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.15.2 | - | - | - | Non-3GPP path switch | - | - | Docs:=12 | - | |
| 9.15.2 | S2-2304080 | CR | Approval | 23.501 CR4201 (Rel-18, 'C'): URSP rules for non-3GPP access path switching | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Dario (Qualcomm) asks questions for clarification. Rainer (Nokia) replies Marco (Huawei) see comment to 4082 ==== Revisions Deadline ==== Marco (Huawei) objects to r00 Myungjune (LGE) proposes to NOTE this CR. Stefan (Ericsson) proposes to NOTE ==== Comments Deadline ==== | Postponed |
| 9.15.2 | S2-2304081 | CR | Approval | 23.502 CR3960 (Rel-18, 'C'): URSP rules for non-3GPP access path switching | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Dario (Qualcomm): please see my comments for 4080. Marco (Huawei) see comment to 4082 ==== Revisions Deadline ==== Marco (Huawei) objects to r00 Myungjune (LGE) proposes to NOTE this CR. Stefan (Ericsson) proposes to NOTE ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304082 | CR | Approval | 23.503 CR0948 (Rel-18, 'C'): URSP rules for non-3GPP access path switching | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Yishan (Huawei) asks for clarification Rainer (Nokia) replies. Myungjune (LGE) comments Myungjune (LGE) replies to Rainer (Nokia) Stefan (Ericsson) provides comments Dario (Qualcomm) asks questions for clarification. Stefan (Ericsson) replies marco (Huawei) comments and express concern Stefan (Ericsson) also has concerns ==== Revisions Deadline ==== Marco (Huawei) objects to r00 Myungjune (LGE) proposes to NOTE this CR. Stefan (Ericsson) proposes to NOTE ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304106 | CR | Approval | 23.501 CR4210 (Rel-18, 'C'): Updates to non-3GPP access path switching | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2305470, merging S2-2304482 | Myungjune (LGE) provides r01. Yishan (Huawei) ask for clarifications Myungjune (LGE) provides r02. Rainer (Nokia) comments Marco (Huawei) provide r03 ==== Revisions Deadline ==== Marco (Huawei) prefers r03 . I can live with r02 Myungjune (LGE) ok with r02, r03 Rainer (Nokia) is ok with r03. Paul R (Charter) also is ok with r03. Omkar (CableLabs) is ok with r03. Stefan (Ericsson) prefers r00 but can live with r03 ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305470 | CR | Approval | 23.501 CR4210R1 (Rel-18, 'C'): Updates to non-3GPP access path switching | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304106r03, merging S2-2304482. Approved | Agreed | |
| 9.15.2 | S2-2304107 | CR | Approval | 23.502 CR3963 (Rel-18, 'C'): Updates to non-3GPP access path switching | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2305471. | Yishan (Huawei) asks for clarification Rainer (Nokia) replies. Myungjune (LGE) comments. Paul Russell (Charter) comments. Myungjune (LGE) replies to Rainer (Nokia). Paul R (Charter) replies to Rainer (Nokia). Myungjune (LGE) provides r01. Rainer (Nokia) replies to Paul (Charter) Stefan (Ericsson) replies Paul R (Charter) minor editorial update to Figure 4.22.9.5-1 Omkar (CableLabs) comments Stefan (Ericsson) provides r02 and r03 ==== Revisions Deadline ==== Myungjune (LGE) ok with r03, not ok with r02. Paul R (Charter) also ok with r03, not ok with r02. Rainer (Nokia) ok with r03 Omkar (CableLabs) also ok with r03, cannot accept r02. DongYeon (Samsung) supports r03, and not ok with r02. Stefan (Ericsson) ok with r03 ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305471 | CR | Approval | 23.502 CR3963R1 (Rel-18, 'C'): Updates to non-3GPP access path switching | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304107r03. Approved | Agreed | |
| 9.15.2 | S2-2304482 | CR | Approval | 23.501 CR4324 (Rel-18, 'F'): Clarification on support of N3GPP path switching on MA PDU session | Huawei, HiSilicon | Rel-18 | Merged into S2-2305470 | Dario (Qualcomm) asks questions for clarification. Yishan (Huawei) replies to Dario (Qualcomm) Rainer (Nokia) replies Stefan (Ericsson) comments Dario (Qualcomm) comments. Myungjune (LGE) replies to Stefan (Ericsson) Stefan (Ericsson) replies to Myungjune Paul R (Charter) comments on MM and SM capability exchange ==== Revisions Deadline ==== Myungjune (LGE) comments this CR should be merged into S2-2304106 or NOTED Stefan (Ericsson) agrees that it should be noted or merged into 4016 Rainer (Nokia) agrees to note Yishan (Huawei) is ok to merge the 4482 into 4106. ==== Comments Deadline ==== | Merged |
| 9.15.2 | S2-2304483 | CR | Approval | 23.502 CR4016 (Rel-18, 'B'): Update call flow of N3GPP path switching on MA PDU session | Huawei, HiSilicon | Rel-18 | Covered by S2-2304017 | Stefan (Ericsson) comments that this overlaps with 4017 Yishan (Huawei) is ok to merge 4483 into 4017 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.15.2 | S2-2304592 | CR | Approval | 23.502 CR4033 (Rel-18, 'F'): Clarification on old access release during non-3GPP switching | LG Electronics | Rel-18 | Approved | Agreed | |
| 9.15.2 | S2-2305270 | CR | Approval | 23.502 CR4138 (Rel-18, 'B'): Update SMF Service Operations for indication of non-3GPP path switching and Registration Management procedure to clarify that non-3GPP access path switching indication meaning for mobility registration | Charter Communications | Rel-18 | r03 agreed. Revised to S2-2305472. | Yishan (Huawei) provides comments Rainer (Nokia) comments Paul R (Charter) response to Yishan (Huawei) and Rainer (Nokia) Myungjune (LGE) comments Paul R (Charter) responding to LGE's comments Paul R (Charter) provides r01 Myungjune (LGE) provides r02. Paul R (Charter) replies Omkar (CableLabs) comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305472 | CR | Approval | 23.502 CR4138R1 (Rel-18, 'B'): Update SMF Service Operations for indication of non-3GPP path switching | Charter Communications, LG Electronics, CableLabs, Samsung | Rel-18 | Revision of S2-2305270r03. Approved | Agreed | |
| 9.15.2 | - | - | - | MPQUIC | - | - | Docs:=8 | - | |
| 9.15.2 | S2-2304922 | CR | Approval | 23.501 CR4435 (Rel-18, 'B'): MPQUIC related ATSSS capability update | Xiaomi | Rel-18 | Merged into S2-2305429 | Dario (Qualcomm) provides r01. Rainer (Nokia) proposes to merge with 5017 Dario (Qualcomm) comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.15.2 | S2-2304923 | CR | Approval | 23.503 CR1010 (Rel-18, 'B'): Support of MPQUIC Steering Mode | Xiaomi | Rel-18 | r05 agreed. Revised to S2-2305473, merging S2-2305021 | Rainer (Nokia) asks for clarification. Yuxin (Xiaomi) replies to Rainer (Nokia) Rainer (Nokia) replies Myungjune (LGE) comments Stefan (Ericsson) comments Yuxin (Xiaomi) provides r01 Rainer (Nokia) comments Yuxin (Xiaomi) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305473 | CR | Approval | 23.503 CR1010R1 (Rel-18, 'B'): Support of MPQUIC Steering Mode | Xiaomi, Lenovo, Apple, Broadcom, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304923r05, merging S2-2305021. Approved | Agreed | |
| 9.15.2 | S2-2305017 | CR | Approval | 23.501 CR4457 (Rel-18, 'B'): Determining the ATSSS capabilities of a MA PDU Session when the UE supports MPQUIC | Lenovo, Broadcom | Rel-18 | r04 agreed. Revised to S2-2305429, merging S2-2304922 | Dario (Qualcomm): this needs a revision to remove non standard text. Yuxin (Xiaomi) comments and suggests to merge this CR into 4922 Apostolis (Lenovo) notes that 5017 is already marked as 'approved'. We just need to make the editorial change suggested by Dario. Rainer (Nokia) is ok to use 5017 Yuxin (Xiaomi) is ok to use 5017 ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305429 | CR | Approval | 23.501 CR4457R1 (Rel-18, 'B'): Determining the ATSSS capabilities of a MA PDU Session when the UE supports MPQUIC | Lenovo, Broadcom, Xiaomi | Rel-18 | Revision of S2-2305017, merging S2-2304922. Approved | Agreed | |
| 9.15.2 | S2-2305019 | CR | Approval | 23.501 CR4459 (Rel-18, 'B'): Associating a QUIC connection with a QoS flow | Lenovo, Apple, Broadcom | Rel-18 | r02 agreed. Revised to S2-2305474. | Rainer (Nokia) provides r01. Yuxin (Xiaomi) provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.15.2 | S2-2305474 | CR | Approval | 23.501 CR4459R1 (Rel-18, 'B'): Associating a QUIC connection with a QoS flow | Lenovo, Apple, Broadcom, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305019r02. Approved | Agreed | |
| 9.15.2 | S2-2305021 | CR | Approval | 23.503 CR1016 (Rel-18, 'B'): Introduction of the MPQUIC Steering Functionality | Lenovo, Apple, Broadcom | Rel-18 | Merged into S2-2305473 | Dario (Qualcomm) asks questions for clarification and asks to update CR. Rainer (Nokia) 5021 be marked as merged into 4923? Apostolis (Lenovo) comments on merging 5021 into 4923. Rainer (Nokia) is ok with proposed way forward Yuxin (Xiaomi) merges this CR into 4923 based on the comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.16.1 | - | - | - | Study on UPF enhancement for Exposure And SBA (FS_UPEAS) | - | - | Docs:=0 | - | |
| 9.16.2 | - | - | - | UPF enhancement for Exposure And SBA (UPEAS) | - | - | Docs:=44 | - | |
| 9.16.2 | - | - | - | General | - | - | Docs:=4 | - | |
| 9.16.2 | S2-2303942 | LS In | Action | LS from CT WG4: LS on NF ID in Nupf_EventExposure_Subscribe Request | CT WG4 (C4-230727) | Rel-18 | Responses drafted in S2-2304834, S2-2304967. Final response in S2-2305757 | Replied to | |
| 9.16.2 | S2-2304834 | LS OUT | Approval | [DRAFT] LS reply on NF ID in Nupf_EventExposure_Subscribe Request | vivo | Response to S2-2303942. Merged into S2-2305757 Merge with S2-2304967? | Yan (China Mobile) suggests to merge this 4834 with 4967. Yoohwa(ETRI) agrees with Yan. Huazhang (vivo) agree to merge, thanks ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged | |
| 9.16.2 | S2-2304967 | LS OUT | Approval | [DRAFT] Reply LS on NF ID in Nupf_EventExposure_Subscribe Request | China Mobile | Rel-18 | Response to S2-2303942. r01 agreed. CC#4: r01 + changes agreed. Revised to S2-2305757, merging S2-2304834 Merge with S2-2304834? | Laurent (Nokia): provides r01 ==== Revisions Deadline ==== Yan (China Mobile) is ok with r01. ==== Comments Deadline ==== Yan (China Mobile) requests to align this LS with the latest conclusion in 4937 by deleting 'are only NWDAF and SMF which' on top of 4967r01. | Revised |
| 9.16.2 | S2-2305757 | LS OUT | Approval | Reply LS on NF ID in Nupf_EventExposure_Subscribe Request | SA WG2 | Rel-18 | Revision of S2-2304967r01 + changes, merging S2-2304834. CC#4: Approved | Approved | |
| 9.16.2 | - | - | - | CRs for 23.501 | - | - | Docs:=11 | - | |
| 9.16.2 | S2-2305126 | CR | Approval | 23.501 CR4490 (Rel-18, 'F'): Update the description of reporting suggestion information | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2305758. Baseline paper for clause 5.8.2.17 and 5.8.2.18. Affected Clauses: 5.8.2.17 | Changki(ETRI) provides r01 by merging S2-2304452 into S2-2305126r01 Yan (China Mobile) suggests the authors to provide the merging version by merging content from 4103, 4782, 4452, 4964. Changki(ETRI) provides S2-2305126r01 link again without file change Magnus (Ericsson) provides r02 Changki(ETRI) provides r03 with only cover sheet change including summary for second change from r02 . The cover sheet of the r02 seems to be broken. Fenqin (Huawei) provides r04 Fenqin, Thank you for providing r04 . For following 2nd thing(missing text in 5.8.2.18), It was my mistake in r01. Thank you again for correcting. Laurent (Nokia): provides r05 Fenqin (Huawei) is fine with r05 ==== Revisions Deadline ==== Changki(ETRI) is fine with r05. Magnus (Ericsson) is fine with r05 Yan (China Mobile) suggests to go with r05. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305758 | CR | Approval | 23.501 CR4490R1 (Rel-18, 'F'): Update the description of reporting suggestion information | Huawei, HiSilicon, Ericsson, ETRI | Rel-18 | Revision of S2-2305126r05. Approved | Agreed | |
| 9.16.2 | S2-2304691 | CR | Approval | 23.501 CR4378 (Rel-18, 'B'): CR 23501 Considering capability of UPF event exposure during UPF discovery | vivo | Rel-18 | r03 agreed. Revised to S2-2306240, merging S2-2304750. Affected Clauses: 6.3.3.3 | Fenqin (Huawei) provides r01 Josep (Deutsche Telekom) proposes improved wording, co-signs. Huazhang (vivo) provide r03 based on r02, only changing the title in the text, thanks to cosign ==== Revisions Deadline ==== Magnus (Ericsson) objects r01 and r00, accepts r03 Huazhang (vivo) ok to go with r03 Yan (China Mobile) suggests to go with r03. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2306240 | CR | Approval | 23.501 CR4378R1 (Rel-18, 'B'): Considering capability of UPF event exposure during UPF discovery | Vivo, Deutsche Telekom | Rel-18 | Revision of S2-2304691r03, merging S2-2304750. Approved | Agreed | |
| 9.16.2 | S2-2304937 | CR | Approval | 23.501 CR3922R1 (Rel-18, 'F'): Update for the description of the Nupf interface in 5G reference architecture | China Telecom | Rel-18 | Revision of S2-2300498 from S2#154AHE. CR Cover sheet error! CC#4: r13 + changes agreed. Revised to S2-2306256. Baseline paper for the architecture enhancement. Affected Clauses: 4.2.3 | Yan (China Mobile) suggests the authors to provide the merging version by merging content from 4694 and 4966. Laurent (Nokia): provides r01 Zhiwei (China Telecom) provides r02 by merging content from 4694 and 4966. Fenqin (Huawei) provides r03 by remove the 2nd change. Huazhang (vivo) replies to Fenqin Josep (Deutsche Telekom) comments, co-signs, provides r04. Jinsook (DISH) comments, co-signed and provides r05 Fenqin (Huawei) comments and provides r06 Josep (Deutsche Telekom) comments, provides r07. Josep (Deutsche Telekom) corrects a typo, provides r08. Yan (China Mobile) comments. Yoohwa(ETRI) provides r09 to cosign. Magnus (Ericsson) provides r10 Fenqin (Huawei) provides r11 Magnus (Ericsson) provides r12 Zhiwei (China Telecom) comments Zhiwei (China Telecom) comments and provides r13 ==== Revisions Deadline ==== Laurent (Nokia): objects to any version apart from R01 and R03. Can live with R13 based on a small change; Tdoc to be put in a CC? Josep (Deutsche Telekom) comments, is fine with the proposed Change in NOTE X to add 'DCCF/MFAF': 'NOTE X: In this Release of the specification, only SMF, NWDAF/DCCF/MFAF, NEF/AF and TSNAF/TSCTSF are considered as service consumers of UPF'. Fenqin(Huawei) suggest to go with R01/R03 or R13 and object the change suggested by Laurent. Magnus (Ericsson) objects to r00-r09 accept r13, can live with Laurent's proposed update Yan (China Mobile) requests for CC#3. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2306256 | CR | Approval | 23.501 CR3922R2 (Rel-18, 'F'): Update for the description of the Nupf interface in 5G reference architecture | China Telecom, Nokia, Nokia Shanghai Bell, vivo, China Mobile, Deutsche Telekom, DISH Network, ETRI, Ericsson | Rel-18 | Revision of S2-2304937r13 + changes. CC#4: Approved | Agreed | |
| 9.16.2 | S2-2304775 | CR | Approval | 23.501 CR4404 (Rel-18, 'B'): Updates on TSC management information | ETRI | Rel-18 | r04 agreed. Revised to S2-2305759. Affected Clauses: 5.8.5.1, 5.8.5.14 | Yoohwa(ETRI) provides r01. Laurent (Nokia): provides r02 Kenny (Qualcomm) provides r03, and not OK with previous revisions Yoohwa(ETRI) asks a question to Kenny(Qualcomm). Kenny(Qualcomm) replies Yoohwa (ETRI) question and OK with r02. Laurent (Nokia): provides r04 Fenqin (Huawei): comments ==== Revisions Deadline ==== Yoohwa(ETRI) is okay with r02 or r04 with reinserting clause 5.8.5.14 to the cover sheet. Laurent (Nokia): objects to R00,R01, R03 Magnus (Ericsson) is fine with r04 Fenqin (Huawei) is also fine with r04 Yan (China Mobile) suggests to go with r04. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305759 | CR | Approval | 23.501 CR4404R1 (Rel-18, 'B'): Updates on TSC management information | ETRI, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304775r04. Approved | Agreed | |
| 9.16.2 | S2-2304778 | CR | Approval | 23.501 CR4405 (Rel-18, 'F'): Clarification on UPF selection | Samsung | Rel-18 | Noted | Yan (China Mobile) comments. Magnus (Ericsson) questions the need for this CR Kisuk (Samsung) replies. ==== Revisions Deadline ==== Magnus (Ericsson) objects to this CR Magnus (Ericsson) objects to r00-r09. Ok with r13 Yan (China Mobile) suggests to object this CR. Magnus H (Ericsson) withdraw my latest comment and sustain objection to this CR ==== Comments Deadline ==== Kisuk (Samsung) notes this CR. | Noted |
| 9.16.2 | S2-2304965 | CR | Approval | 23.501 CR4445 (Rel-18, 'B'): Support of NAT exposure aligned with TS 23.502 | China Mobile | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305760. Affected Clauses: 6.2.3 | Magnus (Ericsson) provides r01 Yan (China Mobile) is ok with r01. Fenqin (Huawei) is ok with r01. Laurent (Nokia): provides r02 ==== Revisions Deadline ==== Yan (China Mobile) is ok with r02. Josep (Deutsche Telekom) is OK with r02 and would like to co-sign. Yan (China Mobile) suggests to go with r02 + adding Deutsche Telekom as a co-signer. Magnus (Ericsson) objects r00 are ok with r02, but cover page needs to be fixed Yan (China Mobile) will fix the cover sheet in the final version to state not affecting other specs. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305760 | CR | Approval | 23.501 CR4445R1 (Rel-18, 'B'): Support of NAT exposure aligned with TS 23.502 | China Mobile. Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304965r02. Approved | Agreed | |
| 9.16.2 | - | - | - | CRs for 23.502 | - | - | Docs:=10 | - | |
| 9.16.2 | S2-2304104 | CR | Approval | 23.502 CR3962 (Rel-18, 'C'): Updates to UPF Event Exposure | Ericsson | Rel-18 | CC#4: r07 agreed. Revised to S2-2306257. Baseline paper. Affected Clauses: 4.15.4.5.1, 4.15.4.5.2, 4.15.4.5.3, 5.2.26.2.1, 5.2.26.2.3 | Changki(ETRI) provides r01 by merging S2-2304453 into S2-2304104r01 with comments Yan (China Mobile) suggests the authors to provide the merging version by merging content from 4453, 4693, 4962, 5010. Laurent (Nokia): Comments Magnus (Ericsson) provides r02 Yan (China Mobile) provides r03. Laurent (Nokia): the procedure relying on NWDAF knowing QFI requires a second thought. QoS monitoring should go via PCF Laurent (Nokia): provides r04 (you can skip) and R05 Yan (China Mobile) provides r06. Fenqin (Huawei) provides r07. Laurent (Nokia): provides r08 Laurent (Nokia): provides r09 ==== Revisions Deadline ==== Laurent (Nokia): objects to any version except R08/R09 Magnus (Ericsson) objects to r08 and r09, accepts all other revisions Fenqin (Huawei) suggest to go with r07 Yan (China Mobile) requests for CC#3 along with 4963. Changki(ETRI) also suggest to go with r07 ==== Comments Deadline ==== Laurent(Nokia) for the sake of progress withdraws his objection but asks his concerns to be put in the meeting Notes | Revised |
| 9.16.2 | S2-2306257 | CR | Approval | 23.502 CR3962R1 (Rel-18, 'C'): Updates to UPF Event Exposure | Ericsson | Rel-18 | Revision of S2-2304104r07. CC#4: Approved | Agreed | |
| 9.16.2 | S2-2304415 | CR | Approval | 23.502 CR3726R1 (Rel-18, 'B'): UPF event exposure service to NWDAF for AoI in TS 23.502 | China Mobile | Rel-18 | Revision of S2-2300451 from S2#154AHE. r05 agreed. Revised to S2-2305761. Affected Clauses: 4.15.4.5.x (all new text) | Laurent (Nokia): provides r01 Naman (Samsung) provides comments Aihua(CMCC) provides r02 and replies. Aihua(CMCC) provides r03 to make alignment between the figure and the procedure description. Aihua (CMCC) provides r04 and replies. Laurent (Nokia): provides r05 Naman (Samsung) is fine with r05 ==== Revisions Deadline ==== Laurent (Nokia): objects to any version apart R03; can live with R05 with a small change (e.g. --> i.e) Magnus H (Ericsson) are OK with r05 Aihua (CMCC) prefer to r05 with a smalll change (e.g. --> i.e) proposed by Laurent. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305761 | CR | Approval | 23.502 CR3726R2 (Rel-18, 'B'): UPF event exposure service to NWDAF for AOI in TS 23.502 | China Mobile, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304415r05. Approved | Agreed | |
| 9.16.2 | S2-2304692 | CR | Approval | 23.502 CR4054 (Rel-18, 'B'): CR 23502 Add NWDAF as consumer of DNAI Mapping service | vivo | Rel-18 | Approved | Agreed | |
| 9.16.2 | S2-2305078 | CR | Approval | 23.502 CR4104 (Rel-18, 'B'): Clarifications to UPF event exposure service for TSC management | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! r04 agreed. Revised to S2-2305762. Baseline paper. Affected Clauses: 5.2.5.3.2 ; 5.2.5.3.3 ; 5.2.5.3.6 ; 5.2.8.3.3 ; 5.2.26.2.1 5.2.26.2.3 ; F.1 | Yoohwa(ETRI) comments. Laurent (Nokia): answers and provides r01 Kenny (Qualcomm): provides comments. Fenqin (Huawei): provides comments and suggest take exiting PCC rule/N4 extension as baseline. Fenqin (Huawei): provides r02. Yan (China Mobile) provides r03. Yoohwa(ETRI) provides r04. Laurent (Nokia): provides r05 Yan (China Mobile) objects to r05. Fenqin (Huawei) objects to r05. ==== Revisions Deadline ==== Yan (China Mobile) suggests to go with r04. Magnus (Ericsson) can only accept r04 objects to all other revisions ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305762 | CR | Approval | 23.502 CR4104R1 (Rel-18, 'B'): Clarifications to UPF event exposure service for TSC management | Nokia, Nokia Shanghai Bell, ETRI | Rel-18 | Revision of S2-2305017r04. Approved | Agreed | |
| 9.16.2 | S2-2304829 | CR | Approval | 23.502 CR4074 (Rel-18, 'C'): Update data exposure via SBI | Samsung | Rel-18 | Noted | Yan (China Mobile) comments. Kisuk (Samsung) replies. Laurent (Nokia): objects to the proposal Fenqin (Huawei) object to this proposal Magnus H (Ericsson) objects to this proposal ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.16.2 | S2-2305193 | CR | Approval | 23.502 CR4124 (Rel-18, 'C'): Improving AF specific UE ID retrieval | Ericsson Inc. | Rel-18 | CR Cover sheet error! r00 agreed. Revised to S2-2305728. Affected Clauses: 4.15.10, 5.2.26.3.2 | Revised | |
| 9.16.2 | S2-2305728 | CR | Approval | 23.502 CR4124R1 (Rel-18, 'C'): Improving AF specific UE ID retrieval | Ericsson Inc. | Rel-18 | Revision of S2-2305193r00. Approved | Agreed | |
| 9.16.2 | - | - | - | CRs for 23.503 | - | - | Docs:=4 | - | |
| 9.16.2 | S2-2304963 | CR | Approval | 23.503 CR1013 (Rel-18, 'B'): QoS monitoring exposure by UPF to NWDAF aligned with TS 23.502 | China Mobile | Rel-18 | CR Cover sheet error! CC#4: r03 agreed. Revised to S2-2306258. Baseline paper. Affected Clauses: 6.1.3.21, 6.1.3.22, 6.3.1 | Kenny (Qualcomm) provides comments Yan (China Mobile) replies. Magnus (Ericsson) with 4104r02 this CR is not needed. Yan (China Mobile) provides r01. Mirko (Huawei) comments and provides r02. Yan (China Mobile) provides r03. ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of the CR (this relates to discussions on 4104) Magnus (Ericsson) objects r00-r02 and suggest to go with r03 ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2306258 | CR | Approval | 23.503 CR1013R1 (Rel-18, 'B'): QoS monitoring exposure by UPF to NWDAF aligned with TS 23.502 | China Mobile | Rel-18 | Revision of S2-2304963r03. CC#4: Approved | Agreed | |
| 9.16.2 | S2-2304777 | CR | Approval | 23.503 CR0997 (Rel-18, 'B'): Updates on TSCTSF parameters | ETRI | Rel-18 | r02 agreed. Revised to S2-2305763. Affected Clauses: 6.1.3.23a | Yan (China Mobile) suggests to keep alignment with 5078. Fenqin (Huawei) comments Kenny (Qualcomm) provides comments Yoohwa(ETRI) responds to Yan(China Mobile). Yoohwa(ETRI) responds to Kenny(Qualcomm). Yan (China Mobile) comments. Yoohwa(ETRI) provides r01 to align with 5078 in 23.502. Laurent (Nokia): provides r02 ==== Revisions Deadline ==== Magnus (Ericsson) is fine with r02 Laurent (Nokia): objects to R00 Yan (China Mobile) suggests to go with r02. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305763 | CR | Approval | 23.503 CR0997R1 (Rel-18, 'B'): Updates on TSCTSF parameters | ETRI, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304777r02. Approved | Agreed | |
| 9.16.2 | - | - | - | CRs for 23.288 | - | - | Docs:=2 | - | |
| 9.16.2 | S2-2304474 | CR | Approval | 23.288 CR0688R1 (Rel-18, 'B'): NWDAF access to UPF information | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2301254 from S2#154AHE. CR Cover sheet error! r02 agreed. Revised to S2-2305764. Affected Clauses: 6.4.1 ; 6.10.2 ; 6.7.3.4 ; 6.10.4 | Magnus (Ericsson) provides r01 Fenqin (Huawei) comments Laurent (Nokia): provides r02 ==== Revisions Deadline ==== Magnus (Ericsson) prefers r01, but can live with r02. Laurent (Nokia): objects to R01 ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2305764 | CR | Approval | 23.288 CR0688R2 (Rel-18, 'C'): NWDAF access to UPF information | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304474r02. Approved | Agreed | |
| 9.16.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=13 | - | |
| 9.16.2 | S2-2304103 | CR | Approval | 23.501 CR4209 (Rel-18, 'C'): UPF Data Exposure via SBI | Ericsson | Rel-18 | Not handled? Merged into S2-2305126? Affected Clauses: 5.8.2.17 | NOT HANDLED | |
| 9.16.2 | S2-2304782 | CR | Approval | 23.501 CR4406 (Rel-18, 'F'): Update data exposure via SBI | Samsung | Rel-18 | Not handled? Merged into S2-2305126? Affected Clauses: 5.8.2.17 | NOT HANDLED | |
| 9.16.2 | S2-2304452 | CR | Approval | 23.501 CR4315 (Rel-18, 'B'): Update for QoS flow related QoS monitoring event and reporting | ETRI | Rel-18 | Not handled Merged into S2-2305126. Affected Clauses: 5.8.2.18 | NOT HANDLED | |
| 9.16.2 | S2-2304964 | CR | Approval | 23.501 CR4444 (Rel-18, 'B'): QoS monitoring exposure by UPF to NWDAF aligned with TS 23.503 | China Mobile | Rel-18 | CR Cover sheet error! Not handled? Merged into S2-2305126? Affected Clauses: 5.8.2.18 | NOT HANDLED | |
| 9.16.2 | S2-2304694 | CR | Approval | 23.501 CR4379 (Rel-18, 'B'): CR 23501 Architecture enhancement of service based interface provided by UPF | vivo | Rel-18 | Not handled? Merged into S2-2304937? Affected Clauses: 4.2.X | NOT HANDLED | |
| 9.16.2 | S2-2304966 | CR | Approval | 23.501 CR4446 (Rel-18, 'B'): Update the reference architecture with Nupf | China Mobile | Rel-18 | CR Cover sheet error! Not handled? Merged into S2-2304937? Affected Clauses: 4.2.3 | NOT HANDLED | |
| 9.16.2 | S2-2305077 | CR | Approval | 23.501 CR4474 (Rel-18, 'B'): Clarifications to UPF event exposure service for TSC management | Nokia, Nokia Shanghai Bell | Rel-18 | Not handled? Merged into S2-2304775? Affected Clauses: 5.28.3.1 | NOT HANDLED | |
| 9.16.2 | S2-2304453 | CR | Approval | 23.502 CR4011 (Rel-18, 'B'): Update for Indirect UPF Event event exposure subscription | ETRI | Rel-18 | Merged into S2-2304104. Affected Clauses: 4.15.4.5, 5.2.8.3 | NOT HANDLED | |
| 9.16.2 | S2-2304693 | CR | Approval | 23.502 CR4055 (Rel-18, 'B'): CR 23502 Clarification of UPF discovery during event exposure | vivo | Rel-18 | Not handled? Merged into S2-2304104? Affected Clauses: 4.15.4.5.1 | NOT HANDLED | |
| 9.16.2 | S2-2304962 | CR | Approval | 23.502 CR4089 (Rel-18, 'B'): QoS monitoring exposure by UPF to NWDAF | China Mobile | Rel-18 | Not handled? Merged into S2-2304104? Affected Clauses: 4.15.4.5.1 | NOT HANDLED | |
| 9.16.2 | S2-2305010 | CR | Approval | 23.502 CR4095 (Rel-18, 'B'): Update to Nupf Event exposure | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Not handled? Merged into S2-2304104? Affected Clauses: 5.2.26.2.1, 5.2.26.2.3; 4.15.4.5.1; 4.15.4.5.2 | NOT HANDLED | |
| 9.16.2 | S2-2304776 | CR | Approval | 23.502 CR3817R1 (Rel-18, 'F'): Updates on Npcf_PolicyAuthorization service | ETRI | Rel-18 | Revision of S2-2300935 from S2#154AHE Not handled? Merged into S2-2305078? Affected Clauses: 5.2.5.3.2, 5.2.5.3.3 | NOT HANDLED | |
| 9.16.2 | S2-2304105 | CR | Approval | 23.503 CR0798R1 (Rel-18, 'B'): Update to enable NWDAF subscription to QoS monitoring event for an Application Id | Ericsson | Rel-18 | Revision of S2-2300133 from S2#154AHE Not handled? Merge with S2-2304963? Affected Clauses: 6.1.3.21, 6.3.1 | NOT HANDLED | |
| 9.17.1 | - | - | - | Study on Edge Computing Phase 2 (FS_EDGE_Ph2) | - | - | Docs:=0 | - | |
| 9.17.2 | - | - | - | Edge Computing Phase 2 (EDGE_Ph2) | - | - | Docs:=89 | - | |
| 9.17.2 | - | - | - | Incoming LS | - | - | Docs:=3 | - | |
| 9.17.2 | S2-2303972 | LS In | Information | Reply LS on the use of a non-network defined identifier for UE identification | SA WG3 (S3-231402) | Rel-18 | Noted | Patrice (Huawei) indicates that this LS can be noted. | Noted |
| 9.17.2 | S2-2303977 | LS In | Action | LS on shared EHE and HR PDU session with SBO in V-PLMN | SA WG5 (S5-232734) | Rel-18 | Noted | Patrice (Huawei) indicates that this LS can be noted. | Noted |
| 9.17.2 | S2-2303986 | LS In | Information | LS from SA WG6: Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | SA WG6 (S6-231061) | Rel-18 | Noted | Patrice (Huawei) indicates that this LS can be noted. | Noted |
| 9.17.2 | - | - | - | KI#1/SBO general aspects | - | - | Docs:=7 | - | |
| 9.17.2 | S2-2304284 | CR | Approval | 23.548 CR0115 (Rel-18, 'C'): Supporting HR-SBO in VPLMN | China Unicom | Rel-18 | Merged into S2-2306208 | Hui(Huawei) this paper is merged into S2-2304707. Tianqi (China Unicom) is ok to merge this tdoc into S2-2304707. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.17.2 | S2-2304709 | CR | Approval | 23.502 CR4060 (Rel-18, 'B'): KI#1 PCF and SMF service enhancement to support HR-SBO | Huawei, HiSilicon | Rel-18 | CC#4: r01 + chnages agreed. Revised to S2-2306238. POSTPONED? For CC#4 | Jicheol (Samsung) comments. Magnus (Ericsson) provides comments Hui (Huawei) replies and provide r01 Hui (Huawei) replies to Jicheol. Laurent (Nokia): Comments Dario (Qualcomm) strongly support option 1 by Laurent (V-EASDF forwards to public DNS server unresolvable DNS queries). Magnus H (Ericsson) V-EASDF sends DNS traffic to what is in the DNS Handling rules, nothing more, nothing less. Hui(Huawei) provides comment. Dario (Qualcomm) replies. ==== Revisions Deadline ==== Dario (Qualcomm): this seems linked to 4976 etc. and should be postponed. Hui (Huawei): propose r02 and asks for discuss in CC# or CC#4 Laurent (Nokia): ok with R02 post deadline (for CC) with one additional removal Hui (Huawei): propose r03 and asks for discuss in CC# or CC#4: r03 is based r01(uploaded before rev deadline), with remove all 'HPLMN DNS Server address' Dario (Qualcomm) is OK with r03. Tianqi (China Unicom) asks for clarification. Hui (Huawei) replies to Tianqi. ==== Comments Deadline ==== Jicheol (Samsung) object r03. Hui (Huawei) suggest to go with r02. R02 =r01 + removal of 2 new added'HPLMN DNS Server address'. | Revised |
| 9.17.2 | S2-2306238 | CR | Approval | 23.502 CR4060R1 (Rel-18, 'B'): KI#1 PCF and SMF service enhancement to support HR-SBO | Huawei, HiSilicon | Rel-18 | Revision of S2-2304709r01 + chnages. CC#4: Approved | Agreed | |
| 9.17.2 | S2-2304710 | CR | Approval | 23.501 CR4381 (Rel-18, 'B'): KI#1 V-SMF selection enhancement to support HR-SBO | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306204. | Magnus (Ericsson) comments Hui (Huawei) provides r01 Magnus (Ericsson) suggest the same update in second change as was made in first change in r01 Hui (Huawei) provides r02 ==== Revisions Deadline ==== Magnus (Ericsson) objects to r00-r01. Can only accept r02 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306204 | CR | Approval | 23.501 CR4381R1 (Rel-18, 'B'): KI#1 V-SMF selection enhancement to support HR-SBO | Huawei, HiSilicon | Rel-18 | Revision of S2-2304710r02. Approved | Agreed | |
| 9.17.2 | S2-2304792 | CR | Approval | 23.502 CR4069 (Rel-18, 'C'): SMF service description update for usage monitoring on HR-SBO Session | Samsung | Rel-18 | Postponed | Laurent (Nokia): has concerns with the proposal: Usage reporting should go to V-SMF and V-CHF, not over (inter PLMN) N16 Hyesung (Samsung) replies Hui (Huawei) provides comments. ==== Revisions Deadline ==== Dario (Qualcomm) shares Nokia's and Huawei's view and suggest postponing the paper. Laurent (Nokia): objects to any version ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304824 | CR | Approval | 23.548 CR0131 (Rel-18, 'C'): Usage monitoring for HR-SBO PDU Session | Samsung | Rel-18 | Postponed | Laurent (Nokia): has concerns with the proposal: Usage reporting should go to V-SMF and V-CHF, not over (inter PLMN) N16 Hyesung (Samsung) replies Hui (Huawei) provides comments. ==== Revisions Deadline ==== Dario (Qualcomm) shares Nokia's and Huawei's view and suggest postponing the paper. Laurent (Nokia): objects to any version ==== Comments Deadline ==== | Postponed |
| 9.17.2 | - | - | - | KI#1/AF influence | - | - | Docs:=7 | - | |
| 9.17.2 | S2-2305115 | CR | Approval | 23.502 CR4110 (Rel-18, 'C'): Corrections on handling the AF traffic influencing request for HR-SBO PDU Sessions | OPPO | Rel-18 | r01 agreed. Revised to S2-2306205. | Laurent (Nokia): Comments/questions Yaxin (OPPO) replies to Laurent (Nokia). Hyesung (Samsung) asks some questions Magnus H (Ericsson) has same comments and questions as Hyesung Yaxin (OPPO) replies. Hui (Huawei) comments. Magnus H (Ericsson) provides comments Yaxin (OPPO) provides r01 and replies. ==== Revisions Deadline ==== Magnus (Ericsson) can only accept r01, objects to r00 Hui(Huawei) can only accept r01, objects to r00 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306205 | CR | Approval | 23.502 CR4110R1 (Rel-18, 'C'): Corrections on handling the AF traffic influencing request for HR-SBO PDU Sessions | OPPO | Rel-18 | Revision of S2-2305115r01. Approved | Agreed | |
| 9.17.2 | S2-2305116 | CR | Approval | 23.548 CR0142 (Rel-18, 'C'): Corrections on handling the AF traffic influencing request for HR-SBO PDU Sessions | OPPO | Rel-18 | Approved | Laurent (Nokia): Same question as 5115 Yaxin (OPPO) replies to Laurent (Nokia). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.17.2 | S2-2304712 | CR | Approval | 23.502 CR4061 (Rel-18, 'B'): KI#1 Update on AF influence via VPLMN | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306206. | Hyesung (Samsung) comments. Laurent (Nokia): provides r01 Magnus (Ericsson) finds the 0b-1 step confusing and provides r03 Hui (Huawei) replies. Hui (Huawei) provides r04. Magnus H (Ericsson) provides comments Hui (Huawei) replies to Magnus Hui (Huawei) replies to Hyesung Laurent (Nokia): provides r05 Magnus H (Ericsson replies to Hui and asks some more questions ==== Revisions Deadline ==== Magnus (Ericsson) can only accept r03, objects to all other revision ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306206 | CR | Approval | 23.502 CR4061R1 (Rel-18, 'B'): KI#1 Update on AF influence via VPLMN | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304712r03. Approved | Agreed | |
| 9.17.2 | S2-2304687 | CR | Approval | 23.502 CR4053 (Rel-18, 'B'): CR 23502 Authorization of AF traffic influence in roaming in HR-SBO | vivo | Rel-18 | r04 agreed. Revised to S2-2306207. | Magnus (Ericsson) don't understand how EN is solved Huazhang (vivo) replies to Magnus Huazhang (vivo) correct the title and responses to Laurent (Nokia) Hui (Huawei) provides comments Huazhang (vivo) reply to Hui Huazhang (vivo) provides r01 to reflect the comments by Hui Hui (Huawei) fine with r01 Laurent (Nokia): provides r02 Laurent (Nokia): provides r03 Huazhang (vivo) can live with this r03, thanks Laurent and Hui Hyesung (Samsung) has concern on the proposed changes on the subscription data Huazhang (vivo) provides r04 to reflect the concerns Huazhang (vivo) provides r04 to reflect the concerns, forget to copy the link Hyesung (Samsung) provides r05 (minor change from r04) ==== Revisions Deadline ==== Hui(Huawei) objects r00, can accept other versions Huazhang (vivo) can accept r04 - r05, and prefer to go with r05 Hyesung (Samsung) suggests to go with r05, objects to r00~03. r04 is not preferred. Laurent (Nokia): objects to R00, R01, R02 and to R05 Huazhang (vivo) think the only agreed version is r04, thanks ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306207 | CR | Approval | 23.502 CR4053R1 (Rel-18, 'B'): Authorization of AF traffic influence in roaming | Vivo, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304687r04. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1/EAS discovery | - | - | Docs:=4 | - | |
| 9.17.2 | S2-2304707 | CR | Approval | 23.548 CR0120 (Rel-18, 'B'): KI#1 EAS Discovery: Resolve ENs | Huawei, HiSilicon | Rel-18 | CC#4: r09 + changes agreed. Revised to S2-2306208, merging S2-2304284 | Laurent (Nokia): cannot proceed with this tdoc as long as we have not concluded on how to forward DNS traffic Magnus (Ericsson) provides r01 Hui (Huawei) provides r02 Tianqi (China Unicom) provides r03. Magnus (Ericsson) provides r04 Hui (Huawei) provides r05, removed changes related to EN on detect which FQDN is allowed for HR-SBR. Laurent (Nokia): provides r07 Tianqi (China Unicom) provides r06. Magnus (Ericsson) provides r08 Tianqi (China Unicom) provides r09. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306208 | CR | Approval | 23.548 CR0120R1 (Rel-18, 'B'): KI#1 EAS Discovery: Resolve ENs | Huawei, HiSilicon, China Unicom | Rel-18 | Revision of S2-2304707r09 + changes, merging S2-2304284. CC#4: Approved | Agreed | |
| 9.17.2 | S2-2304708 | CR | Approval | 23.503 CR0992 (Rel-18, 'B'): KI#1 Resolve ENs on EAS Discovery for HR-SBO | Huawei, HiSilicon | Rel-18 | CC#4: r01 + chnages agreed. Revised to S2-2306209. | Laurent (Nokia): Comments Hui (Huawei) provides r01 Dario (Qualcomm) comments. Hui (Huawei) replies to Dario. ==== Revisions Deadline ==== ==== Comments Deadline ==== Hui (Huawei) provides r02 = r01+ remove second change, to avoid overlapping with S2-2304980r03. Requests to discuss the CR on CC#4. | Revised |
| 9.17.2 | S2-2306209 | CR | Approval | 23.503 CR0992R1 (Rel-18, 'B'): KI#1 Resolve ENs on EAS Discovery for HR-SBO | Huawei, HiSilicon | Rel-18 | Revision of S2-2304708r01 + chnages. CC#4: Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1/DNS request handling & security aspects | - | - | Docs:=14 | - | |
| 9.17.2 | S2-2305054 | LS OUT | Approval | [DRAFT] LS to SA WG3 on Secure DNS | Sony | Rel-18 | r05 agreed. CC#4: r06 + changes agreed. Revised to S2-2306210. | Laurent (Nokia): has sympathy with LS from Sony but would like some changes Magnus H (Ericsson) is OK with the LS and with Laurent's proposed updates. And proposes to postpone 5052 until answer from SA3 Laurent (Nokia): provides r01 according to his previous comments Hui (Huawei) provides r02 and clarify that this is not EC-specific topic. Svante (Sony): provides answers on Hui (Huawei) LS proposal. Dario (Qualcomm) comments. Svante (Sony): Provide answers to Dario (Qualcomm) on DNS Security Magnus (Ericsson) provides R03 Jicheol (Samsung) comments. Hui (Huawei) comments Laurent (Nokia): provides r4 Svante (Sony): Provide answers to Hui (Huawei), Jicheol (Samsung), Magnus (Ericsson) & Laurent (Nokia) Dario (Qualcomm) provides r05. Svante (Sony): Asking Dario (Qualcomm) questions on r05. ==== Revisions Deadline ==== Dario (Qualcomm) thanks Svante for spotting the issue; provides r06 (i.e., the real r05) and can only accept this version (objects to previous ones). Hui (Huawei): objects to r00-r02, can accept other versions. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306210 | LS OUT | Approval | DNS over TLS (DoT) and DNS over HTTPS (DoH) | SA WG2 | Rel-18 | Revision of S2-2305054r06 + changes. CC#4: Approved | Approved | |
| 9.17.2 | S2-2305049 | DISCUSSION | Discussion | Discussion on Secure DNS | Sony | Rel-18 | Noted | Noted | |
| 9.17.2 | S2-2305052 | CR | Approval | 23.501 CR4472 (Rel-18, 'B'): Secure DNS in 23.501 | Sony | Rel-18 | Postponed | Laurent (Nokia): provides r01 Magnus (Ericsson) proposes to postpone this until response from SA3 Dan (China Mobile) ask some question Svante (Sony): Provide answers to Magnus (Ericsson) and Dan (China Mobile). Hui (Huawei) comments that this issue is not EC specific, thus should not be discussed in EC. Svante (Sony): Provide answers to Hui (Huawei). Dario (Qualcomm) comments. Svante (Sony): Provide answers to Dario (Qualcomm) on DoH Jicheol (Samsung) comments. Svante (Sony): Provide answers to Jicheol (Samsung) and r02. Dario (Qualcomm) replies to Svante. Svante (Sony): Replies to Dario (Qualcomm) ==== Revisions Deadline ==== Jicheol (Samsung) proposes to postpone this CR until SA3 responds Magnus (Ericsson) objects to this CR (postpone). Let's wait for SA3 reply on LS 5054 Hui (Huawei) proposes to note this CR ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304688 | CR | Approval | 23.501 CR4377 (Rel-18, 'B'): CR 23.501 Add FQDN in Traffic Detection Information | vivo | Rel-18 | r07 agreed. Revised to S2-2306211. | Laurent (Nokia): asks whether this shouldn't be a R17 CR Yaxin (OPPO) provides comments. Huazhang (vivo) reply to Laurent Huazhang (vivo) provides r01 Laurent (Nokia): answers (and concerns with this R18 Edge_Ph2 CR) Hui (Huawei) provides comments and r02, and agree a Rel-17 CR is needed. Huazhang (vivo) thanks for Hui to provide r02, that Huazhang provide r03 based on r02, to remove wording 'NOTE 9' Xinpeng(Huawei) comments. Dario (Qualcomm): shouldn't we use the term 'FQDN(s)' instead of 'FQDN range(s)'? Changhong (Intel) propose to postpone this CR. Huazhang (vivo) provides r04 that to add the R17 and TEI 18 as Laurent said in the work item. And add any FQDN as Xinpeng said. And clarify to Changhong about the reasons for change. Huazhang (vivo) reply to Dario that I find the example from Xinpeng that including both the FQDNs, FQDN range and any FQDN. Please see revision 4 I provided. Jicheol (Samsung) provides r05. (proposing a new wording: 'FQDN Filter for DNS Query') Laurent (Nokia): provides r06 Huazhang (vivo) provide r07 based on r06, to fix the reference to 29.244 in the cover sheet, I forgot to add the reference clause. ==== Revisions Deadline ==== Laurent (Nokia): objects to any version between R00 and R05 both included Huazhang (vivo) suggest to go with r07 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306211 | CR | Approval | 23.501 CR4377R1 (Rel-18, 'F'): Add FQDN in Traffic Detection Information | Vivo, Nokia | Rel-18 | Revision of S2-2304688r07. Approved | Agreed | |
| 9.17.2 | S2-2304976 | CR | Approval | 23.548 CR0132 (Rel-18, 'B'): DNS traffic routing between the UE and the V-EASDF for HR-SBO | Samsung | Rel-18 | Postponed | Magnus (Ericsson) needs to be discussed together with 4157 and perhaps 5013 Magnus (Ericsson) provides comments Dario (Qualcomm) comments and has concerns with the approach of forwarding DNS query to H-DNS resolver since it moves away from the regular DNS behavior. Laurent (Nokia): suggests to postpone 4976, 5013 and 4157 ==== Revisions Deadline ==== Dario (Qualcomm) is OK with postponing. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304689 | CR | Approval | 23.548 CR0118 (Rel-18, 'B'): FQDN detection during EAS Discovery Procedure with Local DNS for HR-SBO | vivo | Rel-18 | r04 agreed. Revised to S2-2306212. | Laurent (Nokia): Asks a question Huazhang (vivo) provides r01 Tianqi (China Unicom) comments. Huazhang (vivo) provides r02 and reply to Tianqi Laurent (Nokia): Comments Laurent (Nokia): Comments with request to update Huazhang (vivo) provides r03 as Laurent suggestion Dario (Qualcomm) comments and has concerns with the approach of forwarding DNS query to H-DNS resolver since it moves away from the regular DNS behavior. Huazhang (vivo) reply to Dario and check how to move forward. Huazhang (vivo) provide further reply to Dario Laurent (Nokia): provides r04 ==== Revisions Deadline ==== Dario (Qualcomm) supports v04. Huazhang (vivo) is ok to go with r04, thanks Laurent Hui (Huawei) fine with r04 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306212 | CR | Approval | 23.548 CR0118R1 (Rel-18, 'B'): FQDN detection during EAS Discovery Procedure with Local DNS for HR-SBO | Vivo | Rel-18 | Revision of S2-2304689r04. Approved | Agreed | |
| 9.17.2 | S2-2305063 | CR | Approval | 23.548 CR0139 (Rel-18, 'B'): Resolve the EN about local traffic routing in HR-SBO | China Mobile | Rel-18 | r01 agreed. Revised to S2-2306213. CC#4: Noted | Laurent (Nokia): has a lot of questions (means has doubts) Tangqing(China Mobile) reply to Laurent. Dario (Qualcomm): please see my comments for 5013. Jicheol (Samsung) supports this CR. Hui (Huawei) provide r01 and would like to co-sign. Laurent (Nokia): objects to any version ==== Revisions Deadline ==== Dario (Qualcomm) supports postponing the discussion. Magnus H (Ericsson) suggest to go with r01 and likes to co-sign Dan (China Mobile) suggest to go with r01 and close the discussion. ==== Comments Deadline ==== Laurent (Nokia) reminds that he objected to any version and still object | Noted |
| 9.17.2 | S2-2306213 | CR | Approval | 23.548 CR0139R1 (Rel-18, 'B'): Resolve the EN about local traffic routing in HR-SBO | China Mobile | Rel-18 | Revision of S2-2305063r01. CC#4: WITHDRAWN APPROVED. For CC#4. (reconfirm) | Withdrawn | |
| 9.17.2 | S2-2305013 | CR | Approval | 23.548 CR0136 (Rel-18, 'B'): Route the DNS traffic between the UE, the V-EASDF and the HPLMN DNS server | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Magnus (Ericsson) ask question Laurent (Nokia): answers Dario (Qualcomm) comments and has concerns with the approach of forwarding DNS query to H-DNS resolver. Dan (China Mobile) comments Magnus H (Ericsson) provides comments Hui (Huawei) provides comments. Laurent (Nokia): suggests to postpone 4976, 5013 and 4157 Magnus (Ericsson) provides comments Magnus (Ericsson) withdraws my latest comment ==== Revisions Deadline ==== Dario (Qualcomm) is fine with postponing the discussion. Magnus (Ericsson) objects to this CR ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2305014 | CR | Approval | 23.548 CR0137 (Rel-18, 'B'): HR SBO and DNS security | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2306214. | Laurent (Nokia): this Tdoc is tagged by mistake as Alt 3 of DNS traffic forwarding while it addresses topic 1 Dario (Qualcomm) provides r01 to include change needed from Rel-17. Hui (Huawei) needs to select between this and 5063 Laurent (Nokia): answers Sudeep (Apple) comments on r01. ==== Revisions Deadline ==== Dario (Qualcomm) replies to Sudeep and proposes to move forward with r01 with the understanding that in Berlin we will fix also Rel-17. Hui (Huawei) fine with r01, objects to r00. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306214 | CR | Approval | 23.548 CR0137R1 (Rel-18, 'B'): HR SBO and DNS security | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305014r01. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1/Offload policy | - | - | Docs:=4 | - | |
| 9.17.2 | S2-2304156 | DISCUSSION | Agreement | Discussion on offload policy Editor s Notes for HR-SBO scenario | Ericsson | Rel-18 | Revision of S2-2300921 from S2#154AHE. Noted | Laurent (Nokia): objects to 4156 that is anyhow implemented in 4157 Hui(Huawei) proposes to note this discussion paper which was marked as 'for agreement' ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304157 | CR | Approval | 23.548 CR0112 (Rel-18, 'B'): Home Routed-Session Breakout (HR-SBO) - resolving Overlapping UE IP and offload policy structure | Ericsson | Rel-18 | Postponed | Laurent (Nokia): needs to be discussed with 5013 and 4976 Dario (Qualcomm) comments and has concerns with the approach of forwarding DNS query to H-DNS resolver since it moves away from the regular DNS behavior. Magnus H (Ericsson) answer Dario Hui (Huawei) asks a basic question on the overlapping IP address issue Laurent (Nokia): suggests to postpone 4976, 5013 and 4157 Magnus H (Ericsson) answers Hui Hui (Huawei) replies to Magnus ==== Revisions Deadline ==== Magnus H (Ericsson) replies to Hui Hui (Huawei) proposes to postpone this CR. Laurent (Nokia): objects to this CR ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304980 | CR | Approval | 23.503 CR1014 (Rel-18, 'B'): HR-SBO Session AMBR in VPLMN Specific Offloading Policy | Samsung | Rel-18 | r03 agreed. Revised to S2-2306215. | Laurent (Nokia): provides r01 Hui (Huawei): provides r02 Dario (Qualcomm) comments and provides r03. Hui (Huawei) supports r03. ==== Revisions Deadline ==== Hui (Huawei) can only accept r02/r03, objects r00/r01. Laurent (Nokia): can only accept R03 ; objects to any other version ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306215 | CR | Approval | 23.503 CR1014R1 (Rel-18, 'B'): HR-SBO Session AMBR in VPLMN Specific Offloading Policy | Samsung | Rel-18 | Revision of S2-2304980r03. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1/Edge relocation | - | - | Docs:=9 | - | |
| 9.17.2 | S2-2304650 | CR | Approval | 23.548 CR0100R2 (Rel-18, 'B'): Support of inter-PLMN edge relocation | CATT | Rel-18 | Revision of S2-2302751 from S2#155. Postponed | Laurent (Nokia): Comments and concerns Yuan Tao (CATT) replies to Laurent (Nokia) and provides r01. Dario (Qualcomm) expresses concerns and asks questions. Yuan Tao (CATT) replies to Laurent (Nokia) and provides r02. Yuan Tao (CATT) replies to Dario (Qualcomm) and provides r03. Laurent (Nokia): suggests to postpone 5006, 5011, 4650, 4711 that are about inter PLMN HO; the 23.502 etc... corresponding Tdocs need also to be postponed Yuan Tao (CATT) replies to Laurent (Nokia), and suggest go with r02/r03. Dario (Qualcomm) supports Laurent's proposal. ==== Revisions Deadline ==== Yuan Tao (CATT) is fine to postpone this paper and all other inter-PLMN relocation topic papers. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304651 | CR | Approval | 23.501 CR4016R2 (Rel-18, 'B'): 23.501 Support of inter-PLMN Edge relocation | CATT | Rel-18 | Revision of S2-2302752 from S2#155. Postponed | Laurent (Nokia): Need to first agree on the high level principle in 23.548 Dario (Qualcomm) supports Laurent's comment. ==== Revisions Deadline ==== Dario (Qualcomm) objects to this paper. Yuan Tao (CATT) is fine to postpone this paper and all other inter-PLMN relocation topic papers. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304652 | CR | Approval | 23.503 CR0868R2 (Rel-18, 'B'): Support of inter-PLMN edge relocation | CATT | Rel-18 | Revision of S2-2302753 from S2#155. Postponed | Mike (InterDigital) comments. Yuan Tao (CATT) replies to Mike (InterDigital). Laurent (Nokia): Need to first agree on the high level principle in 23.548 Dario (Qualcomm) supports Laurent's proposal. ==== Revisions Deadline ==== Dario (Qualcomm) objects to this paper. Yuan Tao (CATT) is fine to postpone this paper and all other inter-PLMN relocation topic papers. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2305006 | CR | Approval | 23.548 CR0134 (Rel-18, 'B'): HR-SBO re-authorization procedure due to VPLMN change | Samsung | Rel-18 | Postponed | Yuan Tao (CATT) asks for clarifications. Laurent (Nokia): cannot be agreed as is, need to first agree on the documentation and procedure principles (hard in emeeting) Jicheol (Samsung) comments. Jicheol (Samsung) provides r01. Tianqi (China Unicom) asks for clarification. Hui (Huawei) comments Laurent (Nokia): suggests to postpone 5006, 5011, 4650, 4711 that are about inter PLMN HO; the 23.502 etc... corresponding Tdocs need also to be postponed ==== Revisions Deadline ==== Ouerdia (Orange): agree to postpone and discuss inter-PLMN topic Jicheol (Samsung) agree to postpone all the inter-PLMN topic. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2304764 | CR | Approval | 23.548 CR0126 (Rel-18, 'B'): V-EASDF handling during UE mobility with V-SMF change | LG Electronics | Rel-18 | Noted | Laurent (Nokia): cannot be agreed as is, need to first agree on the high level documentation and procedure principles (hard in emeeting) Hui (Huawei): comments Dario (Qualcomm) comments. Tianqi (China Unicom) asks for clarification. Hongsuk (LG Electronics) comments. Magnus H (Ericsson) agrees with Hui Hui (Huawei) replies to Hongsuk. ==== Revisions Deadline ==== Dario (Qualcomm) objects to this paper. Jicheol (Samsung) shares the view with Qualcomm, Huawei, Ericsson. proposes to note this paper. Magnus H (Ericsson) objects to this CR Hongsuk (LGE) asks to mark this CR as 'NOTED' ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304765 | CR | Approval | 23.502 CR4066 (Rel-18, 'B'): Support for the V-EASDF handling during UE mobility with V-SMF change | LG Electronics | Rel-18 | Noted | Laurent (Nokia): Need to first agree on the high level principle in 23.548 Dario (Qualcomm) supports Laurent's proposal. ==== Revisions Deadline ==== Dario (Qualcomm) objects to this paper (for the same reason expressed for 4764). Magnus (Ericsson) objects to this CR Hongsuk (LGE) asks to mark this CR as 'NOTED' ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304711 | CR | Approval | 23.548 CR0121 (Rel-18, 'B'): KI#1 EAS Re-discovery: Resolve ENs | Huawei, HiSilicon | Rel-18 | Postponed | Laurent (Nokia): cannot be agreed as is, need to first agree on the high level documentation and procedure principles (hard in emeeting) Hui (Huawei) replies Dario (Qualcomm) expresses concerns on the need for this CR. Tianqi (China Unicom) asks for clarification. Hui (Huawei) replies to Dario. Laurent (Nokia): suggests to postpone 5006, 5011, 4650, 4711 that are about inter PLMN HO; the 23.502 etc... corresponding Tdocs need also to be postponed Hui (Huawei) fine with postpone this and all other inter PLMN HO papers. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2305011 | CR | Approval | 23.548 CR0135 (Rel-18, 'B'): AF triggered EAS Re-discovery Procedure in HR-SBO Roaming scenarios | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Yuan Tao (CATT) asks for clarifications. Laurent (Nokia): answers Hui (Huawei) cannot agree with the paper. Dario (Qualcomm) expresses concern on the need to support the change of V-EASDF during the EAS re-discovery and proposes to remove that part. Tianqi (China Unicom) asks for clarification. Laurent (Nokia): suggests to postpone 5006, 5011, 4650, 4711 that are about inter PLMN HO; the 23.502 etc... corresponding Tdocs need also to be postponed Dario (Qualcomm) replies to Laurent. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2305079 | CR | Approval | 23.502 CR4105 (Rel-18, 'B'): AF triggered EAS Re-discovery Procedure in HR-SBO Roaming scenarios | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Hui (Huawei) cannot agree with the paper since it depends on S2-2305011. Dario (Qualcomm) comments. Magnus (Ericsson) provides comments Laurent (Nokia): suggests to postpone this paper related with 5011 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.17.2 | - | - | - | KI#1/EACI | - | - | Docs:=10 | - | |
| 9.17.2 | S2-2303989 | LS In | Action | LS from SA WG6: Reply LS on Edge Configuration Server associated with or serves multiple PLMNs | SA WG6 (S6-231093) | Rel-18 | Response drafted in S2-2304835. Final response in S2-2306216 | Replied to | |
| 9.17.2 | S2-2304835 | LS OUT | Approval | [DRAFT] LS reply on Edge Configuration Server associated with or serves multiple PLMNs | vivo | Response to S2-2303989. r01 agreed. Revised to S2-2306216. | Hui(Huawei) asks question. Huazhang (vivo) reply to Hui, and many thanks that you indicate this, provide r01 ==== Revisions Deadline ==== Hui(Huawei) fine with r00 and r01 Huazhang (vivo) thanks Hui, I am ok with r00 and r01, but prefers r01 to ask further ==== Comments Deadline ==== | Revised | |
| 9.17.2 | S2-2306216 | LS OUT | Approval | Reply LS on Edge Configuration Server associated with or serves multiple PLMNs | SA WG2 | - | Revision of S2-2304835r01. Approved | Approved | |
| 9.17.2 | S2-2304684 | CR | Approval | 23.502 CR4052 (Rel-18, 'B'): CR 23502 ECS Address Configuration Information delivery in roaming | vivo,Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2306217 | Hui(Huawei) asks how this solution works same as S2-2304685. Dario (Qualcomm) comments and suggests updates. ==== Revisions Deadline ==== Hui (Huawei) asks to note this paper. Huazhang (vivo) prefers to merge this paper to 2304714, if we all agree that paper, thanks Hui (Huawei) is happy to consider this as merged into S2-2304714. ==== Comments Deadline ==== | Merged |
| 9.17.2 | S2-2304685 | CR | Approval | 23.548 CR0117 (Rel-18, 'B'): ECS Address Configuration Information retrieving from UDR | vivo, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Hui(Huawei) asks question. Dario (Qualcomm) provides comments. Huazhang (vivo) reply to Hui Hui (Huawei) reply to Huazhang Huazhang (vivo) have a try and provide the r01 Hui (Huawei) provides comments to r01 Huazhang (vivo) feel free if can go to 4713/4714, see other comments. ==== Revisions Deadline ==== Hui (Huawei) asks to note this paper. Huazhang (vivo) thanks Hui, and I suggest to merge this paper into 2304713, I can agree that way Hui (Huawei) is happy to consider this as merged into S2-2304713. ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304713 | CR | Approval | 23.548 CR0122 (Rel-18, 'B'): KI#1 EACI provisioning from VPLMN | Huawei, HiSilicon | Rel-18 | Approved | Dario (Qualcomm) has concerns with defining a new Nnef service operation and explains how the existing one could be extended. Hyesung (Samsung) asks some questions. Hui(Huawei) replies to Dario Hui (Huawei) replies to Hyesung ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.17.2 | S2-2304714 | CR | Approval | 23.502 CR4062 (Rel-18, 'B'): KI#1 EACI provisioning from VPLMN | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2306217, merging S2-2304684 | Laurent (Nokia): provides r01 Dario (Qualcomm) has concerns as described in 4713. Hui(Huawei): fine with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306217 | CR | Approval | 23.502 CR4062R1 (Rel-18, 'B'): KI#1 EACI provisioning from VPLMN | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304714r01, merging S2-2304684. Approved | Agreed | |
| 9.17.2 | S2-2304763 | CR | Approval | 23.548 CR0125 (Rel-18, 'C'): Clarification on ECS Address Provisioning in roaming scenarios | Samsung | Rel-18 | CR Cover sheet error! r01 agreed. Revised to S2-2306218. | Dario (Qualcomm) comments and suggests change. Hyesung (Samsung) provides r01 ==== Revisions Deadline ==== Dario (Qualcomm) is OK w/ r01. Laurent (Nokia): objects to any version but a simple change can remove the objectioin: removing 'For the UE' in NOTE 2 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306218 | CR | Approval | 23.548 CR0125R1 (Rel-18, 'C'): Clarification on ECS Address Provisioning in roaming scenarios | Samsung | Rel-18 | Revision of S2-2304763r01. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#4/Multi-SMF | - | - | Docs:=9 | - | |
| 9.17.2 | S2-2304311 | CR | Approval | 23.501 CR4271 (Rel-18, 'F'): Selection of Common DNAI | NTT DOCOMO | Rel-18 | r01 agreed. Revised to S2-2306219. | Xinpeng(Huawei) provides r01. Tugce(NTT DOCOMO) responds and provides r03. Xinpeng(Huawei) replies to Tugce(NTT DOCOMO). Tugce(NTT DOCOMO) provides clarification. Tugce (NTT DOCOMO) responds. Magnus H (Ericsson) ask question Tugce (NTT DOCOMO) clarifies and provides r04. Magnus H (Ericsson) comments ==== Revisions Deadline ==== Xinpeng(Huawei) is ok with r01, and objects to all other versions. Tugce (NTT DOCOMO) proposes to continue with r04. Magnus (Ericsson) suggests to go with r04 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306219 | CR | Approval | 23.501 CR4271R1 (Rel-18, 'F'): Selection of Common DNAI | NTT DOCOMO | Rel-18 | Revision of S2-2304311r01. CC#4: Approved | Agreed | |
| 9.17.2 | S2-2304313 | CR | Approval | 23.502 CR3990 (Rel-18, 'F'): Selection of Common DNAI | NTT DOCOMO | Rel-18 | r04 agreed. Revised to S2-2306220. | Xinpeng(Huawei) comments. Shubhranshu (Nokia) asks for clarification Tugce (NTT DOCOMO) provides clarification. Tugce (NTT DOCOMO) provides r01. Tugce (NTT DOCOMO) responds. Xinpeng(Huawei) provides r02. Tugce (NTT DOCOMO) provides r03. Xinpeng(Huawei) replies to Tugce (NTT DOCOMO). Shubhranshu (Nokia) comments Tugce (NTT DOCOMO) provides r04. ==== Revisions Deadline ==== Xinpeng(Huawei) is ok with r02 and r04, objects to all other versions. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306220 | CR | Approval | 23.502 CR3990R1 (Rel-18, 'F'): Selection of Common DNAI | NTT DOCOMO | Rel-18 | Revision of S2-2304313r04. Approved | Agreed | |
| 9.17.2 | S2-2304314 | CR | Approval | 23.548 CR0116 (Rel-18, 'F'): Selection of Common DNAI | NTT DOCOMO | Rel-18 | Merged into S2-2305389 (noted) | Xinpeng(Huawei) comments. Tugce (NTT DOCOMO) responds. Shubhranshu (Nokia) asks for clarifications Tugce (NTT DOCOMO) provides clarification. Shubhranshu (Nokia) responds Tugce (NTT DOCOMO) provides r01. Xinpeng(Huawei) provides r02. Shubhranshu (Nokia) suggests to merge into S2-2305389 Tugce (NTT DOCOMO) is OK to merge clause 6.2.3.2.7 into S2-2305389 Shubhranshu (Nokia) OK to merge Tugce (NTT DOCOMO) OK to merge all clauses. Shubhranshu (Nokia) comments Dario (Qualcomm) comments. Hui(Huawei) proposes to note this LS in. Hui(Huawei) withdraw the previous comment which used wrong subject. Huazhang (vivo) says: Hui, is this the right number of TDoc? ==== Revisions Deadline ==== Xinpeng(Huawei) is ok with r02, and objects to all other versions. ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304784 | CR | Approval | 23.548 CR0127 (Rel-18, 'F'): KI#4 Coordination among SMFs for Common EASDNAI determination | Huawei, HiSilicon | Rel-18 | Noted | Xinpeng(Huawei) provides r01. Shubhranshu (Nokia) asks for clarification Tugce (NTT DOCOMO) comments. Xinpeng(Huawei) replies to Shubhranshu (Nokia). Xinpeng(Huawei) replies to Tugce (NTT DOCOMO). Magnus H (Ericsson) provides comments Xinpeng(Huawei) replies to Magnus H (Ericsson) Xinpeng(Huawei) provides r02. Shubhranshu (Nokia) comments Xinpeng(Huawei) replies to Magnus H (Ericsson). Xinpeng(Huawei) provides r05 based on r04. Shubhranshu (Nokia) comments and suggests to merge into S2-2305389 Xinpeng(Huawei) proposes keep 4784 seperately, not to merge. Tugce (NTT DOCOMO) responds ==== Revisions Deadline ==== Shubhranshu (Nokia) objects this paper, including to r05 ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2304831 | CR | Approval | 23.503 CR1001 (Rel-18, 'B'): 503 KI#4 Coordination among SMFs for Common EASDNAI determination | Huawei, HiSilicon | Rel-18 | LATE DOC: Rx: 11/04, 07:10. Noted | Dario (Qualcomm) asks question and suggests change. Xinpeng(Huawei) provides r01. Shubhranshu (Nokia) comments Xinpeng(Huawei) replies to Shubhranshu (Nokia). Shubhranshu (Nokia) asks for clarification Xinpeng(Huawei) replise to Shubhranshu (Nokia). Xinpeng(Huawei) provides r02. ==== Revisions Deadline ==== Shubhranshu (Nokia) Objects this paper ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2305389 | CR | Approval | 23.548 CR0144 (Rel-18, 'B'): Common EAS/DNAI determination for a set of UEs | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Shubhranshu (Nokia) provides r01 Xinpeng(Huawei) proposes update on solution based on what has been approved, but not invent a totally new one by the end of release. Shubhranshu (Nokia) responds Magnus H (Ericsson) agree with Shubhranshu Xinpeng(Huawei) replies to Magnus H (Ericsson). Tugce (NTT DOCOMO) asks for clarification. Shubhranshu (Nokia) comments Xinpeng(Huawei) responses to Shubhranshu (Nokia). Yuan Tao (CATT) comments. Shubhranshu (Nokia) provides r02 Tugce (NTT DOCOMO) comments. Shubhranshu (Nokia) provides r03 Shubhranshu (Nokia) provides r04 ==== Revisions Deadline ==== Xinpeng(Huawei) proposes to mark this paper as merged into 4784 or postponed. Shubhranshu (Nokia) proposes to agree this paper, NOT merge into S2-2304784 Tugce (NTT DOCOMO) is OK with r04. Xinpeng(Huawei) objects this CR. Totally new solution submitted by the end of release 18, which is never been evaluation. Shubhranshu (Nokia) does not agree to Xinpeng (Huawei) on this ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2305390 | CR | Approval | 23.502 CR4160 (Rel-18, 'B'): Common EAS/DNAI determination for a set of UEs | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Xinpeng(Huawei) the progress of this CR should be based on discussion in 5389 thread. ==== Revisions Deadline ==== Xinpeng(Huawei) proposes to postpone the paper, since the solution in TS23.548 should be stable first, then come to the TS23.502 CR. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | - | - | - | KI#4/Other | - | - | Docs:=2 | - | |
| 9.17.2 | S2-2304716 | CR | Approval | 23.548 CR0124 (Rel-18, 'B'): KI#4 DNS cache refresh triggered by common EAS-DNAI requests | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2306221. | Shubhranshu (Nokia) comments Dario (Qualcomm) suggests additional change. Hui (Huawei) asks for clarification Shubhranshu (Nokia) provides r01 Hui (Huawei) provides r02 ==== Revisions Deadline ==== Hui (Huawei) objects r02 and suggest to go with r01 Shubhranshu (Nokia) ok to r01 ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306221 | CR | Approval | 23.548 CR0124R1 (Rel-18, 'B'): KI#4 DNS cache refresh triggered by common EAS-DNAI requests | Huawei, HiSilicon | Rel-18 | Revision of S2-2304716r01. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#7 | - | - | Docs:=6 | - | |
| 9.17.2 | S2-2305084 | CR | Approval | 23.548 CR0140 (Rel-18, 'B'): Clarification for geographic area in DNAI mapping | China Mobile | Rel-18 | r04 agreed. Revised to S2-2306222, merging S2-2305371 and S2-2305369 | Shubhranshu (Nokia) comments Dan (China Mobile) reply Magnus H (Ericsson) provides comments Dario (Qualcomm) proposes to add reference to TS 23.032. Tangqing (China Mobile) provides r01. Shubhranshu (Nokia) asks for clarification Shubhranshu (Nokia) responds Dan (China Mobile) provide r02 Shubhranshu (Nokia) provides r03 Dan(China Mobile) can accept r03 Patrice (Huawei) provides r04 (removal of geographical areas) and r05 (coarser geographical areas). Shubhranshu (Nokia) is OK with r04 ==== Revisions Deadline ==== Dario (Qualcomm) has issues with r04. 'area of validity' is unclear (should be removed). Other revisions are not acceptable. Shubhranshu (Nokia) agrees to r04, but after removing areas of validity in table 6.8.1-1 Dan (China Mobile) OK with r04+ removing 'area of validity ' in table 6.8.1-1 Patrice (Huawei) is OK with r04 + removing the row in table 6.8.1-1 with 'Area of validity'. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306222 | CR | Approval | 23.548 CR0140R1 (Rel-18, 'B'): Clarification for geographic area in DNAI mapping | China Mobile | Rel-18 | Revision of S2-2305084r04, merging S2-2305371 and S2-2305369. Approved | Agreed | |
| 9.17.2 | S2-2305085 | CR | Approval | 23.548 CR0141 (Rel-18, 'B'): NEF and UDR service update for geographic are to support for DNAI mapping | China Mobile | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2306223 (as 23.502 CR4161). | Shubhranshu (Nokia) comments Dario (Qualcomm) supports Shubhranshu's proposal to focus on 5084 first. Dan (China Mobile) provide r01 to be alignment with 548 CR. Patrice (Huawei) proposes r02 to match with 5084r04. Shubhranshu (Nokia) ok with r02 ==== Revisions Deadline ==== Dario (Qualcomm) comments as is OK w/ r02. Tangqing (China Mobile) is ok with r02. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2306223 | CR | Approval | 23.502 CR4161 (Rel-18, 'B'): NEF and UDR service update for geographic are to support for DNAI mapping | China Mobile | Rel-18 | Revision of S2-2305085r02 (23.502 CR4161). Approved. | Agreed | |
| 9.17.2 | S2-2305369 | CR | Approval | 23.548 CR0143 (Rel-18, 'B'): Updates to DNAI mapping information | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2306222 | Dan (China Mobile) suggest to merge this paper into 5084 and comment Dario (Qualcomm) comments. Shubhranshu (Nokia) comments Patrice (Huawei) clarifies that this CR is considered as merged in 5084, and no longer progressed separately. Shubhranshu (Nokia) ok to merge ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.17.2 | S2-2305371 | CR | Approval | 23.502 CR4156 (Rel-18, 'B'): Updates to DNAI mapping information | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2306222 | Dan (China Mobile) suggest to merge this paper into 5085 Shubhranshu (Nokia) comments Tangqing (China Mobile) reply to Shubhranshu. Shubhranshu (Nokia) responds Dario (Qualcomm) comments. Shubhranshu (Nokia) Ok to merge into 5085 ==== Revisions Deadline ==== Shubhranshu (Nokia) merge this into 5085 (and not to 5084), 5085 is 23.502 CR ==== Comments Deadline ==== | Merged |
| 9.17.2 | - | - | - | General | - | - | Docs:=1 | - | |
| 9.17.2 | S2-2304977 | CR | Approval | 23.501 CR4447 (Rel-18, 'D'): Support for Edge Computing DNAI mapping update | Huawei (rapporteur) | Rel-18 | Approved | Agreed | |
| 9.17.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=13 | - | |
| 9.17.2 | S2-2304715 | CR | Approval | 23.548 CR0123 (Rel-18, 'B'): KI#1 EDI provision for HR-SBO | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2305053 | CR | Approval | 23.548 CR0138 (Rel-18, 'F'): Secure DNS in 23.548 | Sony | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304690 | CR | Approval | 23.548 CR0119 (Rel-18, 'B'): CR 23548 Support packet buffering and EAS IP replacement for roaming cases | vivo | Rel-18 | CR Cover sheet error!. Confirm CR Number - CR states xxx! | NOT HANDLED | |
| 9.17.2 | S2-2304653 | CR | Approval | 23.502 CR4046 (Rel-18, 'C'): 23.502 Update on SMF/UPF selection based on common DNAI | CATT | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304786 | CR | Approval | 23.548 CR0129 (Rel-18, 'F'): Correction on UL CL/BP insertion | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304787 | CR | Approval | 23.548 CR0130 (Rel-18, 'B'): KI5 23.501 SMF determining target AF ID | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.17.2 | S2-2304158 | CR | Approval | 23.548 CR0113 (Rel-18, 'B'): DNAI mapping based on conclusions in TR 23.700-48 | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304159 | CR | Approval | 23.502 CR3972 (Rel-18, 'B'): Removing ENs for KI#7 | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304162 | CR | Approval | 23.548 CR0114 (Rel-18, 'C'): Including a latency parameter related to DNAI mapping | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304163 | CR | Approval | 23.502 CR3973 (Rel-18, 'C'): Including a latency parameter related to DNAI mapping | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304978 | CR | Approval | 23.548 CR0133 (Rel-18, 'B'): Resolving ENs on DNAI mapping | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304979 | CR | Approval | 23.502 CR4090 (Rel-18, 'B'): Resolving ENs on DNAI mapping | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.17.2 | S2-2304686 | CR | Approval | 23.501 CR4376 (Rel-18, 'B'): Update for supporting Edge in 23.501 | vivo | Rel-18 | NOT HANDLED | ||
| 9.18.1 | - | - | - | Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) | - | - | Docs:=0 | - | |
| 9.18.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | Docs:=50 | - | |
| 9.18.2 | - | - | - | KI#1 related papers | - | - | Docs:=10 | - | |
| 9.18.2 | S2-2303948 | LS In | Action | Reply LS on Proposed method for Time Synchronization status reporting to UE(s) | RAN WG2 (R2-2302106) | Rel-18 | Noted | Devaki (Nokia) proposes to note this LS. | Noted |
| 9.18.2 | S2-2303955 | LS In | Action | Reply LS on proposed method for time synchronization status reporting to UE(s) | RAN WG3 (R3-230811) | Rel-18 | Noted | Devaki (Nokia) proposes to note this LS. | Noted |
| 9.18.2 | S2-2304124 | CR | Approval | 23.501 CR4216 (Rel-18, 'C'): Addressing ENs on timing synchronization status reporting | Ericsson | Rel-18 | CC#4: r12 + changes agreed. Revised to S2-2306224. Baseline for KI#1 TS 23.501 | Shabnam (Ericsson) provides comments and r01 providing merged version and some resolutions needed as per offline discussion Devaki (Nokia) comments. Jari (NTT DOCOMO) comments. Yuan Tao (CATT) comments. Jari (NTT DOCOMO) responds to Yuan Tao Lufeng.Han(Spreadtrum) comments and provides rev02. Jari (NTT DOCOMO) responds to Lufeng.Han Qianghua (Huawei) provides comments Shabnam (Ericsson) provides comments with r03 Devaki (Nokia) provides r04 Yuan Tao (CATT) replies to Jari (NTT DOCOMO). Sebastian (Qualcomm) provides r05 Runze (Huawei) provides r06 Sebastian (Qualcomm) is not OK with r06 and replies to Runze Runze (Huawei) replies to Sebastian (Qualcomm). Shabnam (Ericsson) provides comments with r07 Devaki (Nokia) provides r09 Jari (NTT DOCOMO) provides r10 (r08 and r09 are in the server, but no email) Devaki (Nokia) provides r09 (link for it). Sebastian (Qualcomm) provides r12 (please ignore r11) Lufeng.Han(Spreadtrum) provides comments on r12 for clarification. Runze (Huawei) comments on 'the clock quality acceptance criteria provided by the AF' Shabnam (Ericsson) provides comments and r13 Sebastian (Qualcomm) objects to r13 Shabnam (Ericsson) provides response Sebastian (Qualcomm) replies to Shabnam (Ericsson) ==== Revisions Deadline ==== Shabnam (Ericsson) objects to r11, r12, comments that Ericsson is ok to open the discussion and potential input from UE internal error reporting which we brought up during study phase but we are NOT ok to have the wrong assumption in the specifications that leads to misleading services assumption. Sang-Jun (Samsung) proposes to go with r10 Sebastian (Qualcomm) is ok with r12 and objects to other versions; can also be ok with r12 with the following change: Replace NOTE X by ' NOTE X: In this release, UE capabilities and internal inaccuracies are assumed to be budgeted by the client network operator when agreeing the required clock accuracy with the 5G network operator. ' Shabnam (Ericsson) let's go forward with r12 + text proposed by Sebastian, I uploaded r14 in CC#3 folder. Some comments: Devaki (Nokia) comments that we agree to go with r12 with text proposed by Sebastian. Thanks for the way forward. Runze (Huawei) proposed to agree r12 + text proposed by Sebastian + RAN internal process in NOTE3 of table Table 5.27.1.12-1. Shabnam (Ericsson) let's go forward with r12 + text proposed by Sebastian+ text proposed by Runze, I uploaded r15 in CC#3 folder. Sebastian (Qualcomm) ok to go forward with r12 + text proposed by Sebastian+ text proposed by Runze, Devaki (Nokia) ok to go forward with r12 + text proposed by Sebastian+ text proposed by Runze. ==== Comments Deadline ==== Shabnam (Ericsson) provides comments that to align 23.501 CR with what we agreed in 23.502 (doc 05210), I will remove highlighted text when uploading, as discussed offline: 'If the UE is instructed by AMF (via the Registration procedure, the UE Configuration Update procedure, or via DL NAS TRANSPORT message) to reconnect to the network in the case when the UE determines that the reference report ID has changed or based on UE local configuration, the UE in the RRC_INACTIVE or RRC_IDLE state, if supported by the UE, reconnects to the network. RAN may delay or prioritize UE's transition to the RRC_CONNECTED state using the UAC framework [28], i.e., UEs are not expected to transition to the RRC_CONNECTED state immediately after determining that the clock quality information has changed and receiving instructions from the AMF. After the UE has reconnected to the network, the gNB uses unicast RRC signaling to provision the clock quality information to the UEs.' | Revised |
| 9.18.2 | S2-2306224 | CR | Approval | 23.501 CR4216R1 (Rel-18, 'C'): Addressing ENs on timing synchronization status reporting | Ericsson, Nokia, Nokia Shanghai Bell, NTT DoCoMo, Samsung, Huawei, ZTE | Rel-18 | Revision of S2-2304124r12r12 + changes. CC#4: Approved | Agreed | |
| 9.18.2 | S2-2305210 | CR | Approval | 23.502 CR4130 (Rel-18, 'B'): Procedures to support network timing synchronization status and reporting | Nokia, Nokia Shanghai Bell, NTT DOCOMO | Rel-18 | r10 agreed. Revised to S2-2306225, merging S2-2305034 Baseline for KI#1 TS 23.502 | Devaki (Nokia) provides r01, merges content from 5167, 4125, 5034. Jari (NTT DOCOMO) provides r02 Shabnam (Ericsson) provides comments with r03, added Ericsson as supporting company. Josep (Deutsche Telekom) comments, provides r04, co-signs. Jari (NTT DOCOMO) comments Sebastian (Qualcomm) comments on r04 and provides r05 Devaki (Nokia) provides r07. Please ignore r06 as I had to update further on top of r06. Jari (NTT DOCOMO) provides r08 Shabnam (Ericsson) asks clarification on added condition by QC on clause 4.15.9.X.X step 4. Shabnam (Ericsson) provides r09 clarifying the text in question below Sebastian (Qualcomm) provides r10 Shabnam (Ericsson) comments that no it is not clear why UE local configuration would be part of this function as initially asked, so can you please explain my original question then? Sebastian (Qualcomm) replies to Shabnam ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that we would like to wait to add this last minute change since to me there is no reason then for AMF to not indicate notification. We have not discussed this before and as such prefer to approve a version without this change now and can discuss during May meeting. So r09 or r10 without the text 'or based on UE local configuration' is acceptable way forward. Devaki (Nokia) also agrees with r09 or r10 without 'or based on UE local configuration'. Hope we don't lose the progress for such a huge CR for this change. Runze (Huawei) supports Devaki (Nokia)'s view, can either agree with r09 or r10 without 'or based on UE local configuration'. Sebastian (Qualcomm) is ok with r10 without ' or based on UE local configuration ' ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306225 | CR | Approval | 23.502 CR4130R1 (Rel-18, 'B'): Procedures to support network timing synchronization status and reporting | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Ericsson, Deutsche Telekom, ZTE | Rel-18 | Revision of S2-2305210r10, merging S2-2305034. Approved | Agreed | |
| 9.18.2 | S2-2305032 | CR | Approval | 23.501 CR4466 (Rel-18, 'F'): Corrections for the configuration of Report ID | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! Postponed | Jari (NTT DOCOMO) comments Runze (Huawei) replies to Jari (DCM) Shabnam (Ericsson) provides comments that we are not ready to go forward with this proposal for SIB at this time, comments that rest can be considered merged Devaki (Nokia) comments. Jari (NTT DOCOMO) comments. Shabnam (Ericsson) provides comments that we can discuss further between now and May meeting and we can also leave it up to operators to decide and RAN to document since that is where it will belong, if to be mandated. ==== Revisions Deadline ==== Runze (Huawei) thanks Shabnam (Ericsson) and fine to postpone the paper. Runze (Huawei) replies to Devaki (Nokia)'s comments. Runze (Huawei) replies to Jari (NTT DOCOMO). Devaki (Nokia) comments - minor correction to the example. Runze (Huawei) thanks Devaki (Nokia) for the explanation and propose to continue with this issue offline. ==== Comments Deadline ==== | Postponed |
| 9.18.2 | S2-2305034 | CR | Approval | 23.502 CR4096 (Rel-18, 'B'): Adding the procedures for 5GS network timing synchronization status reporting. | Huawei, HiSilicon | Rel-18 | Merged into S2-2306225 | Devaki (Nokia) proposes to consider this CR as merged with S2-2305210. Sebastian (Qualcomm): can the author please confirm that this paper is merged into 5210? Runze (Huawei) agrees this paper is merged into 5210. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.18.2 | S2-2304655 | CR | Approval | 23.503 CR0929R1 (Rel-18, 'B'): Support of time synchronization status reporting | CATT | Rel-18 | Revision of S2-2302985 from S2#155. r02 agreed. Revised to S2-2306226. Baseline for KI#1 TS 23.503 | Yuan Tao (CATT) provides r01. Runze (Huawei) provides comments. Shabnam (Ericsson) provides comments Devaki (Nokia) comments. Yuan Tao (CATT) replies. Yuan Tao (CATT) provides r02. ==== Revisions Deadline ==== Runze (Huawei) is ok with r02. ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306226 | CR | Approval | 23.503 CR0929R2 (Rel-18, 'B'): Support of time synchronization status reporting | CATT | Rel-18 | Revision of S2-2304655r02. Approved | Agreed | |
| 9.18.2 | - | - | - | KI#2 related papers | - | - | Docs:=6 | - | |
| 9.18.2 | S2-2305168 | CR | Approval | 23.501 CR4514 (Rel-18, 'F'): Clarification on the TSCTSF handling when it receives the time sync request from AF and time sync subscription from UDM | ZTE | Rel-18 | r03 agreed. Revised to S2-2306227. | Devaki (Nokia) comments. Jari (NTT DOCOMO) provides r01 Qianghua (Huawei) provides comments Jari (NTT DOCOMO) comments Zhendong (ZTE) prefer option 2. Zhendong (ZTE) provides response. Shabnam (Ericsson) comments that having difficulty understanding the benefit for Option 2 or why we need to change? As such we are not supportive of reopening the solution specified. Zhendong (ZTE) provides clarification on both options. Devaki (Nokia) comments, prefers option 1 based on Zhendong's clarification. Runze(Huawei) replies to the comments. Zhendong (ZTE) provides r02. Zhendong (ZTE) provides response to shabnam. Jari (NTT DOCOMO) provides r03 Zhendong (ZTE) provides comment. Zhendong (ZTE) is fine with r03. Runze (Huawei) asks a question to r03. ==== Revisions Deadline ==== Runze (Huawei) hopes the comments can be answered, or postpone the paper . Jari (NTT DOCOMO) responds to Runze Runze (Huawei) thanks Jari (NTT DOCOMO) for the answer and can live with r03 ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306227 | CR | Approval | 23.501 CR4514R1 (Rel-18, 'F'): Clarification on the TSCTSF handling when it receives the time sync request from AF and time sync subscription from UDM | ZTE, NTT DOCOMO | Rel-18 | Revision of S2-2305168r03. Approved | Agreed | |
| 9.18.2 | S2-2305169 | CR | Approval | 23.502 CR4118 (Rel-18, 'F'): Modification to the UE time synchronization subscription | ZTE | Rel-18 | r03 agreed. Revised to S2-2306228. | Devaki (Nokia) supports the proposal, we had a similar paper for UE time sync subscription that was merged here. So, wishes to cosign. Jari (NTT DOCOMO) comments Zhendong (ZTE) provides r01. Qianghua (Huawei) provides comments on r01 Zhendong (ZTE) provides r02. Shabnam (Ericsson) provides comments on some editorial updates needed Zhendong (ZTE) provides r03. ==== Revisions Deadline ==== Runze(Huawei) supports r03. Josep (Deutsche Telekom) supports r03, would like to co-sign. Please kindly add Deutsche Telekom as co-signer to the revision. ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306228 | CR | Approval | 23.502 CR4118R1 (Rel-18, 'F'): Modification to the UE time synchronization subscription | ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom | Rel-18 | Revision of S2-2305169r03. Approved | Agreed | |
| 9.18.2 | S2-2305211 | CR | Approval | 23.501 CR4525 (Rel-18, 'F'): Correction on the use of Adjust AoI based on RA indicator for the UE mobility event notification | Nokia, Nokia Shanghai Bell | Rel-18 | r04 agreed. Revised to S2-2306229. | Runze (Huawei) provides r01 Shabnam (Ericsson) Ericsson would also like to support this CR. Devaki (Nokia) provides r02 (mainly adding Ericsson on top of r01), r03 (separating the NRF and UDM option to avoid requiring TSCTSF to support both). Prefer r03 Jari (NTT DOCOMO) comments, prefers r00 Shabnam (Ericsson) provides comments to Jari's question Jari (NTT DOCOMO) provides r04 Runze (Huawei) replies to Jari (NTT DOCOMO). Zhendong (ZTE) provides r05. Runze (Huawei) provides r06. Runze (Huawei) replies to Zhendong (ZTE). ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that prefers r05, r06 adding TA 'list' is not correct since RAN feedback to restrict to a gNB and the added text in r06 makes the second change quite difficult to read. Runze (Huawei) replies to Shabnam (Ericsson), and agrees to remove 'list' from r06. Jari (NTT DOCOMO) has a concern on r06 Runze (Huawei) clarifies to Jari (NTT DOCOMO) for his concern in r06 Shabnam (Ericsson) suggests to also go with the original version and then any further changes can be done in May. Devaki (Nokia) is fine with original version but considering the progress, wonders if we can consider r05? Jari (NTT DOCOMO) can agree r00 or r04 Sebastian (Qualcomm) prefers to go with r00 Runze (Huawei) can accept r04 or r05, and objects to other revisions including r00. Devaki (Nokia) wonders if we can progress with r04? Shabnam (Ericsson) provides comments that we can endorse r04 and continue discussion in May? That is why my suggestion & preference is we go with r00 now and I think the UDM approach needs some further work as it will/may not work in all cases and can be separate CR in May. Devaki (Nokia) proposes to go with r04 for approval. We can always revise the paper in May (same sections may be impacted thus different CR could be harder) Runze (Huawei) agrees with Devaki (Nokia) to go with r04 for approval. ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306229 | CR | Approval | 23.501 CR4525R1 (Rel-18, 'F'): Correction on the use of Adjust AoI based on RA indicator for the UE mobility event notification | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, NTT DOCOMO | Rel-18 | Revision of S2-2305211r04. Endorsed | Endorsed | |
| 9.18.2 | - | - | - | KI#3 related papers | - | - | Docs:=1 | - | |
| 9.18.2 | S2-2305037 | CR | Approval | 23.501 CR4469 (Rel-18, 'C'): Clarification for Controlling time synchronization service based on the Subscription | Huawei, HiSilicon | Rel-18 | Noted | Devaki (Nokia) provides r01. Jari (NTT DOCOMO) proposes to merge with S2-2305168 Runze (Huawei) replied to Devaki (Nokia) and provides r02. Josep (Deutsche Telekom) asks questions for clarification. Jari (NTT DOCOMO) objects r02 Sebastian (Qualcomm) objects to the CR (all versions) Runze (Huawei) replies to Josep (Deutsche Telekom). Shabnam (Ericsson) proposes to note this and continue discussion under 05168 as proposed by NTT DoCoMo. Runze (Huawei) is fine to use 5168 for discussion. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.18.2 | - | - | - | KI#5 related papers | - | - | Docs:=5 | - | |
| 9.18.2 | S2-2304052 | CR | Approval | 23.501 CR4196 (Rel-18, 'C'): Resolving (Removing) ENs for TSN TN integration | Nokia, Nokia Shanghai Bell | Rel-18 | r09 agreed. Revised to S2-2306230, merging S2-2304867 | Srinivas Garikipati (Nokia) Updated with the inputs of paper 2304126 Srinivas Garikipati (Nokia) proposes to carry out changes related to EN György (Ericsson) provides r02 Jari (NTT DOCOMO) provides r03 Haiyang (Huawei) provides comments and r04 Srinivas Garikipati (Nokia) provides responses to the comments from Docomo, Ericsson and Huawei. Srinivas Garikipati (Nokia) provides r05 as responses to the comments from Docomo, Ericsson and Huawei. György (Ericsson) provides r06. Jari (NTT DOCOMO) comments Srinivas Garikipati (Nokia) provides r07 as responses to the comments from Docomo and comments for r06 from Ericsson. Srinivas Garikipati (Nokia) provides r08 to include Reference updates and also clarifies comments of Huawei. Srinivas Garikipati (Nokia) provides responses to Jari (NTT DOCOMO) Haiyang (Huawei) comments Srinivas Garikipati (Nokia) provides r09 and also clarifies to Jari (NTT DOCOMO) Srinivas Garikipati (Nokia) provides r10 minor correction. ==== Revisions Deadline ==== Sang-Jun (Samsung) is fine with r09 or r10, and wishes to co-sign. Haiyang (Huawei) suggests to go with r09 György (Ericsson) suggests to go with r09 with the following sentence removed: ,Its absence indicates that stream transformation is performed in the Talker and Listeners of this Steam.' Srinivas Garikipati (Nokia) accepts to go with r09 along with the removal of the sentence 'Its absence indicates that stream transformation is performed in the Talker and Listeners of this Steam' Jari (NTT DOCOMO) agrees to go with r09 with the following sentence removed: ,Its absence indicates that stream transformation is performed in the Talker and Listeners of this Steam.' ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306230 | CR | Approval | 23.501 CR4196R1 (Rel-18, 'C'): Resolving (Removing) ENs for TSN TN integration | Nokia, Nokia Shanghai Bell, Huawei, Samsung | Rel-18 | Revision of S2-2304052r09, merging S2-2304867. Approved | Agreed | |
| 9.18.2 | S2-2304867 | CR | Approval | 23.501 CR4423 (Rel-18, 'B'): KI#5: TN CNC | Samsung | Rel-18 | Merged into S2-2306230 | Laurent (Nokia): this CR may not be needed Jari (NTT DOCOMO) proposes to merge with S2-2304052 Sang-Jun (Samsung) agrees to to merge S2-2304867 with S2-2304052 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.18.2 | S2-2305080 | CR | Approval | 23.501 CR4475 (Rel-18, 'B'): Remove the EN on supporting TSN TN | Huawei, HiSilicon | Rel-18 | r06 agreed. Revised to S2-2306231. | Jari (NTT DOCOMO) proposes to merge with S2-2304052 Haiyang (Huawei) provides r02. Srinivas Garikipati (Nokia) proposed changes related to EN3 (Gate Control information) Srinivas Garikipati (Nokia) provides r03 related to EN3 (Gate Control information) Haiyang (Huawei) comments to r03. Srinivas Garikipati (Nokia) provides responses to Haiyang (Huawei) Haiyang (Huawei) comments. Haiyang (Huawei) provides r04 (for TL option) and r05 (for SMF option). Srinivas Garikipati (Nokia) provides r06 on top of r04 as response to Haiyang (Huawei) Srinivas Garikipati (Nokia) wishes to co-sign based on r06 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306231 | CR | Approval | 23.501 CR4475R1 (Rel-18, 'B'): Remove the EN on supporting TSN TN | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305080r06. Approved | Agreed | |
| 9.18.2 | - | - | - | KI#6 related papers | - | - | Docs:=4 | - | |
| 9.18.2 | S2-2304657 | CR | Approval | 23.501 CR4370 (Rel-18, 'C'): Support of provisioning periodicity set | CATT | Rel-18 | r03 agreed. Revised to S2-2306232. | Devaki (Nokia) supports the proposal, wishes to cosign. Yuan Tao (CATT) replies to Devaki (Nokia) and provides r01. Yuan Tao (CATT) provides r02. Haiyang (Huawei) provides r03. Yuan Tao replies to Haiyang (Huawei) , and suggests to go with r02. Haiyang (Huawei) comments, still prefer r03. ==== Revisions Deadline ==== Yuan Tao (CATT) replies to Haiyang (Huawei). Haiyang (Huawei) comments. Yuan Tao(CATT) replies to Haiyang (Huawei). Sebastian (Qualcomm) is ok with r03 ==== Comments Deadline ==== | Revised |
| 9.18.2 | S2-2306232 | CR | Approval | 23.501 CR4370R1 (Rel-18, 'C'): Support of provisioning periodicity set | CATT, Nokia, Nokia Shanghai Bell, Huawei | Rel-18 | Revision of S2-2304657r03. Approved | Agreed | |
| 9.18.2 | S2-2304451 | CR | Approval | 23.503 CR0971 (Rel-18, 'F'): KI#6 Clarify the AF adjustment for BAT offset and adjusted periodicity on the UL direction | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.18.2 | S2-2304658 | CR | Approval | 23.502 CR4047 (Rel-18, 'C'): Support of provisioning periodicity set | CATT | Rel-18 | Noted | Yuan Tao (CATT) provides r01. Haiyang (Huawei) thinks we do not need 502 CR if we do not change the term. Please see 4657r03 ==== Revisions Deadline ==== Haiyang (Huawei) suggest to note this paper as per discussion in 4657. ==== Comments Deadline ==== | Noted |
| 9.18.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=23 | - | |
| 9.18.2 | S2-2304849 | CR | Approval | 23.501 CR4416 (Rel-18, 'B'): KI#1: Info elements and Clock quality acceptance | Samsung | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2304853 | CR | Approval | 23.501 CR4420 (Rel-18, 'B'): KI#1: Report ID per gNB | Samsung | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2304855 | CR | Approval | 23.501 CR4421 (Rel-18, 'B'): KI#1: Support for RRC_INACTIVE and RRC_IDLE states | Samsung | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305033 | CR | Approval | 23.501 CR4467 (Rel-18, 'C'): Corrections for the description of network timing synchronization status reporting | Huawei, HiSilicon | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305102 | CR | Approval | 23.501 CR4483 (Rel-18, 'F'): Clarification for Clock quality reporting control information | Spreadtrum Communications | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305103 | CR | Approval | 23.501 CR4484 (Rel-18, 'F'): Providing clock quality metrics to UE | Spreadtrum Communications | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2304125 | CR | Approval | 23.502 CR3969 (Rel-18, 'B'): Time synchronization status reporting | Ericsson | Rel-18 | Merge with S2-2305210 | NOT HANDLED | |
| 9.18.2 | S2-2305209 | CR | Approval | 23.501 CR4524 (Rel-18, 'C'): Functional updates and clarifications for network timing synchronization status and reporting | Nokia, Nokia Shanghai Bell, NTT DOCOMO | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305166 | CR | Approval | 23.501 CR4513 (Rel-18, 'F'): Resolve the issue on whether the report id is broadcasted always or not | ZTE | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305167 | CR | Approval | 23.502 CR4117 (Rel-18, 'B'): Adding the timing synchronization status reporting to AMF and tsctsf service operation. | ZTE | Rel-18 | Merge with S2-2305210 | NOT HANDLED | |
| 9.18.2 | S2-2305212 | CR | Approval | 23.502 CR4131 (Rel-18, 'F'): Corrections to the AF Request Authorization Information for Time Synchronization | Nokia, Nokia Shanghai Bell | Rel-18 | Merged with S2-2305169 | NOT HANDLED | |
| 9.18.2 | S2-2305165 | CR | Approval | 23.501 CR4512 (Rel-18, 'F'): Clarification on the status report according to RAN WG feedback | ZTE | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2304411 | CR | Approval | 23.501 CR4303 (Rel-18, 'F'): AF request Authorization | NTT DOCOMO | Rel-18 | CR Cover sheet error! Merge with S2-2305168 | NOT HANDLED | |
| 9.18.2 | S2-2304654 | CR | Approval | 23.501 CR4369 (Rel-18, 'C'): Update on time synchronization status reporting | CATT | Rel-18 | Merge with S2-2304124 | NOT HANDLED | |
| 9.18.2 | S2-2305031 | DISCUSSION | Agreement | TRS key issue 1 open issues | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2304656 | DISCUSSION | Discussion | Discussion on the Time Synchronization status reporting | CATT | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2304051 | CR | Approval | 23.502 CR3956 (Rel-18, 'C'): Update the references to the new IEEE Std 802.1Q-2022, in regards to KI#5 | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2304050 | CR | Approval | 23.501 CR4195 (Rel-18, 'C'): Updating references to new IEEE Std 802.1Q-2022 and IEEE P802.1Qdj | Nokia, Nokia Shanghai Bell | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2304126 | CR | Approval | 23.501 CR4217 (Rel-18, 'C'): Resolve editor s note on indication of TEID and QFI to the TN CNC | Ericsson | Rel-18 | György (Ericsson) proposes this document to be merged into S2-2304052. | NOT HANDLED | |
| 9.18.2 | S2-2305035 | CR | Approval | 23.501 CR4468 (Rel-18, 'C'): Corrections for the description of requested coverage area for time synchronization service | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2305036 | CR | Approval | 23.502 CR4097 (Rel-18, 'C'): Corrections for the procedures of requested coverage area for time synchronization service | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.18.2 | S2-2304659 | CR | Approval | 23.503 CR0985 (Rel-18, 'C'): Support of provisioning periodicity set | CATT | Rel-18 | NOT HANDLED | ||
| 9.18.2 | S2-2305038 | CR | Approval | 23.502 CR4098 (Rel-18, 'C'): Corrections for the procedures of controlling time synchronization service based on the subscriptionCorrections for the procedures of controlling time synchronization service based on the subscription | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.19.1 | - | - | - | Study on Vehicle Mounted Relays (FS_VMR) | - | - | Docs:=0 | - | |
| 9.19.2 | - | - | - | Vehicle Mounted Relays (VMR) | - | - | Docs:=42 | - | |
| 9.19.2 | - | - | - | MBSR Authorization and deauthorization | - | - | Docs:=2 | - | |
| 9.19.2 | S2-2304056 | DISCUSSION | Discussion | Discussion on MBSR authorization indication and update | KPN | Rel-18 | Noted | Noted | |
| 9.19.2 | S2-2304179 | DISCUSSION | Agreement | IAB-node release and authorization change | Ericsson | Rel-18 | Noted | Hong (Qualcomm) comments. Qian (Ericsson) provides comments. Nassima (KPN) provides comments. Alessio(Nokia) provides comments. Qian (Ericsson) provides further comments. Xiaoyan Shi (Intel) provides comments. Hong (Qualcomm) comments and tries to summary points. Alessio(Nokia) comments on the Hong (Qualcomm) summary points. Hong (Qualcomm) provides comments. Nassima (KPN) comments. Xiaoyan Shi (Intel) comments. Hong (Qualcomm) proposes to have a compromise of supporting both deregistration/re-registration & UCU, to allow the operator having the tools they prefer to use based on network operation policies. Nassima (KPN) is OK with compromise solution, provides r04 of S2-2304053. Qian (Ericsson) provides comment and consider UCU approach shall be checked with RAN WG first. Alessio(Nokia) comments that this is in scope of SA2. Hence disagrees with Ericsson. We are fine with compromise if this let's us move forward. Provides 4053 r05 to back the compromise up Nassima (KPN) provides comments, supports the UCU option, can live with compromise solution, not OK with only de-registration. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | - | - | - | MBSR Authorization and deauthorization - TS 23.501 CRs | - | - | Docs:=5 | - | |
| 9.19.2 | S2-2304053 | CR | Approval | 23.501 CR4197 (Rel-18, 'C'): MBSR Authorization Update | KPN N.V. | Rel-18 | Noted | Alessio (nokia) provides r01 merging the relevant aspects of Nokia CR and adding some more considerations. LaeYoung (LGE) provides comment. Qian (Ericsson) provides comments. Xiaoyan Shi (Intel) provides comments on r01 LiMeng (Huawei) provides comments. Nassima (KPN) responds to comments, provides r02. Hong (Qualcomm) comments. LaeYoung (LGE) provides r03. Alessio(Nokia) Agrees with Hong (Qualcomm) comment. We need to have NAS state machine to control the MBSR IAB-UE operation. Remember the NG-RAN may not support MBSR ubiquitously in the network and the 5GMM indication and the authorization state can help to handle the MBSR IAB UE also where RAN does not support too. Alessio(Nokia) comments that r02,r03 introduce the notion that subscription is a necessary but not sufficient condition to obtain service. But I would not be happy to say that this is a systematic thing , only if exceptional circumstances happen and maybe we can say which they are... and this is not only or roaming UEs. Hence for now I would keep this outside the CR and come back next meeting with more details? So for now we prefer r01. Nassima (KPN) agrees that the MBSR roaming use case needs to be discussed further in the next meeting, and is OK with r01 for now Xiaoyan Shi (Intel) comments. Nassima (KPN) provides r04 of S2-2304053 with a compromise solution. Alessio(Nokia) is not ok with r04 as it seems the MBSR started to handover UEs but not clear based on what input... also the indication from CU of donor is not supported. If we had a compromise this would be a local AMF decision without any indication from RAN. Also the cause code should be specified as what prevents the UE from attempting to register again as MBSR in infinite loop? Qian (Ericsson) cannot agree with any of the revisions and provides comments. Alessio(nokia) provides r05 Nassima (KPN) provides comments, supports r05 as a way forward. LiMeng (Huawei) comments that the last paragraph of 4053 is not fully correct. Alessio(nokia) provides r06 to address LiMeng (Huawei) comments that the last paragraph of 4053 is not fully correct. ==== Revisions Deadline ==== Xiaoyan Shi (Intel) objects all revisions since the MBSR capability indication is still in NAS message which is duplicated info and makes 5GC complicated. Qian (Ericsson) share the same concern and objects all revisions. ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304180 | CR | Approval | 23.501 CR4227 (Rel-18, 'F'): IAB authorization change handling | Ericsson | Rel-18 | Noted | Nassima (KPN) comments and proposes to merge into r04 of S2-2304053 which proposes a compromise solution to merge both baselines. Alessio(Nokia) also proposes to note this paper. If we specify both options the deregistration case needs to have no additional requirements from RAN and a precise definition of the Ue behaviour at subsequent registration so it does not cause an infinite loop. Qian (Ericsson) provides comments and r01 considering the merge of 4736, 5332 Alessio(Nokia) comments it is not acceptable to just use deregistration option. Also this cR is incomplete from a specification standpoint as UE behavior is left unspecified. Nassima (KPN) also cannot accept using deregistration only. ==== Revisions Deadline ==== Qian (Ericsson) responds and ask to go with r01. Alessio(Nokia) unfortunately thinks this CR quality is not acceptable to be ready for agreement hence asks this to be noted. We need to work together offline before next meeting Nassima (KPN) objects to all revisions. Proposes to note and discuss further offline. ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304736 | CR | Approval | 23.501 CR4392 (Rel-18, 'B'): Clarification on MBSR Authorization | Huawei, HiSilicon | Rel-18 | Merged into S2-2304180 (noted) Merge into S2-2304180 | Hong (Qualcomm) comments and proposes to merge it with S2-2304180. LiMeng (Huawei) supports Hong's proposal to merge the document. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2305328 | CR | Approval | 23.501 CR4552 (Rel-18, 'F'): Authorization information indication to UE. | Samsung | Rel-18 | Merge intoS2-2304053 (noted). Merge into (revision of) S2-2304053 | Hong (Qualcomm) comments and proposes to merge it with S2-2304053. Lalith (Samsung) OK to merge it with S2-2304053. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2305332 | CR | Approval | 23.501 CR4103R2 (Rel-18, 'B'): MBSR authorization update | Intel, Ericsson | Rel-18 | Revision of S2-2301451 from S2-154AHE. Merged into S2-2304180 (noted) Merge into S2-2304180 | Hong (Qualcomm) comments and proposes to merge it with S2-2304180. Xiaoyan Shi (Intel) is ok to merge this CR with S2-2304180. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | - | - | - | MBSR Authorization and deauthorization - TS 23.502 CRs | - | - | Docs:=5 | - | |
| 9.19.2 | S2-2304700 | CR | Approval | 23.502 CR4058 (Rel-18, 'B'): Support of VMR configuration and authorization | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Wrong TS number. Confirm Specification Number - CR states 23.501! Noted | Nassima (KPN) provides r01 and co-signs. Alessio(nokia) provides r02 and thanks Nassima for the update. We are ok with it , just we prefere the 'reasons' for update to be described in 501. So we refer to 501 for those. LaeYoung (LGE) provides comment. Alessio(Nokia) provides r03 Nassima (KPN) is ok with r03. Alessio(Nokia) provides r04 that incorporates some changes from 4181 Qian (Ericsson) provides comments and cannot agree to any of the revisions. ==== Revisions Deadline ==== Xiaoyan Shi (Intel) objects all revisions and proposes to postpone this CR to next meeting since we cannot get an agreement on the NAS impact. Qian (Ericsson) share the same concern and objects all revisions. ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304055 | CR | Approval | 23.502 CR3957 (Rel-18, 'C'): MBSR Authorization Update | KPN N.V. | Rel-18 | Merged into S2-2304700 (noted) Merge into S2-2304700 | Hong (Qualcomm) comments and proposes to merge it with S2-2304700. Nassima (KPN) supports proposal to merge the document into S2-2304700. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2305361 | CR | Approval | 23.502 CR4154 (Rel-18, 'F'): MBSR authorization. | Samsung | Rel-18 | Merged into S2-2304700 (noted) Merge into S2-2304700 | Hong (Qualcomm) comments and proposes to merge it with S2-2304700. Lalith(Samsung) OK to merge it with S2-2304700. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304181 | CR | Approval | 23.502 CR3686R1 (Rel-18, 'B'): Mobile IAB authorization | Ericsson | Rel-18 | Revision of S2-2300226 from S2#154AHE. Noted | LiMeng (Huawei) comments on the subscription data in UDM. Hong (Qualcomm) comments. Xiaoyan Shi (Intel) provides r01. LiMeng (Huawei) provides r02. Lalith (Samsung) comments. Alessio(Nokia) proposes to merge into 4700r04 - mark this paper merged into 4700 ==== Revisions Deadline ==== Qian (Ericsson) comments that paper is the basic part of the registration procedure while 4700 has extra contents that can't be agreed at this moment, proposes to go with r02 Alessio(Nokia) unfortunately thinks this CR quality (and content) is not acceptable to be ready for agreement hence asks this to be noted. We need to work together offline before next meeting ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2305335 | CR | Approval | 23.502 CR4149 (Rel-18, 'B'): TS23.502 MBSR authorization | Intel Ireland | Rel-18 | MergeD into S2-2304181 (Noted) Merge into S2-2304181 | Hong (Qualcomm) comments and proposes to merge it with S2-2304181. Xiaoyan Shi (Intel) is ok to merge this CR with S2-2304181. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | - | - | - | MBSR configuration (w/ roaming support) | - | - | Docs:=4 | - | |
| 9.19.2 | S2-2303971 | LS In | Action | LS from SA WG3: Reply LS on secured and trusted access to the serving PLMN OAM server by a MBSR | SA WG3 (S3-231400) | Rel-18 | Noted | Noted | |
| 9.19.2 | S2-2304699 | CR | Approval | 23.501 CR4380 (Rel-18, 'C'): Update of the UE configuration and UE authorization clauses | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Qian (Ericsson) provides comments Alessio(Nokia) replies Hong (Qualcomm) comments. LiMeng (Huawei) suggests this document to focus on clause 5.35A.2, and merge 5.35A.4 to 4053. Alessio(nokia) provides r01 to focus on clause 5.35A.2 Qian (Ericsson) provides comments and has concerns with several aspects ==== Revisions Deadline ==== Hong (Qualcomm) asks if r01 is the correct revision uploaded. Xiaoyan Shi (Intel) proposes to postpone this CR. LiMeng (Huawei) suggests to postpone this CR. Qian (Ericsson) suggests also to postpone this CR since the content in r01 should be 5.35A.2 not 5.35A.4. Alessio(Nokia) confirms there was a mistake ?. Please see what I should have uploaded in the DRAFTS (link below) Alessio(Nokia) asks to fix error via CC#3 discussion if possible Qian (Ericsson) comments the context in the revision in the draft folder is not ok and still propose to postpone ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304735 | CR | Approval | 23.501 CR4391 (Rel-18, 'B'): Update of MBSR Configuration | Huawei, HiSilicon | Rel-18 | r00 agreed. Revised to S2-2305627. CC#4: Postponed | Alessio(Nokia) proposes to merge this into 4699r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.19.2 | S2-2305627 | CR | Approval | 23.501 CR4391R1 (Rel-18, 'B'): Update of MBSR Configuration | Huawei, HiSilicon | Rel-18 | Revision of S2-2304735r00. Approved. CC#4: WITHDRAWN | Withdrawn | |
| 9.19.2 | - | - | - | Allowed CAG list with location restriction | - | - | Docs:=10 | - | |
| 9.19.2 | S2-2304642 | CR | Approval | 23.501 CR4366 (Rel-18, 'B'): Allowed CAG list with location restrictions | Qualcomm Incorporated | Rel-18 | Noted | Pallab (Nokia) provides comments. Qian (Ericsson) provides comments. Pallab (Nokia) responds ==== Revisions Deadline ==== Hong (Qualcomm) suggests handling this in CC#3, as part of SoH for VMR (together w/ S2-2304091, and S2-2304644r02) ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304090 | CR | Approval | 23.501 CR4202 (Rel-18, 'C'): Clarify the allowed CAG list with validity condition | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305628, merging S2-2304593 | Hong (Qualcomm) comments and suggests removing the NOTE 1a. Myungjune (LGE) provides r01 and co-signs. LiMeng (Huawei) comments on r01. Myungjune (LGE) replies to LiMeng (Huawei) Peter Hedman (Ericsson) provides comments LiMeng (Huawei) agrees that the if AMF doesn't support validity information, the better way is to not provide such CAG entry. Guanzhou (InterDigital) comments. Hong (Qualcomm) comments. Xiaoyan Shi (Intel) comments. Myungjune (LGE) comments. Peter Hedman (Ericsson) provides r02 Myungjune (LGE) provides r03. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with any revision, suggests to approve r03 ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305628 | CR | Approval | 23.501 CR4202R1 (Rel-18, 'C'): Clarify the allowed CAG list with validity condition | Ericsson, LG Electronics | Rel-18 | Revision of S2-2304090r03, merging S2-2304593. Approved | Agreed | |
| 9.19.2 | S2-2304091 | CR | Approval | 23.501 CR4203 (Rel-18, 'C'): Allowed CAG list with location validity | Ericsson | Rel-18 | Noted | Pallab (Nokia) provides comments. Qian (Ericsson) provides comments. ==== Revisions Deadline ==== Hong (Qualcomm) suggests handling this in CC#3, as part of SoH for VMR (together w/ S2-2304642, and S2-2304644r02) ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304093 | DISCUSSION | Agreement | Access control of location validity associated with entries of Allowed CAG list. | Ericsson | Rel-18 | Noted | Hong (Qualcomm) comments. Qian (Ericsson) provides comments. Xiaoyan Shi (Intel) comments. Pallab (Nokia) provides comments. Pallab (Nokia) provides further comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304593 | CR | Approval | 23.501 CR4352 (Rel-18, 'C'): Modification of AN release condition due to update of Allowed CAG list | LG Electronics | Rel-18 | Merged into S2-2305628 | Hong (Qualcomm) comments and suggests merging into S2-2304090. Peter Hedman (Ericsson) provides comments and noted that LGE agreed to merge the CR into 4090 Myungjune (LGE) is ok to merge the CR into 4090 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.19.2 | S2-2304594 | CR | Approval | 23.502 CR4034 (Rel-18, 'C'): Modification of AN release condition due to update of Allowed CAG list | LG Electronics | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305629. | Peter Hedman (Ericsson) provides comments Xiaoyan Shi (Intel) provides comments Myungjune (LGE) replies to Peter (Ericsson) and Xiaoyan Shi (Intel) and provides r01. Peter Hedman (Ericsson) provides r02 Xiaoyan Shi (Intel) is fine with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305629 | CR | Approval | 23.502 CR4034R1 (Rel-18, 'C'): Modification of AN release condition due to update of Allowed CAG list | LG Electronics, Ericsson | Rel-18 | Revision of S2-2304594r02. Approved | Agreed | |
| 9.19.2 | S2-2304486 | CR | Approval | 23.502 CR4018 (Rel-18, 'F'): Correction on CAG information in UE subscription and UE context | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2305630. | Peter Hedman (Ericsson) provides comments Xiaoyan Shi (Intel) provides comments Yishan (Huawei) provides r01. Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305630 | CR | Approval | 23.502 CR4018R1 (Rel-18, 'F'): Correction on CAG information in UE subscription and UE context | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304486r02. Approved | Agreed | |
| 9.19.2 | - | - | - | New topic on paging optimization impacts | - | - | Docs:=3 | - | |
| 9.19.2 | S2-2304661 | DISCUSSION | Discussion | VMR impact on paging optimizations | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.19.2 | S2-2304664 | CR | Approval | 23.501 CR4373 (Rel-18, 'B'): Paging optimization support during full Migration of MBSR | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Qian (Ericsson) provides comments Alessio(Nokia) replies Xiaoyan Shi (Intel) comments and proposes to postpone this contribution. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.19.2 | S2-2304677 | CR | Approval | 23.502 CR4050 (Rel-18, 'B'): Paging optimization support during full Migration of MBSR | Nokia, Nokia Shanghai Bell | Rel-18 | Confirm Specification Number - CR states 23.501! Postponed | Qian (Ericsson) indicates that the comments for this paper are similar to 4664. Alessio(Nokia) see our reply in 4664 thread. Xiaoyan Shi (Intel) comments and proposes to postpone this contribution. ==== Revisions Deadline ==== Qian (Ericsson) also proposes to postpone this contribution. ==== Comments Deadline ==== | Postponed |
| 9.19.2 | - | - | - | Additional ULI support | - | - | Docs:=6 | - | |
| 9.19.2 | S2-2303963 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR solutions review | RAN WG3 (R3-231011) | Rel-18 | Noted | Noted | |
| 9.19.2 | S2-2304182 | CR | Approval | 23.501 CR4228 (Rel-18, 'C'): Additional User Location Information | Ericsson | Rel-18 | r01 agreed. Revised to S2-2305631, merging S2-2305018 and S2-2304738 Baseline | Alessio(Nokia) provides r01 ==== Revisions Deadline ==== Hong (Qualcomm) would like to check if S2-2304182r01 should be used as baseline or this CR, as they are overlapping. Hongsuk (LGE) is ok to merge the CR(S2-2305018) into S2-2304182r01 ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305631 | CR | Approval | 23.501 CR4228R1 (Rel-18, 'C'): Additional User Location Information | Ericsson | Rel-18 | Revision of S2-2304182r01, merging S2-2305018 and S2-2304738. Approved | Agreed | |
| 9.19.2 | S2-2304738 | CR | Approval | 23.501 CR4394 (Rel-18, 'B'): Providing cell ID/TAC of MBSR for services | Huawei, HiSilicon | Rel-18 | Merged into S2-2305631 Merge into S2-2304182 | Alessio(Nokia ) commitments this CR is unacceptable as it removes the existing that that works 5018 or 4182 ==== Revisions Deadline ==== Qian (Ericsson) comments that this paper shall be considered as merged into 4182 ==== Comments Deadline ==== | Merged |
| 9.19.2 | S2-2305018 | CR | Approval | 23.501 CR4458 (Rel-18, 'B'): Providing ULI of IAB-UE for services using location reference | LG Electronics | Rel-18 | Merged into S2-2305631 Merge into S2-2304182 | Alessio(Nokia) provides r01 to correct a mistake (RRC connection indication not F1) ==== Revisions Deadline ==== Hongsuk (LGE) suggests to merge this CR(S2-2305018) into S2-2304182r01 ==== Comments Deadline ==== | Merged |
| 9.19.2 | S2-2305041 | CR | Approval | 23.502 CR4099 (Rel-18, 'B'): Providing user location information of MBSR to the AMF | Huawei, HiSilicon | Rel-18 | Approved | Qian (Ericsson) provides comments Hong (Qualcomm) comments. Xiaoyan Shi (Intel) comments. Alessio(Nokia) suggests to postpone to next meeting this 502 topic LiMeng (Huawei) responds. ==== Revisions Deadline ==== LiMeng (Huawei) agrees with the proposal from the rapporteur and suggests to go with r00. ==== Comments Deadline ==== | Agreed |
| 9.19.2 | - | - | - | Overall TS 23.501 EN clean up | - | - | Docs:=2 | - | |
| 9.19.2 | S2-2304644 | CR | Approval | 23.501 CR4367 (Rel-18, 'B'): Open issue resolutions for MBSR support | Qualcomm Incorporated | Rel-18 | r02 agreed. Revised to S2-2305632. | Hong (Qualcomm) provides r01 for potential SoH for CAG location restriction discussion. Alessio(nokia) provides r02 focusing on the CAG issue (the rest is covered in 4699 and 4053). Qian (Ericsson) provides comments that location validity can be further discuss in next meeting. ==== Revisions Deadline ==== Hong (Qualcomm) suggests handling this in CC#3, as part of SoH for VMR (together w/ S2-2304642, and S2-2304091) ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305632 | CR | Approval | 23.501 CR4367R1 (Rel-18, 'B'): Open issue resolutions for MBSR support | Qualcomm Incorporated | Rel-18 | Revision of S2-2304644r02. Approved | Agreed | |
| 9.19.2 | - | - | - | TS 23.273 Location Service support and NRPPa enhancements | - | - | Docs:=5 | - | |
| 9.19.2 | S2-2304678 | CR | Approval | 23.273 CR0339 (Rel-18, 'C'): Update of the Location Services involving Mobile Base Station Relay | Nokia, Nokia Shanghai Bell, Sony | Rel-18 | CR Cover sheet error! r02 agreed. Revised to S2-2305633, merging S2-2304913 | Qian (Ericsson) provides comments Hong (Qualcomm) comments. Alessio(Nokia) replies LiMeng (Huawei) provides r01 with merging S2-2304913 . Alessio(nokia) thanks li meng for the compromise and provides r02. Changes in yellow and a comment on a reinstated text that was deleted in r01 ==== Revisions Deadline ==== Hong (Qualcomm) comments and suggest correct Work Item Code on cover page when generating the final version. ==== Comments Deadline ==== | Revised |
| 9.19.2 | S2-2305633 | CR | Approval | 23.273 CR0339R1 (Rel-18, 'B'): Update of the Location Services involving Mobile Base Station Relay | Nokia, Nokia Shanghai Bell, Sony | Rel-18 | Revision of S2-2304678r02, merging S2-2304913. Approved | Agreed | |
| 9.19.2 | S2-2304913 | CR | Approval | 23.273 CR0351 (Rel-18, 'B'): Update of MT-LR procedure for when a MBSR is involved in the location of a UE | Huawei, HiSilicon | Rel-18 | Merged into S2-2305633 | Hong (Qualcomm) comments. Alessio(Nokia) agrees with Hong's comments and suggests that the CR is noted or merged in the nokia 4678 CR to have one discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.19.2 | S2-2305076 | CR | Approval | 23.273 CR0363 (Rel-18, 'F'): Update the positioning procedure of a target UE involving MBSR | CATT | Rel-18 | Noted | Lars (Sony) comments. Hong (Qualcomm) comments and propose to NOTE the CR. ==== Revisions Deadline ==== Yunjing (CATT) replies. ==== Comments Deadline ==== | Noted |
| 9.19.2 | S2-2304646 | CR | Approval | 23.273 CR0334 (Rel-18, 'F'): Clarification on conditions for privacy check for MBSR | Qualcomm Incorporated | Rel-18 | Approved | Agreed | |
| 9.20.1 | - | - | - | Study on the support for 5WWC Phase 3 (FS_5WWC_Ph2) | - | - | Docs:=0 | - | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) | - | - | Docs:=51 | - | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / General (LS) | - | - | Docs:=3 | - | |
| 9.20.2 | S2-2303917 | LS In | Action | LS from BBF: BBF answer to your liaison S2-2207761 solutions for 5WWC_Ph2 Key Issue 1 | BBF (LIAISE-562-05) | Revision of postponed S2-2302184 from S2#155. Response drafted in S2-2305015. Postponed | Postponed | ||
| 9.20.2 | S2-2303919 | LS In | Information | LS from CableLabs: Feedbacks on solutions for 5WWC_Ph2 Key Issue 1 | CableLabs (CableLabs LS Response on 3GPP Rel-18 5WWC_Ph2) | Revision of postponed S2-2302193 from S2#155. Response drafted in S2-2305015. Postponed | Laurent (Nokia): please don't NOTE this Ls but POSTPONE it (as 5015 is also POSTPONED° | Postponed | |
| 9.20.2 | S2-2305015 | LS OUT | Approval | [DRAFT] LS on progress of 5WWC_Ph2 normative work | Nokia, Nokia Shanghai Bell | Rel-18 | Response to S2-2303917 and S2-2303919. Postponed | Marco (Huawei) propose to postpone the LS to May meeting Yishan (Huawei) comments Stefan (Ericsson) supports to postpone. Laurent (Nokia): supports to postpone ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / KI1 3GPP UE | - | - | Docs:=10 | - | |
| 9.20.2 | S2-2304768 | LS OUT | Approval | [DRAFT] LS on Support of NSWO for 3GPP UE behind 5G-RG | Huawei, Hisilicon | Rel-18 | Postponed | Sriram(CableLabs) comments and provides r01. Sriram(CableLabs) comments and provides r01 with the correct tag. ==== Revisions Deadline ==== Marco (Huawei) proposes to Postpone to May after addition in TS the NSWO with FN-RG support Yildirim (Charter) also proposes to Postpone to May meeting because the corresponding CR to be attached to the LS has not been finalized yet. Laurent (Nokia): supports postponing the LS ==== Comments Deadline ==== | Postponed |
| 9.20.2 | S2-2304263 | CR | Approval | 23.316 CR2087 (Rel-18, 'B'): New feature for 5G-RG to support NSWO procedure to authorize UE behind RG | China Telecom | Rel-18 | r10 agreed. Revised to S2-2305634. | Laurent (Nokia): provides r01 Marco (Huawei) provides r02 merging with S2-234767 (HW) Stefan (Ericsson) comments and provides r03 Sriram(CableLabs) comments and provides r04 Marco (Huawei) asks clarification to Sriram(CableLabs) Sriram(CableLabs) replies to Marco (Huawei). Laurent (Nokia): provides r05 (and claen r06) based on r03 Sebastian (Qualcomm) provides r07 Sriram(CableLabs) replies to Laurent and provides r08 Marco (Huawei) object r08 and addition of FN-RG. Provide r09 on top of r07. Yildirim (Charter) comments and supports 5G NSWO support for FN-RG Jing (China Telecom) suggests to focus on adding 5G-RG in this meeting. marco (Huawei) propose to limit to 5G-RG in this meeting and add FN-RG in next meeting. Sriram(CableLabs) replies to Marco and seeks clarification. Yildirim (Charter) replies to Marco (Huawei) and Jing (China Telecom) Marco (Huawei) provide r10 Sriram(CableLabs) replies to Marco and offer r11 ( built on top of r08). ==== Revisions Deadline ==== Marco (Huawei) OK with R11, R10 objects R00,R01, R03, R04, r08 Yildirim (Charter) is OK with r08. If r08 cannot be agreed, can live with r11 to progress and discuss open aspects at the next meeting. Ojas (Comcast) prefers r08 but as compromise can support r11 Laurent (Nokia): objects to R00, R01, R02, R03, R04, R10, R11; can live with R10 if we remove a sentence Sriram(CableLabs) prefers r08. Can progress forward with r11. ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305634 | CR | Approval | 23.316 CR2087R1 (Rel-18, 'B'): New feature for 5G-RG to support NSWO procedure to authorize UE behind RG | China Telecom, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304263r10. Approved | Agreed | |
| 9.20.2 | S2-2304116 | CR | Approval | 23.316 CR2085 (Rel-18, 'B'): Differentiation for UEs behind 5G-RG | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305635. | Laurent (Nokia): provides r01 Suresh Srinivasan (Intel) provides r02 Stefan (Ericsson) provides comments and provides r03 ==== Revisions Deadline ==== Marco (Huawei) ok for R03 Laurent (Nokia): objects to R00 and R02 Suresh Srinivasan (Intel) is ok with r03 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305635 | CR | Approval | 23.316 CR2085R1 (Rel-18, 'B'): Differentiation for UEs behind 5G-RG | Ericsson, Nokia, Nokia Shanghai Bell, Intel | Rel-18 | Revision of S2-2304116r03. Approved | Agreed | |
| 9.20.2 | S2-2305099 | CR | Approval | 23.316 CR2097 (Rel-18, 'B'): 5G-RG ID provided in Trusted Non-3GPP access procedure | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2305636. | Laurent (Nokia): provides r01 Stefan (Ericsson) provides r02 Laurent (Nokia): Suggests that we document the call flow and changes UE's policy control subscription information related with the TNAP ID feature only in 23.316. Suresh Srinivasan (Intel) provides r03 Laurent (Nokia): Comments Marco (Huawei) I disagree to removal of 5G-RG ID from any version, but for seek of progress discuss separately. Provide r04 Stefan (Ericsson) comments Laurent (Nokia): provides r05 Marco (Huawei) comment r05. ==== Revisions Deadline ==== Marco (Huawei) OK with R05 Suresh Srinivasan (Intel) is ok with r05 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305636 | CR | Approval | 23.316 CR2097R1 (Rel-18, 'B'): 5G-RG ID provided in Trusted Non-3GPP access procedure | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Intel | Rel-18 | Revision of S2-2305099r05. Approved | Agreed | |
| 9.20.2 | S2-2304500 | CR | Approval | 23.502 CR4022 (Rel-18, 'B'): 5G-RG ID provided in Trusted Non-3GPP access procedure | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2305637. | Laurent (Nokia): Comments Yishan (Huawei) replies to Laurent (Nokia) Stefan (Ericsson) provides comments Laurent (Nokia): provides r01 (you may skip) and R02 Marco (Huawei) thanks Laurent (Nokia) for R02 Stefan (Ericsson) provides r03 Yishan (Huawei) comments Yishan (Huawei) provides r04 to correct the wording. ==== Revisions Deadline ==== Marco (Huawei) ok with R04 Laurent (Nokia): objects to R00. .R03/R04 are the best versions ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305637 | CR | Approval | 23.502 CR4022R1 (Rel-18, 'B'): 5G-RG ID provided in Trusted Non-3GPP access procedure | Huawei, HiSilicon | Rel-18 | Revision of S2-2304500r04. Approved | Agreed | |
| 9.20.2 | S2-2304117 | CR | Approval | 23.503 CR0951 (Rel-18, 'B'): Location based policies for trusted non-3GPP access | Ericsson | Rel-18 | Noted | Laurent (Nokia): Comments Marco (Huawei) comment considering 5099 Stefan (Ericsson) replies to Marco Laurent (Nokia): provides r01 ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc that is redundant with 4119 (and 23.316 is a better place for this information) ==== Comments Deadline ==== | Noted |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / KI1 AUN3 | - | - | Docs:=2 | - | |
| 9.20.2 | S2-2304480 | CR | Approval | 23.316 CR2091 (Rel-18, 'B'): Support of AUN3 device | Huawei, HiSilicon | Rel-18 | Noted. CC#4: r14 agreed. Revised to S2-2306261. | Yishan (Huawei) provides r01 Laurent (Nokia): provides r02 Dieter (Deutsche Telekom): comments current solution is unacceptable as long as it is not ensured that when the network releases the PDU Session for the RG or deregisters the RG that all PDU Sessions/registrations for devices behind the RG are also released/deregistered. Yishan (Huawei) replies to Dieter (Deutsche Telekom) Sriram(CableLabs) provides r03. Dieter (Deutsche Telekom): provides r04 based on r02. Stefan (Ericsson) comments and provides r05 Sriram(CableLabs) comments and provides r06 Sriram(CableLabs) comments and provides r07 Yildirim (Charter) comments and supports Sriram (CableLabs) for the motivation behind including support for AUN3 devices behind FN-RG. Laurent (Nokia): I am going to produce an as clean as possible R08 based on R06 Sebastian (Qualcomm) comments Laurent (Nokia): provides r08 (you can skip it) and R09 Marco (Huawei): comments on FN-RG Marco (Huawei) provide r10 on top of r09 Yildirim (Charter) provides r11 (based on r10) updating the ULI aspect of AUN3 device. Stefan (Ericsson) provides r12 Sriram(CableLabs) provides r13 (based on r12) adding support for AUN3 device served by FN-RG. Laurent (Nokia): provides r14 (built on R12) Sriram(CableLabs): replies to Marco and provides r15 (built on R14) Marco (Huawei) comment from r12 to R14. Question to Stepan (Ericsson) Marco (Huawei) thanks Sriram(CableLabs) to have added the EN. Stefan (Ericsson) replies to Marco Stefan (Ericsson) provides question to Marco and Sriram Marco (Huawei) answer to Stefan (Ericsson) Sriram(CableLabs) replies to Stefan (Ericsson). ==== Revisions Deadline ==== Marco (Huawei) OK R15, 14 object R13, R11 and any version R03-R09 Dieter (Deutsche Telekom) can accept to technically endorse R14 or 15 as a basis for further work at the next meeting but certainly not agree on any version of this CR ... Laurent (Nokia): objects to R3+R6+R7+R13+R15. Prefer to approve R14 but OK to endorse R14 if we cannot do more Yildirim (Charter) ok with r15. Also fine with endorsing it as base for the next meeting. Stefan (Ericsson) objects to r00-r11. Prefers r14. OK to endorse r14 if it cannot be approved. Sebastian (Qualcomm) is ok with r14/r15 Sriram(CableLabs) is OK with r15 only. Stefan (Ericsson) Update: objects to r00-r11, r13, r15. Prefers r14. OK to endorse r14 if it cannot be approved. ==== Comments Deadline ==== Marco (Huawei) proposes to approve R15 considering that in any case the proposal needs to be discussed and agreed per regular process | Revised |
| 9.20.2 | S2-2306261 | CR | Approval | 23.316 CR2091R1 (Rel-18, 'B'): Support of AUN3 device | Huawei, HiSilicon, | Rel-18 | Revision of S2-2304480r14. CC#4: Approved | Agreed | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / KI1 AUN3+NAUN3 | - | - | Docs:=5 | - | |
| 9.20.2 | S2-2304771 | CR | Approval | 23.501 CR4403 (Rel-18, 'B'): N3GPP device definitions | Huawei, Hisilicon | Rel-18 | CR Cover sheet error! Merged into S2-2305638 | Laurent (Nokia): *suggests* to move forward with 5205 revisions (23.316 CR) and to Note this paper (23.501 CR) Marco (Huawei) reply and disagree with Laurent (Nokia): Yildirim (Charter) expresses preference on TS 23.316 CR for the sake of progress. Marco (Huawei) for sake of progress ok to merge with 5205 and go to 23.316. If needed we may come back in May. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.20.2 | S2-2305205 | CR | Approval | 23.316 CR2098 (Rel-18, 'B'): Non-3GPP Device Category Definitions | CableLabs | Rel-18 | CC#4: r04 + changes agreed. Revised to S2-2305638, merging S2-2304771 | Laurent (Nokia): provides r01. proposes to have the definitions in 23.316 Marco (Huawei) comments Marco (Huawei). proposes to have the definitions in 23.501 and ask clarifications on revised definition Dieter (Deutsche Telekom): comments that for the definitions it must be clear that those devices are connected only via Non-3GPP access to an RG. Omkar (CableLabs) responds to Marco (Huawei) Yildirim (Charter) comments/questions. Omkar (CableLabs) comments Marco (Huawei) comments and propose r03 Laurent (Nokia): provides r04 Marco (Huawei) provide r05 Omkar (CableLabs) responds to Marco and Laurent and provide r06. Dieter (Deutsche Telekom): comments. Yildirim (Charter): provides r07 (based on r06). Omkar (CableLabs) responds to Dieter (Deutsche Telekom) and provides r08 (on top of r04). Yildirim (Charter): provides r09 (based on r08). ==== Revisions Deadline ==== Marco (Huawei) ok with r09 Dieter (Deutsche Telekom) ok with r04, objects to all other revisions. Yildirim (Charter) prefers r09. Also, 'may' in the NOTE can be replaced with 'can' as Dieter (Deutsche Telekom) pointed out. Omkar (CableLabs) prefers r09 with an updated NOTE to address Dieter (Deutsche Telekom) concerns. ==== Comments Deadline ==== Laurent (Nokia): thinks the proposal from Dieter is a good compromise: R04 + extra NOTE 2: An AUN3 or NAUN3 device can operate as a 5G UE over NG-RAN, if the device implements in addition 5G UE functionality. Marco (Huawei) : R04 has the approved version and prefer to keep it. We can revise definitions afterward also as Cat F. Laurent (Nokia) : let's stick to R04 this is the safe side | Revised |
| 9.20.2 | S2-2305638 | CR | Approval | 23.316 CR2098R1 (Rel-18, 'B'): Non-3GPP Device Category Definitions | CableLabs, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305205r04 + changes, merging S2-2304771. CC#4: Approved | Agreed | |
| 9.20.2 | S2-2304469 | CR | Approval | 23.503 CR0973 (Rel-18, 'B'): URSP for authenticable and non- authenticable non-3GPP (AUN3/NAUN3) devices connected behind a 5G-RG | Nokia, Nokia Shanghai-Bell | Rel-18 | Confirm CR Number - CR states {{No CR number}}! r07 agreed. Revised to S2-2305639. | Marco (Huawei) express concern and asks question Stefan (Ericsson) provides comments Laurent (Nokia): provides r01 Sebastian (Qualcomm) provides r02 Marco (Huawei) object r00, r001 and comment r02 Marco (Huawei) comment why AUN3 is not needed. Sebastian (Qualcomm) provides r03 Sriram(CableLabs) provides r04 ( built on top of r03). Sebastian (Qualcomm) provides r05 Marco (Huawei) provides r06 Laurent (Nokia): provides r07 ==== Revisions Deadline ==== Marco (Huawei) ok with r07, r06 and objects r00-r04 Dieter (Deutsche Telekom) ok with r07, r06 and objects r00-r04 Laurent (Nokia): much prefers R07 Stefan (Ericsson) prefers r07, comments that some editorial fixing is needed, and please add Ericsson as co-signer Sebastian (Qualcomm) is ok with r07, objects to r00, r01, r04 ==== Comments Deadline ==== Laurent (Nokia): I am OK to do the editorial change proposed by Ericsson | Revised |
| 9.20.2 | S2-2305639 | CR | Approval | 23.503 CR0973R1 (Rel-18, 'B'): URSP for authenticable and non- authenticable non-3GPP (AUN3/NAUN3) devices connected behind a 5G-RG | Nokia, Nokia Shanghai-Bell, Ericsson | Rel-18 | Revision of S2-2304469r07. Approved | Agreed | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / KI1 generic | - | - | Docs:=2 | - | |
| 9.20.2 | S2-2304089 | CR | Approval | 23.316 CR2082 (Rel-18, 'B'): Introducing non-3GPP QoS assistance information | Qualcomm, Nokia, Nokia Shanghai Bell | Rel-18 | r04 agreed. Revised to S2-2305640. | Sriram(CableLabs) comments and provides r01 Sebastian (Qualcomm) replies to Sriram Yishan (Huawei) asks for clarification Sebastian (Qualcomm) replies to Yishan Laurent (Nokia): supports Sebastian's points Marco (Huawei) concerns on FN-RG and W-AGF role. Provide r02 Dieter (Deutsche Telekom): shares the concerns of Marco, Sebastian and Laurent regarding the how this could work for the FN-RG case. Sebastian (Qualcomm) provides r03 Sriram( CableLabs) replies to Sebastian (Qualcomm), Marco, Dieter. Marco (Huawei) replies to Sriram( CableLabs) Sriram(CableLabs) replies to Marco (Huawei). Laurent(Nokia) has the same SHARED concerns on FN-RG and W-AGF role Laurent (Nokia): provides r04 ==== Revisions Deadline ==== Marco (Huawei) ok with r04 , object r02 Laurent (Nokia): objects to any version except R00 and R04 Yildirim (Charter) OK with r03 or r02 because non-3GPP QoS assistance information can be beneficial for FN-RG + W-AGF deployments. Sebastian (Qualcomm) understands the desire to support FN-RG but in the conclusion in TR 23.700-17 we stated 'this applies for 5G RG only;'; FN-RG support has also not been studied for this Sebastian (Qualcomm) therefore proposes to go ahead with r04 Sriram (CableLabs) OK with r03 or r02. ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305640 | CR | Approval | 23.316 CR2082R1 (Rel-18, 'B'): Introducing non-3GPP QoS assistance information | Qualcomm, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304089r04. Approved | Agreed | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / NAUN3 | - | - | Docs:=4 | - | |
| 9.20.2 | S2-2305266 | CR | Approval | 23.316 CR2099 (Rel-18, 'B'): Differentiated service for NAUN3 devices connected behind a 5G-RG | Intel | Rel-18 | r06 agreed. Revised to S2-2305641. | Stefan (Ericsson) provides r01 Yishan (Huawei) provides comments Sebastian (Qualcomm) replies to Yishan Laurent (Nokia): provides r02 and R03 Sebastian (Qualcomm) comments on r02/r03 Yildirim (Charter) comments on r02/r03 Yildirim (Charter) provides r04 Sebastian (Qualcomm) provides r05 Stefan (Ericsson) provides r06 ==== Revisions Deadline ==== Marco (Huawei) ok R06 and objects any other version Yildirim (Charter) OK with r04. can live with r06. Ojas (Comcast) OK with r04. Could also live with r06. Sriram(CableLabs) prefers r04. Can live with r06. Suresh Srinivasan (Intel) is ok with r06 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305641 | CR | Approval | 23.316 CR2099R1 (Rel-18, 'B'): Differentiated service for NAUN3 devices connected behind a 5G-RG | Intel, Nokia, Nokia Shanghai-Bell, Ericsson | Rel-18 | Revision of S2-2305266r06. Approved. NOTE: This file was replaced on the server to show revision marks. | Agreed | |
| 9.20.2 | S2-2304119 | CR | Approval | 23.316 CR2086 (Rel-18, 'B'): Support for AF influence on TNAP ID | Ericsson | Rel-18 | r04 agreed. Revised to S2-2305642. | Laurent (Nokia): provides r01 Marco (Huawei) comments and provide r02 Stefan (Ericsson) provides r03 Laurent (Nokia): provides r04 ==== Revisions Deadline ==== Marco (Huawei) ok with r04, object r00 Laurent (Nokia): ok with r04, object to r00 Stefan (Ericsson) ok with r04 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305642 | CR | Approval | 23.316 CR2086R1 (Rel-18, 'B'): Support for AF influence on TNAP ID | Ericsson | Rel-18 | Revision of S2-2304119r04. Approved | Agreed | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) / KI2 | - | - | Docs:=6 | - | |
| 9.20.2 | S2-2304590 | CR | Approval | 23.501 CR4351 (Rel-18, 'F'): Clarification on N3IWF/TNGF selection to support of S-NSSAI needed by UE | LG Electronics | Rel-18 | r04 agreed. Revised to S2-2305643. | Stefan (Ericsson) provides comments Myungjune (LGE) replies to Stefan (Ericsson) Heng (China Telecom) ask for clarification. Yishan (Huawei) comments and provides r01 Myungjune (LGE) is ok with r01 and replies to Yishan (Huawei) Sebastian (Qualcomm) comments and provides r02 Laurent (Nokia): provides r03 Myungjune (LGE) provides r04. Yishan (Huawei) provides r05 and replies to Sebastian (Qualcomm) Sebastian (Qualcomm) replies and objects to r05 Yishan (Huawei) replies to Sebastian (Qualcomm) Marco (Huawei) comment Yishan (Huawei) provides r06 to address the comments from Sebastian (Qualcomm) Myungjune (LGE) asks question on r06. Yishan (Huawei) answers to Myungjune (LGE) and provides r07 to correct the misleading wording. Myungjune (LGE) provides comments and provides r08 Stefan (Ericsson) provides question on r08 Yishan (Huawei) provides r09 and r10 to address the comments from Laurent (Nokia) and Stefan (Ericsson) Myungjune (LGE) provides r11 Myungjune (LGE) provides r12 ==== Revisions Deadline ==== Yishan (Huawei) is ok with r10 and r12 Sebastian (Qualcomm) is ok with r02-r04, objects to all other versions. Yishan (Huawei) questions to Sebastian (Qualcomm) Myungjune (LGE) proposes r04 + two EN: 'Editor's Note: it is FFS whether and how to deal with a legacy UE that does not support N3IWF selection based on the slices the UE wishes to use' & 'Editor's Note: it is FFS whether and how to deal with a legacy UE that does not support TNGF selection based on the slices the UE wishes to use' Sebastian (Qualcomm) is not OK with proposal by Myungjune (LGE) Myungjune (LGE) proposes to agree r04. Yishan (Huawei) is fine to go with r04 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305643 | CR | Approval | 23.501 CR4351R1 (Rel-18, 'F'): Clarification on N3IWF/TNGF selection to support of S-NSSAI needed by UE | LG Electronics, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304590r04. Approved | Agreed | |
| 9.20.2 | S2-2304470 | CR | Approval | 23.502 CR4015 (Rel-18, 'B'): AMF/PCF interactions to support TNGF/N3IWF selection enhancement for support of S-NSSAI needed by UE | Nokia, Nokia Shanghai Bell | Rel-18 | r09 agreed. Revised to S2-2305644. | Ashok (Samsung) requests for clarification Heng (China Telecom) shares same view as Ashok. Myungjune (LGE) provides comments Stefan (Ericsson) provides comments Yishan (Huawei) provides r01 Heng (China Telecom) provides r02 Laurent (Nokia): provides r03 Myungjune (LGE) provides r04 Stefan (Ericsson) provides r05 Stefan (Ericsson) questions on r05 Heng (China Telecom) clarify to Laurent (Nokia) on r02 Heng (China Telecom) provides r06 Laurent (Nokia): provides r07 Laurent (Nokia): provides r08 Stefan (Ericsson) provides r09 ==== Revisions Deadline ==== Myungjune (LGE) comments on last visited TA. Heng(China Telecom) replys to Myungjune (LGE). Myungjune (LGE) replies to Heng(China Telecom) Heng(China Telecom) replies to Myungjune (LGE). Myungjune (LGE) replies to Heng(China Telecom). Myungjune (LGE) prefer r08 but can live with r09. Heng (China Telecom) replies. Yishan (Huawei) is ok with r09 Laurent (Nokia): objects to R01+R02+R03+R04+R05+R06 Laurent (Nokia): OK with R09 (better than R08) but asks an extra sentence to be added Sebastian (Qualcomm) can only accept r09 if the following statements are removed 'if the registration request contains an indication that the UE supports N3IWF selection based on the slices the UE wishes to use over untrusted non-3GPP access,' AND 'if the registration request contains an indication that the UE supports TNGF selection based on the slices the UE wishes to use over trusted non-3GPP access,'; objects to all other versions ==== Comments Deadline ==== Heng (China Telecom) suggests to agree r09 with added sentence proposed by Laurent and removed sentence proposed by Sebastian in previous email. Yishan (Huawei) suggest to discuss in CC#4 to agree r09 with following revision: 1. In step 12 in clause 4.12.2.2, remove 'if the registration request contains an indication that the UE supports N3IWF selection based on the slices the UE wishes to use over untrusted non-3GPP access,', and add below the step 12 'the AMF behavior when the UE does not support slice-based N3IWF selection, is defined in TS 23.501 clause 6.3.6.1'. 2. In step 15 in clause 4.12a.2.2, remove 'if the registration request contains an indication that the UE supports TNGF selection based on the slices the UE wishes to use over trusted non-3GPP access,' and add below the step 15 'the AMF behavior when the UE does not support slice-based TNGF selection, is defined in TS 23.501 clause 6.3.12.2' Sebastian (Qualcomm) is not ok with proposal by Yishan | Revised |
| 9.20.2 | S2-2305644 | CR | Approval | 23.502 CR4015R1 (Rel-18, 'B'): AMF/PCF interactions to support TNGF/N3IWF selection enhancement for support of S-NSSAI needed by UE | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304470r09. Approved | Agreed | |
| 9.20.2 | S2-2304471 | CR | Approval | 23.503 CR0974 (Rel-18, 'B'): AMF/PCF Policy Control Trigger for TNGF/N3IWF selection enhancement based on support of S-NSSAI needed by UE | Nokia, Nokia Shanghai-Bell | Rel-18 | r02 agreed. Revised to S2-2305645. | Stefan (Ericsson) provides comments Heng (China Telecom) share the same view as Stefan (Ericsson) Laurent (Nokia): answers Stefan (Ericsson) replies to Laurent Stefan (Ericsson) provides r01 Laurent (Nokia): provides r02 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r02. But, if possible, wants to update very last sentence. Laurent (Nokia): OK to update the last sentence. We can also remove the content of the () i.e. remove '(e.g. WLANSP or ANDSP)' ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2305645 | CR | Approval | 23.503 CR0974R1 (Rel-18, 'B'): AMF/PCF Policy Control Trigger for TNGF/N3IWF selection enhancement based on support of S-NSSAI needed by UE | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304471r02. Approved | Agreed | |
| 9.20.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=19 | - | |
| 9.20.2 | S2-2304118 | CR | Approval | 23.502 CR3967 (Rel-18, 'B'): Support for AF influence on TNAP ID | Ericsson | Rel-18 | Merge into S2-2304500 | NOT HANDLED | |
| 9.20.2 | S2-2304499 | CR | Approval | 23.503 CR0976 (Rel-18, 'B'): Update on policy control subscription data in UDR | Huawei, HiSilicon | Rel-18 | Merge into S2-2304117 | NOT HANDLED | |
| 9.20.2 | S2-2304770 | DISCUSSION | Agreement | N3GPP device definitions | Huawei, Hisilicon | Rel-18 | NOT HANDLED | ||
| 9.20.2 | S2-2304769 | DISCUSSION | Information | Is URSP improvement for 5G-RG required? | Huawei, Hisilicon | Rel-18 | NOT HANDLED | ||
| 9.20.2 | S2-2305267 | CR | Approval | 23.316 CR2100 (Rel-18, 'B'): Differentiated services for UE devices behind 5G-RG and FN-RG | Intel | Rel-18 | No revision marks shown! Merge into S2-2304116 | NOT HANDLED | |
| 9.20.2 | S2-2304767 | CR | Approval | 23.316 CR2096 (Rel-18, 'B'): Support of NSWO for 3GPP UE behind 5G-RG | Huawei, HiSilicon | Rel-18 | Merge into S2-2304263 | NOT HANDLED | |
| 9.20.2 | S2-2304540 | CR | Approval | 23.503 CR0982 (Rel-18, 'C'): URSP handling for NAUN3 devices behind the 5G-RG | Qualcomm | Rel-18 | Merge into S2-2304469 | NOT HANDLED | |
| 9.20.2 | S2-2304120 | CR | Approval | 23.502 CR3968 (Rel-18, 'B'): Delivery of N3IWF and TNGF selection policies to UE | Ericsson | Rel-18 | Merge into S2-2304470 | NOT HANDLED | |
| 9.20.2 | S2-2304498 | CR | Approval | 23.502 CR4021 (Rel-18, 'B'): Clarification on Registration procedure over Non-3GPP access | Huawei, HiSilicon | Rel-18 | Merge into S2-2304470 | NOT HANDLED | |
| 9.20.2 | S2-2304591 | CR | Approval | 23.502 CR4032 (Rel-18, 'F'): Clarification on N3IWF/TNGF selection to support of S-NSSAI needed by UE | LG Electronics | Rel-18 | Merge into S2-2304470 | NOT HANDLED | |
| 9.20.2 | S2-2305272 | CR | Approval | 23.502 CR4139 (Rel-18, 'B'): Update to 4.12.2.2 to resolve ENs and issue of target N3IWF determination | China Telecommunications | Rel-18 | CR Cover sheet error! Merge into S2-2304470 | NOT HANDLED | |
| 9.20.2 | S2-2305274 | CR | Approval | 23.502 CR4140 (Rel-18, 'B'): Update to 4.12a.2.2 to resolve EN and issue of target TNAN determination | China Telecom | Rel-18 | Merge into S2-2304470 | NOT HANDLED | |
| 9.20.2 | S2-2304468 | CR | Approval | 23.316 CR2089 (Rel-18, 'B'): Providing differentiated service for authenticable non-3GPP (AUN3) devices connected behind a 5G-RG | Nokia, Nokia Shanghai-Bell | Rel-18 | Merge into S2-2304480 | NOT HANDLED | |
| 9.20.2 | S2-2304743 | CR | Approval | 23.316 CR2093 (Rel-18, 'B'): Providing differentiated service for authenticable non-3GPP (AUN3) devices connected behind a 5G-RG and FN-RG | CableLabs, [Nokia, Nokia Shanghai-Bell], Broadcom, Charter(?), Comcast(?), Rogers(?), Meta(?), Intel(?) | Rel-18 | Merge into S2-2304480 | NOT HANDLED | |
| 9.20.2 | S2-2304481 | CR | Approval | 23.501 CR4323 (Rel-18, 'F'): Clarification on slice-based N3IWF/TNGF selection | Huawei, HiSilicon | Rel-18 | Merge into S2-2304590 | NOT HANDLED | |
| 9.20.2 | S2-2304472 | CR | Approval | 23.501 CR4321 (Rel-18, 'B'): Clarification on TNGF identifiers | Nokia, Nokia Shanghai Bell | Rel-18 | Merge into S2-2304590 | NOT HANDLED | |
| 9.20.2 | S2-2304473 | CR | Approval | 23.316 CR2090 (Rel-18, 'B'): Definition of AUN3 and NAUN3 devices | Nokia, Nokia Shanghai-Bell | Rel-18 | Merge into S2-2305205 | NOT HANDLED | |
| 9.20.2 | S2-2304115 | CR | Approval | 23.316 CR2084 (Rel-18, 'B'): Differentiation for NAUN3 devices behind 5G-RG | Ericsson | Rel-18 | Merge into S2-2305266 | NOT HANDLED | |
| 9.20.2 | S2-2304467 | CR | Approval | 23.316 CR2088 (Rel-18, 'B'): Providing differentiated service for Non authenticable (NAUN3) devices connected behind a 5G RG | Nokia, Nokia Shanghai-Bell | Rel-18 | Merge into S2-2305266 | NOT HANDLED | |
| 9.21 | - | - | - | Stage 2 of MPS_WLAN (MPS_WLAN) | - | - | Docs:=6 | - | |
| 9.21 | S2-2305118 | CR | Approval | 23.401 CR3731 (Rel-18, 'F'): MPS when access to EPC is WLAN correction | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | Approved | Agreed | |
| 9.21 | S2-2305128 | CR | Approval | 23.402 CR3000 (Rel-18, 'F'): MPS when access to EPC is WLAN corrections | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | Approved | Agreed | |
| 9.21 | S2-2305129 | CR | Approval | 23.501 CR4491 (Rel-18, 'F'): MPS when access to 5GC is WLAN corrections | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | r01 agreed. Revised to S2-2305646. | Pallab (Nokia) provides comments Haris(Qualcomm) comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.21 | S2-2305646 | CR | Approval | 23.501 CR4491R1 (Rel-18, 'F'): MPS when access to 5GC is WLAN corrections | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | Revision of S2-2305129r01. Approved | Agreed | |
| 9.21 | S2-2305130 | CR | Approval | 23.502 CR4111 (Rel-18, 'F'): MPS when access to 5GC is WLAN corrections | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | r02 agreed. Revised to S2-2305647. | Pallab (Nokia) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.21 | S2-2305647 | CR | Approval | 23.502 CR4111R1 (Rel-18, 'F'): MPS when access to 5GC is WLAN corrections | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-18 | Revision of S2-2305130r02. Approved | Agreed | |
| 9.22.1 | - | - | - | Study on 5G AM Policy (FS_AMP) | - | - | Docs:=0 | - | |
| 9.22.2 | - | - | - | 5G AM Policy (AMP) | - | - | Docs:=0 | - | |
| 9.23.1 | - | - | - | Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) | - | - | Docs:=0 | - | |
| 9.23.2 | - | - | - | Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | - | - | Docs:=148 | - | |
| 9.23.2 | - | - | - | Key Issue #1: How to improve correctness of NWDAF analytics | - | - | Docs:=34 | - | |
| 9.23.2 | S2-2304536 | DISCUSSION | Discussion | Discussion on Enhancement of Analytics Transfer due to Analytics Accuracy check support | Huawei, HiSilicon | Rel-18 | Noted | Zhang (Ericsson) provides comments Haiyang (Huawei) clarifies to Zhang (Ericsson). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.23.2 | S2-2304754 | DISCUSSION | Information | Discussion on Accuracy Information | vivo | Rel-18 | Noted | Zhang (Ericsson) provides comments Xiaobo (vivo) replies to Zhang(Ericsson)'s comments and call for more comments. Dimitris (Lenovo) comments Antoine (Orange) comments. Xiaobo (vivo) thanks Antoine(Orange) for very detailed explanation, which does help the discussion and propose to move the discussion to 4755(corresponding CR) . ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.23.2 | S2-2304031 | CR | Approval | 23.288 CR0730 (Rel-18, 'B'): Resolving ENs in AnLF assisted ML model accuracy monitoring | Ericsson | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2304057 | CR | Approval | 23.288 CR0702R1 (Rel-18, 'B'): Adding Data Source Information in the Contents of ML Model Provisioning | Lenovo Future Communications, Orange | Rel-18 | Revision of S2-2302429 from S2#155. Postponed | Soohwan (ETRI) asks questions for clarification. Soohwan (ETRI) ask a question for clarification. Zhang (Ericsson) provides comments and indicate the CR is not based on the latest version of TS 23.288 Costas (Lenovo) response to Zhang (Ericsson) and provides r02 ==== Revisions Deadline ==== Soohwan (ETRI) proposes to postpone Costas (Lenovo) replies to Soohwan (ETRI) and proposes to add EN and discuss in CC#4 ==== Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2304076 | CR | Approval | 23.288 CR0737 (Rel-18, 'C'): Timestamp of action taken by analytics consumer | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Check clauses affected! r01 agreed. Revised to S2-2306068. | Zhang (Ericsson) provides comments Fabio (Nokia) replies to comments and provides r01 Xiaobo (vivo) support the CR and would like to co-sign it. Soohwan (ETRI) requests to add ETRI a co-source company. Zhang (Ericsson) also co-sign the paper Antoine (Orange) asks the justification for not adding the expected duration. Antoine (Orange) provides r02 adding the expected duration and co-signers. Xiaobo (vivo) support r02 by adding the expected duration. Fabio (Nokia) asks for clarification. Fabio (Nokia) provides r03 Zhang (Ericsson) provide comments Antoine (Orange) provides r04 based on r03 removing illegal 'should' in Note :-) ==== Revisions Deadline ==== Dimitris (Lenovo) supports r04 and co-signs Zhang (Ericsson) accept r01 and object all other versions Bahador (NTT DOCOMO) accepts r01 and objects to all other versions. Xiaobo (vivo) propose to go with r01 this meeting to make progress and further discuss duration time in May meeting. Fabio (Nokia) is OK with either r01 or r04. ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306068 | CR | Approval | 23.288 CR0737R1 (Rel-18, 'C'): Timestamp of action taken by analytics consumer | Nokia, Nokia Shanghai Bell, Vivo, ETRI, Ericsson, Lenovo | Rel-18 | Revision of S2-2304076r01. Approved | Agreed | |
| 9.23.2 | S2-2304269 | CR | Approval | 23.288 CR0744 (Rel-18, 'B'): Clarification on AnLF registering its capability for monitoring analytics accuracy of an ML model to the MTLF | Lenovo | Rel-18 | Covered by S2-2304031 | Zhang (Ericsson) provides comments and suggest to use S2-2304031 as baseline Dimitris (Lenovo) responds Zhang (Ericsson) response to Dimitris (Lenovo) Xiaobo (vivo) share view Dimitris (Lenovo) ok to go with 4031 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.23.2 | S2-2304439 | CR | Approval | 23.288 CR0598R4 (Rel-18, 'B'): Rating untrusted AF data sources | Lenovo Future Communications | Rel-18 | Revision of S2-2303520 from S2#155. r03 agreed. Revised to S2-2306069. | Soohwan (ETRI) provides comments and questions. Zhang (Ericsson) provides comments Costas (Lenovo) replies to Zhang (Ericsson) and Soohwan (ETRI) and uploads r01 Soohwan (ETRI) provides further comments on r01. Xiaoyan (CATT) provides comments. Zhang (Ericsson) provides comments on r01 Costas (Lenovo) accepts r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306069 | CR | Approval | 23.288 CR0598R5 (Rel-18, 'B'): Rating untrusted AF data sources | Lenovo Future Communications | Rel-18 | Revision of S2-2304439r03. Approved | Agreed | |
| 9.23.2 | S2-2304535 | CR | Approval | 23.288 CR0761 (Rel-18, 'B'): Extending Analytics Transfer to support also accuracy checking transfer to target NWDAF. | Huawei, HiSilicon | Rel-18 | Postponed | Xiaoyan (CATT) provides comments. Haiyang (Huawei) provides r01. Zhang (Ericsson) provide r02 Haiyang (Huawei) provides r03. Zhang (Ericsson) response to Hiayang Haiyang (Huawei) provides further clarifications to Zhang (Ericsson) and r04. ==== Revisions Deadline ==== Zhang (Ericsson) suggest to postpone the paper ==== Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2304539 | CR | Approval | 23.288 CR0763 (Rel-18, 'B'): Removing Ens from AnLF Analytics Accuracy Monitoring | Huawei, HiSilicon | Rel-18 | r06 agreed. Revised to S2-2306070, merging S2-2304918, S2-2304916 and S2-2304459 | Jiahui (China Telecom) provides comment. Zhang (Ericsson) provides comments Haiyang (Huawei) provides r01 Aihua(CMCC) provides r02 and co-signs the paper Jiahui (China Telecom) provides comment and r03. Aihua(CMCC) provides r04 and co-signs the paper Dimitris (Lenovo) comments on r04 Aihua(CMCC) provides r05 Aihua(CMCC) provides r06 ==== Revisions Deadline ==== Jiahui (China Telecom) is ok with r06 and co-signs. Dimitris (Lenovo) is OK with r06 and co-signs Zhang (Ericsson) is OK with r06 and co-sign ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306070 | CR | Approval | 23.288 CR0763R1 (Rel-18, 'B'): Removing Ens from AnLF Analytics Accuracy Monitoring | Huawei, HiSilicon, China Mobile, China Telecom, Lenovo, Ericsson | Rel-18 | Revision of S2-2304539r06, merging S2-2304918, S2-2304916 and S2-2304459. Approved | Agreed | |
| 9.23.2 | S2-2304553 | CR | Approval | 23.288 CR0767 (Rel-18, 'C'): New parameter introduced in Contents of ML Model Provisioning | Intel | Rel-18 | r02 agreed. Revised to S2-2306071. | Megha (Intel) provides r01 and comments. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306071 | CR | Approval | 23.288 CR0767R1 (Rel-18, 'C'): New parameter introduced in Contents of ML Model Provisioning | Intel, Vivo | Rel-18 | Revision of S2-2304553r02. Approved | Agreed | |
| 9.23.2 | S2-2304554 | CR | Approval | 23.288 CR0768 (Rel-18, 'C'): Update to MTLF-based ML Model Accuracy Monitoring Procedure | Intel | Rel-18 | Check Affected Clauses! r03 agreed. Revised to S2-2306072. | Zhang (Ericsson) provides comments Megha(Intel) provides comments. I think the comments provided by Zhang(Ericsson) on S2-2304554 are applicable to TDoc S2-2304553. Costas (Lenovo) provides a suggestion to change the NOTE Megha (Intel) provides r01 and comments Costas (Lenovo) is fine with the update r01 provided Fabio (Nokia) provides r02. Antoine (Orange) provides r03. Costas (Lenovo) provides comments on r03 and provide r04. Fabio (Nokia) prefers r03 over r04 as the latter unnecessarily restricts the behavior of an NF. ==== Revisions Deadline ==== Megha(Intel) is ok with r03. Zhang (Ericsson) is OK with r03 and object all other revisions ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306072 | CR | Approval | 23.288 CR0768R1 (Rel-18, 'C'): Update to MTLF-based ML Model Accuracy Monitoring Procedure | Intel | Rel-18 | Revision of S2-2304554r03. Approved | Agreed | |
| 9.23.2 | S2-2304459 | CR | Approval | 23.288 CR0756 (Rel-18, 'B'): Resolve EN about AnLF can provide only the accuracy information to a consumer | China Mobile | Rel-18 | Merged into S2-2306070 | Soohwan (ETRI) asks a question. Aihua(CMCC) replies to Soohwan (ETRI) Dimitris (Lenovo) has concerns with the proposal Aihua(CMCC) replies to Dimitris (Lenovo) Dimitris (Lenovo) responds Zhang (Ericsson) have concerns for the proposal Haiyang (Huawei) also prefers to keep using the analytic subscription service and propose to use S2-2304539 for discussions on removal of ENs from Clause 6.2D. Aihua(CMCC) replies to Dimitris (Lenovo) , Zhang (Ericsson) and Haiyang (Huawei) ==== Revisions Deadline ==== Haiyang (Huawei) suggests to merge this paper into S2-2304539. Zhang (Ericsson) suggests to merge the paper into S2-2304539 Aihua(CMCC) agrees to merge into 4539. ==== Comments Deadline ==== | Merged |
| 9.23.2 | S2-2304755 | CR | Approval | 23.288 CR0782 (Rel-18, 'B'): KI#1 Clarification on the accuracy information | vivo | Rel-18 | r06 agreed. Revised to S2-2306073. | Soohwan (ETRI) ask a question for clarification. Jiahui (China Telecom) provides comment and r01. Xiaobo (vivo) provides clarification and r02 by merging S2-2304917/S2-2304534 <file:///D:/Users/11131741/Downloads/Docs/S2-2304534.zip> /S2-2304538 <file:///D:/Users/11131741/Downloads/Docs/S2-2304538.zip> Costas (Lenovo) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306073 | CR | Approval | 23.288 CR0782R1 (Rel-18, 'B'): KI#1 Clarification on the accuracy information | Vivo, China Telecom, Huawei | Rel-18 | Revision of S2-2304755r06. Approved | Agreed | |
| 9.23.2 | S2-2304756 | CR | Approval | 23.288 CR0783 (Rel-18, 'B'): KI#1 Adding the number of inferences for calculating global accuracy | vivo | Rel-18 | r06 agreed. Revised to S2-2306074. | Soohwan (ETRI) provides comments. Xiaobo (vivo) provides r01 to address the comment from Soohwan (ETRI). Fabio (Nokia) provides comments to r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306074 | CR | Approval | 23.288 CR0783R1 (Rel-18, 'B'): KI#1 Adding the number of inferences for calculating global accuracy | Vivo | Rel-18 | Revision of S2-2304756r06. Approved | Agreed | |
| 9.23.2 | S2-2304757 | CR | Approval | 23.502 CR3743R2 (Rel-18, 'B'): NRF service enhancements for Analytics Accuracy Monitoring | Vivo, Huawei | Rel-18 | Revision of S2-2302539 from S2#155. Approved | Agreed | |
| 9.23.2 | S2-2304788 | CR | Approval | 23.288 CR0787 (Rel-18, 'B'): KI#1: Update of MLModelMonitor service to deliver Analytics feedback information | ETRI | Rel-18 | r05 agreed. Revised to S2-2306075. | Zhang (Ericsson) provides r01 Soohwan (ETRI) provides r02. Haiyang (Huawei) comments. Jiahui (China Telecom) provides comment. Soohwan (ETRI) provides r03 and replies to Haiyang (Huawei). Soohwan (ETRI) responds to Jiahui (China Telecom). Soohwan (ETRI) provides r04. Yannick (Convenor): To record that r03 was provided by Soohwan (ETRI). Fabio (Nokia) provides comments and r05 ==== Revisions Deadline ==== Soohwan (ETRI) okay with r05. Xiaobo (vivo) is ok with r05 and would like to co-sign it. Jiahui (China Telecom) is ok with r05 and requests to co-sign. Zhang (Ericsson) is OK with r05 and co-sign ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306075 | CR | Approval | 23.288 CR0787R1 (Rel-18, 'B'): KI#1: Update of MLModelMonitor service to deliver Analytics feedback information | ETRI, vivo, China Telecom, Ericsson | Rel-18 | Revision of S2-2304788r05. Approved | Agreed | |
| 9.23.2 | S2-2304791 | CR | Approval | 23.502 CR3903R1 (Rel-18, 'B'): KI#1: Update of Nnef_AnalyticsExposure service | ETRI, [vivo] | Rel-18 | Revision of S2-2302593 from S2#155. r01 agreed. Revised to S2-2306076. | Zhang (Ericsson) ask for a clean version of the CR Haiyang(Huawei) agrees with Zhang (Ericsson) Soohwan (ETRI) provides r01 and add vivo a co-source company ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306076 | CR | Approval | 23.502 CR3903R2 (Rel-18, 'B'): KI#1: Update of Nnef_AnalyticsExposure service | ETRI, vivo | Rel-18 | Revision of S2-2304791r01. Approved | Agreed | |
| 9.23.2 | S2-2304899 | CR | Approval | 23.288 CR0796 (Rel-18, 'C'): Update information used for ML Model Accuracy Monitoring | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2304916 | CR | Approval | 23.288 CR0804 (Rel-18, 'B'): Enhancement on Nwdaf_AnalyticsSubscription service to support accuracy information exposure | China Telecom | Rel-18 | Merged into S2-2306070 | Zhang (Ericsson) suggest to merge this CR into S2-2304539 Jiahui (China Telecom) agrees to merge. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.23.2 | S2-2304918 | CR | Approval | 23.288 CR0806 (Rel-18, 'B'): Remove EN on data collection for accuracy information subscription | China Telecom | Rel-18 | Merged into S2-2306070 | Zhang (Ericsson) suggest to merge the CR into S2-2304539 Jiahui (China Telecom) agrees to merge. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.23.2 | S2-2304926 | CR | Approval | 23.288 CR0807 (Rel-18, 'B'): Enhancement of DN Performance Analytics | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2306077. | Zhang (Ericsson) provides comments Zhang (Ericsson) ask another question for clarification Susan (Huawei) provides r01. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r01 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306077 | CR | Approval | 23.288 CR0807R1 (Rel-18, 'B'): Enhancement of DN Performance Analytics | Huawei, HiSilicon | Rel-18 | Revision of S2-2304926r01. Approved | Agreed | |
| 9.23.2 | S2-2305171 | CR | Approval | 23.501 CR3764R4 (Rel-18, 'B'): Extension of NWDAF registration information to reflect new accuracy checking capability | Huawei, HiSilicon, vivo | Rel-18 | Revision of S2-2302412 from S2#155. Approved | Zhang (Ericsson) provides comments Haiyang (Huawei) responds to Zhang (Ericsson) Zhang (Ericsson) agree with Haiyang ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.23.2 | S2-2305222 | CR | Approval | 23.288 CR0817 (Rel-18, 'C'): Subsets and order of results for newly defined analytics output | Orange | Rel-18 | r01 agreed. Revised to S2-2306078. | Kenichi (KDDI) co-signs the paper Antoine (Orange) provides r01 to add KDDI as co-signer. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306078 | CR | Approval | 23.288 CR0817R1 (Rel-18, 'C'): Subsets and order of results for newly defined analytics output | Orange, KDDI | Rel-18 | Revision of S2-2305222r01. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #2: NWDAF-assisted application detection | - | - | Docs:=2 | - | |
| 9.23.2 | S2-2305234 | CR | Approval | 23.503 CR1028 (Rel-18, 'C'): Clarification on NWDAF-assisted PFD management in TS23.503 | CMCC, KDDI | Rel-18 | r02 agreed. Revised to S2-2306079. | Belen (Ericsson) provides comments. Aihua(CMCC) replies to Belen (Ericsson) and provides r02, please ignore r01. ==== Revisions Deadline ==== Belen (Ericsson) is okay with r02 Thomas(Nokia) comments that r02 still has problems. Suggest agreeing r02 + Remove 'provided by the NWDAF' Aiua(CMCC) is okay with r02 + Remove 'provided by the NWDAF' ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306079 | CR | Approval | 23.503 CR1028R1 (Rel-18, 'C'): Clarification on NWDAF-asssisted PFD management in TS23.503 | CMCC, KDDI | Rel-18 | Revision of S2-2305234r02. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #3: Data and analytics exchange in roaming case | - | - | Docs:=16 | - | |
| 9.23.2 | S2-2305154 | DISCUSSION | Discussion | Proposals for open issues for key issue 3 (roaming). | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2303140 from S2#155. Noted | Noted | |
| 9.23.2 | S2-2304584 | CR | Approval | 23.288 CR0770 (Rel-18, 'B'): Resolving editor's notes in procedures for analytics exposure in roaming case | CATT, Qualcomm, Nokia, Nokia-Shanghai-Bell, vivo, NTT DOCOMO, Ericsson | Rel-18 | r09 agreed. Revised to S2-2306080. | Antoine (Orange) provides r01 with some rewording to the new clause. Thomas(Nokia) provides some comments. Suggest an offline Telco to discuss open points for KI#3 Zhang (Ericsson) provides comments Xiaoyan (CATT) replies to Zhang (Ericsson). Xiaoyan (CATT) provides r02. Xiaoyan (CATT) provides r03. Antoine (Orange) comments. Thomas (Nokia) provides r04 to merge overlapping parts of S2-2305156 Antoine (Orange) provides r05. Vivian (vivo) provides r06. Zhang (Ericsson) provide r07 Thomas (Nokia) provide r08 Xiaoyan (CATT) provide r09 Xiaoyan (CATT) provide r10 ==== Revisions Deadline ==== Xiaoyan (CATT) provides comments to the late r10 Thomas (Nokia) replies to Xiaoyan, prefers r08, can live with r09 Thomas (Nokia) corrects himself, still prefers r08, objects r09 as is, (for the sake of completeness) also objects to r00, r01, r02, r03, and r07 can live with r09 + Reinstating the following ENs: Editor's note: Whether and how the H-NWDAF aggregates the analytics from VPLMN and the analytics derived in HPLMN is FFS. Editor's note: Whether and how the V-NWDAF aggregates the analytics from HPLMN and the analytics derived in VPLMN is FFS. Zhang (Ericsson) is OK with r07, 08, 09, 10 object all other versions Thomas(Nokia) comments that r10 was provide by him earlier. Perhaps Xiaoyan can provide a r11? Xiaoyan (CATT) objects to r07, r08, accept r09, can live with r09+ENs reinstated as requested by Thomas (Nokia). ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306080 | CR | Approval | 23.288 CR0770R1 (Rel-18, 'B'): Resolving editor's notes in procedures for analytics exposure in roaming case | CATT, Qualcomm, Nokia, Nokia-Shanghai-Bell, vivo, NTT DOCOMO, Ericsson | Rel-18 | Revision of S2-2304584r09. Approved | Agreed | |
| 9.23.2 | S2-2304585 | CR | Approval | 23.288 CR0713R1 (Rel-18, 'B'): Enhancements to analytics specific procedures for analytics exchange in roaming case | CATT | Rel-18 | Revision of S2-2302793 from S2#155. r04 agreed. revised to S2-2306081. | Bahador (NTT DOCOMO) provides a comment. Antoine (Orange) asks what are the roaming cases involved for these analytics. Xiaoyan (CATT) replies to Bahador (NTT DOCOMO). Xiaoyan (CATT) replies to Antoine (Orange). Xiaoyan (CATT) replies to Costas (Lenovo). Thomas(Nokia) provides more comments. Suggest an offline Telco to discuss open points for KI#3 Xiaoyan (CATT) further clarifies to Antoine (Orange). Xiaoyan (CATT) replies to Thomas(Nokia). Zhang (Ericsson) response comments Bahador (NTT DOCOMO) replies to Xiaoyan (CATT) Xiaoyan (CATT) provides r01. Antoine (Orange) thanks Xiaoyan for the clarifications and provides r02. Thomas(Nokia) provides r03. Antoine (Orange) provides r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306081 | CR | Approval | 23.288 CR0713R2 (Rel-18, 'B'): Enhancements to analytics specific procedures for analytics exchange in roaming case | CATT | Rel-18 | Revision of S2-2304585r04. Approved | Agreed | |
| 9.23.2 | S2-2304586 | CR | Approval | 23.503 CR0926R1 (Rel-18, 'B'): Using network analytics for roaming scenarios | CATT | Rel-18 | Revision of S2-2302796 from S2#155. r02 agreed. Revised to S2-2306082. | Antoine (Orange) provides r01. Zhang (Ericsson) provides comments and ask clarification Bahador (NTT DOCOMO) provides a comment. Xiaoyan (CATT) provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306082 | CR | Approval | 23.503 CR0926R2 (Rel-18, 'B'): Using network analytics for roaming scenarios | CATT | Rel-18 | Revision of S2-2304586r02. Approved | Agreed | |
| 9.23.2 | S2-2304612 | CR | Approval | 23.288 CR0775 (Rel-18, 'C'): Roaming architecture for data or analytics exchange | Vivo, Ericsson | Rel-18 | r01 agreed. Revised to S2-2306083. | Thomas (Nokia) raises concerns against r00 and provides r01 Vivian (vivo) replies to Thomas (Nokia)'s comments Vivian (vivo) provides r02. ==== Revisions Deadline ==== Zhang (Ericsson) prefers r02 Thomas(Nokia) objects against r00 and r02 Vivian(vivo) is OK with r01 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306083 | CR | Approval | 23.288 CR0775R1 (Rel-18, 'C'): Roaming architecture for data or analytics exchange | Vivo, Ericsson | Rel-18 | Revision of S2-2304612r01. Approved | Agreed | |
| 9.23.2 | S2-2304894 | CR | Approval | 23.501 CR4428 (Rel-18, 'B'): Add NWDAF services and Reference point between two NWDAFs for roaming case | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306084. | Antoine (Orange) asks why we need to define a Reference point between two NWDAFs in different PLMNs. Wang Yuan (Huawei) replies to Antoine (Orange). Zhang (Ericsson) provide comments Thomas (Nokia) questions need for the CR Wang Yuan (Huawei) replies to Zhang (Ericsson) and Thomas (Nokia), and provides r01 and r02 with different NWDAF name. Thomas(Nokia) replies to Wang Yuan and provides r03. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 Thomas(Nokia) objects to r00, r01 and r02 (for the record) ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306084 | CR | Approval | 23.501 CR4428R1 (Rel-18, 'B'): Add NWDAF services and Reference point between two NWDAFs for roaming case | Huawei, HiSilicon, Nokoia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304894r03. Approved | Agreed | |
| 9.23.2 | S2-2304895 | CR | Approval | 23.288 CR0794 (Rel-18, 'B'): Update the procedures for data exchange in roaming case | Huawei, HiSilicon | Rel-18 | Postponed | Bahador (NTT DOCOMO) proposes to postpone this CR. Wang Yuan (Huawei) replies to Bahador (NTT DOCOMO) and provides r01. Thomas(Nokia) raises concerns against the principles of the CR.. Bahador (NTT DOCOMO) replies to Yuan (Huawei). Antoine (Orange) comments (r00 and r01 not agreeable). Wang Yuan (Huawei) replies to Thomas (Nokia), Bahador (NTT DOCOMO) and Antoine (Orange) and clarify that it is SA3 conclusion that either the V-NWDAF or H-NWDAF could be the user consent enforcement point. Wang Yuan (Huawei) replies to Bahador (NTT DOCOMO) and provides r02 that aligns the changes in S2-2304898r01, and also provides r03 that removes all the descriptions about V-NWDAF checking user consent as the candidate for approval. Vivian (vivo) provides comments. Antoine (Orange) provides r04, based on r03 with changes under cyan highlight. Wang Yuan (Huawei) can live with r04, and provides r05 that removes all the user consent related changes considering that we may be unable to reach a consensus on it. Bahador (NTT DOCOMO) requests for clarification. ==== Revisions Deadline ==== Wang Yuan (Huawei) replies to Bahador (NTT DOCOMO). Zhang (Ericsson) is OK with r05 and object all other versions Thomas(Nokia) request postponing this CR ==== Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2304898 | CR | Approval | 23.502 CR4085 (Rel-18, 'B'): Update the user consent for UDM and UDR services | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306085. | Zhang (Ericsson) provides comments Thomas(Nokia) raises additional concerns Antoine (Orange) agrees with Thomas. Bahador (NTT DOCOMO) proposes to postpone this CR. Wang Yuan (Huawei) replies to Zhang (Ericsson), Thomas (Nokia), Antoine (Orange) and Bahador (NTT DOCOMO), and provides r01. Zhang (Ericsson) response to Yuan Wang Yuan (Huawei) provides r02 that only keeps the first change. ==== Revisions Deadline ==== Zhang (Ericsson) is ok with r02 and object all other versions ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306085 | CR | Approval | 23.502 CR4085R1 (Rel-18, 'B'): Update the user consent for UDM and UDR services | Huawei, HiSilicon | Rel-18 | Revision of S2-2304898r02. Approved | Agreed | |
| 9.23.2 | S2-2305156 | CR | Approval | 23.288 CR0816 (Rel-18, 'B'): Resolving Open issues for key issue 3 | Nokia, Nokia Shanghai-Bell | Rel-18 | r03 agreed. Revised to S2-2306086. | Zhang (Ericsson) suggest to merge the paper into S2-2304584 Juan Zhang (Qualcomm) provides comments. Xiaoyan (CATT) provides comments. Thomas(Nokia) agrees to merge changes affecting clauses also covered in 4584 into that spec but prefers to keep remaining changes in this CR. Replies to Zhang Vivian (vivo) provides comments Thomas(Nokia) replies to Vivian Bahador (NTT DOCOMO) provides comments. Thomas (Nokia) provides r01 Thomas (Nokia) provides r02 Zhang (Ericsson) provides r03 with editorial updates ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306086 | CR | Approval | 23.288 CR0816R1 (Rel-18, 'B'): Resolving Open issues for key issue 3 | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2305156r03. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #4: How to Enhance Data collection and Storage | - | - | Docs:=19 | - | |
| 9.23.2 | S2-2304041 | CR | Approval | 23.502 CR3661R2 (Rel-18, 'B'): Updates on pending notifications handling | Ericsson | Rel-18 | Revision of S2-2302468 from S2#155. Postponed | Fabio (Nokia) has strong concerns for this contribution. Zhang (Ericsson) response to Fabio (Nokia) Fabio (Nokia) replies to comments from Zhang (Ericsson) ==== Revisions Deadline ==== Fabio (Nokia) provides further replies to comments Zhang (Ericsson) provides comments to Fabio Fabio (Nokia) cannot accept this CR as the problem it addresses deserves further clarification. ==== Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2304074 | CR | Approval | 23.288 CR0726R1 (Rel-18, 'C'): Data Storage Management | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2303078 from S2#155. CR Cover sheet error! Check clauses affected! r02 agreed. Revised to S2-2306087. | Zhang (Ericsson) ask questions Wang Yuan (Huawei) asks questions. Fabio (Nokia) replies to comments and provides r01 Wang Yuan (Huawei) is OK with r01, but finds there are some editorial typos in r01, maybe this can be simply fixed in next revision. Fabio (Nokia) provides r02 to fix editorial typos. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306087 | CR | Approval | 23.288 CR0726R2 (Rel-18, 'C'): Data Storage Management | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304074r02. Approved | Agreed | |
| 9.23.2 | S2-2304075 | CR | Approval | 23.288 CR0727R1 (Rel-18, 'C'): Data storage in ADRF using DSC indicator | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2303080 from S2#155. Confirm CR Revision - CR states 0! r01 agreed. Revised to S2-2306088. | Zhang (Ericsson) provides r01 Fabio (Nokia) provides to comments on r01. Zhang (Ericsson) response to Fabio (Nokia) ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r01 and object all other versions Fabio (Nokia) is OK with r01 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306088 | CR | Approval | 23.288 CR0727R2 (Rel-18, 'C'): Data storage in ADRF using DSC indicator | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304075r01. Approved | Agreed | |
| 9.23.2 | S2-2304408 | CR | Approval | 23.502 CR4003 (Rel-18, 'B'): Clarification on data collection frequency mode in TS 23.502 | China Mobile | Rel-18 | r07 agreed. Revised to S2-2306089. | Aihua(CMCC) provides r01 to replace 'data collection frequency' with 'measurement frequency' to avoid confusion with the remaining parameters. Fabio (Nokia) provides comments about r01 and provides r02. Costas (Lenovo) ask for clarification and proposes alternative solution Antoine (Orange) agrees with Costas's comment, cannot agree to r04 because there is no collection functionality speficied for 5GC NF (except for NWDAF in TS 23.288). Also asks what are the 'corresponding conditions' and which parameter conveys them. Aihua(CMCC) replies to Antoine (Orange) and Costas (Lenovo), provides r06, please ignore r05. Antoine (Orange) replies to Aihua; still cannot accept r06. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306089 | CR | Approval | 23.502 CR4003R1 (Rel-18, 'B'): Variable periodicity in event reporting | China Mobile | Rel-18 | Revision of S2-2304408r07. Approved | Agreed | |
| 9.23.2 | S2-2304410 | CR | Approval | 23.288 CR0754 (Rel-18, 'B'): Clarification on data collection frequency mode in TS 23.288 | China Mobile | Rel-18 | Noted | Antoine (Orange) comments that this CR and S2-2304408 need to be aligned with each other. Aihua(CMCC) replies to Antoine (Orange) that S2-2304408r04 contains the description related to their corresponding conditions. ==== Revisions Deadline ==== Antoine (Orange) objects to r00. ==== Comments Deadline ==== | Noted |
| 9.23.2 | S2-2304461 | CR | Approval | 23.501 CR4318 (Rel-18, 'B'): DCCF Discovery principle enhancements for DCCF relocation in TS 23.501 | China Mobile | Rel-18 | r04 agreed. Revised to S2-2306090. | Zhang (Ericsson) provides comments Fabio (Nokia) provides r01 Aihua(CMCC) provides r02 Fabio (Nokia) replies to comments and provides r03. Zhang (Ericsson) provides r04 ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r04 and object all other versions ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306090 | CR | Approval | 23.501 CR4318R1 (Rel-18, 'B'): DCCF Discovery principle enhancements for DCCF relocation in TS 23.501 | China Mobile | Rel-18 | Revision of S2-2304461r04. Approved | Agreed | |
| 9.23.2 | S2-2304463 | CR | Approval | 23.502 CR4013 (Rel-18, 'B'): Enhance NRF services for DCCF relocation in TS 23.502 | China Mobile | Rel-18 | r03 agreed. Revised to S2-2306091. | Zhang (Ericsson) provides comments Aihua(CMCC) provides r01 Fabio (Nokia) replies to comments and provides r02 Zhang (Ericsson) provide r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306091 | CR | Approval | 23.502 CR4013R1 (Rel-18, 'B'): Enhance NRF services for DCCF relocation in TS 23.502 | China Mobile | Rel-18 | Revision of S2-2304463r03. Approved | Agreed | |
| 9.23.2 | S2-2304608 | CR | Approval | 23.288 CR0771 (Rel-18, 'C'): Clarifications to Model storage and retrieval from ADRF | Vivo | Rel-18 | r02 agreed. Revised to S2-2306092. | Jaewoo (LGE) provides comments. Vivian (vivo) replies to Jaewoo (LGE)'s comments and provides r01. Jaewoo (LGE) replies to Vivian (vivo). Zhang (Ericsson) provides comments Bahador (NTT DOCOMO) provides a comment. Vivian (vivo) replies to Zhang(Ericsson) and Bahador (NTT DOCOMO)'s comment. Bahador (NTT DOCOMO) replies to Vivian (vivo). Vivian (vivo) replies to Bahador's (NTT DOCOMO) comment. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306092 | CR | Approval | 23.288 CR0771R1 (Rel-18, 'C'): Clarifications to Model storage and retrieval from ADRF | Vivo | Rel-18 | Revision of S2-2304608r02. Approved | Agreed | |
| 9.23.2 | S2-2304030 | CR | Approval | 23.288 CR0729 (Rel-18, 'C'): Update to ML model storage and retrieval via ADRF | Ericsson | Rel-18 | r03 agreed. Revised to S2-2306093. | Bahador (NTT DOCOMO) requests for clarification. Vivian (vivo) provides comments and r01. Zhang (Ericsson) provides r02 with some editorial changes Fabio (Nokia) provides comments to r02. Wang Yuan (Huawei) provides comments on r02. Zhang (Ericsson) provides r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306093 | CR | Approval | 23.288 CR0729R1 (Rel-18, 'C'): Update to ML model storage and retrieval via ADRF | Ericsson | Rel-18 | Revision of S2-2304030r03. Approved | Agreed | |
| 9.23.2 | S2-2304901 | CR | Approval | 23.501 CR4430 (Rel-18, 'B'): Update of ADRF services | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2304906 | CR | Approval | 23.288 CR0802 (Rel-18, 'B'): Update the contents of ML model provisioning | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306094. | Zhang (Ericsson) provides r01 Fabio (Nokia) provides comments to r01. Wang Yuan (Huawei) provides r02. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r02 and co-sign Fabio (Nokia) is OK with r02 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306094 | CR | Approval | 23.288 CR0802R1 (Rel-18, 'B'): Update the contents of ML model provisioning | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304906r02. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #5: Enhance trained ML Model sharing | - | - | Docs:=40 | - | |
| 9.23.2 | - | - | - | Key issue #6: NWDAF-assisted URSP | - | - | Docs:=1 | - | |
| 9.23.2 | S2-2304925 | CR | Approval | 23.501 CR4437 (Rel-18, 'B'): Update on NWDAF-assisted URSP | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! Postponed | Jihoon (ETRI) provides comments. Susan (Huawei) provides r01. Jihoon (ETRI) provides r02. LaeYoung (LGE) cannot accept r01 and r02 because the Redundant Transmission Experience analytics is not about DC but about redundant transmission on N3/N9. Jihoon (ETRI) replies to LaeYoung (LGE). LaeYoung (LGE) replies to Jihoon (ETRI). Jihoon (ETRI) provides r03. LaeYoung (LGE) is fine with r03. Susan (Huawei) replies to LaeYoung (LGE) and Jihoon (ETRI) and clarify that reference to 5.33.2.2 of 23.501 as proposed in r03 is not correct. Belen (Ericsson) cannot accept r03 or previous revisions, proposed some changes LaeYoung (LGE) asks a Q. Juan Zhang (Qualcomm) provides comments Susan (Huawei) replies to LaeYoung (LGE). LaeYoung (LGE) responds to Susan (Huawei). LaeYoung (LGE) comments. Susan (Huawei) replies to Jihoon (ETRI). ==== Revisions Deadline ==== LaeYoung (LGE) prefers to POSTPONE this CR. Belen (Ericsson) asks to postpone Susan (Huawei) is ok to postpone ==== Comments Deadline ==== | Postponed |
| 9.23.2 | - | - | - | Key issue #7: Enhancements on QoS Sustainability analytics | - | - | Docs:=2 | - | |
| 9.23.2 | S2-2305385 | LS OUT | Approval | [DRAFT] LS on OAM input data for QoS Sustainability Analytics | Orange | Rel-18 | r00 agreed. Revised to S2-2306095. | Revised | |
| 9.23.2 | S2-2306095 | LS OUT | Approval | LS on OAM input data for QoS Sustainability Analytics | SA WG2 | Rel-18 | Revision of S2-2305385r00. Approved | Approved | |
| 9.23.2 | - | - | - | Key Issue #8: Supporting Federated Learning in 5GC | - | - | Docs:=13 | - | |
| 9.23.2 | S2-2304033 | CR | Approval | 23.288 CR0732 (Rel-18, 'F'): Solving EN in the Procedure for Maintaining Federated Learning | Ericsson | Rel-18 | r08 agreed. Revised to S2-2306096. | Zhang (Ericsson) provides r01 Vivian(vivo) provides r03 on top of r01, please ignore the r02 (sorry for the mis-uploading). Costas (Lenovo) comments on r01 Bahador (NTT DOCOMO) replies to Costas (Lenovo). Susan (Huawei) provides r04. Vivian (vivo) provides r05. Zhang (Ericsson) provides r06 and thanks everyone for the help Costas (Lenovo) further comments Susan (Huawei) provides r07. Zhang (Ericsson) provides r08 ==== Revisions Deadline ==== Susan (Huawei) is ok with r08. Bahador (NTT DOCOMO) supports r08 and wants to co-sign. ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306096 | CR | Approval | 23.288 CR0732R1 (Rel-18, 'F'): Solving EN in the Procedure for Maintaining Federated Learning | Ericsson, Huawei, HiSilicon, NTT DOCOMO | Rel-18 | Revision of S2-2304033r08. Approved | Agreed | |
| 9.23.2 | S2-2304427 | CR | Approval | 23.288 CR0755 (Rel-18, 'C'): Clarification on Federated Learning among Multiple NWDAFs in TS 23.288 | China Mobile | Rel-18 | r05 agreed. Revised to S2-2306097. | Dimitris (Lenovo) provides r01 including aspects from 4264 Zhang (Ericsson) provides r02 and co-sign the paper Vivian (vivo) provides r03 and co-signs the paper Susan (Huawei) provides r04. Zhang (Ericsson) provides r05 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306097 | CR | Approval | 23.288 CR0755R1 (Rel-18, 'C'): Clarification on Federated Learning among Multiple NWDAFs in TS 23.288 | China Mobile, Lenovo, Ericsson, vivo, Huawei, HiSilicon | Rel-18 | Revision of S2-2304427r05. Approved | Agreed | |
| 9.23.2 | S2-2304551 | CR | Approval | 23.288 CR0765 (Rel-18, 'C'): Service operations update to general procedure for Federated Learning between NWDAFs | Intel | Rel-18 | r09 agreed. Revised to S2-2306098. | Vivian(vivo) provides r01 to merge S2-2304609(vivo) and S2-2304611(vivo) into S2-2304551. Fabio (Nokia) provides r02 to merge S2-2304077 into S2-2304551 Megha (Intel) asks question for clarification on merging documents from documents marked as exceeding TU budget Jaewoo (LGE) provides comments on r02. Costas(Lenovo) provides comments on r06. Megha(Intel) provides r09 and comments ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r09, r08 and object all other versions Fabio (Nokia) is OK with r09 and co-signs. Vivian(vivo) is OK with r09 and co-signs. Jaewoo (LGE) is OK with r09 and would like to co-sign. Aihua(CMCC) is fine with r09 and would like to co-sign. ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306098 | CR | Approval | 23.288 CR0765R1 (Rel-18, 'C'): Service operations update to general procedure for Federated Learning between NWDAFs | Intel, ETRI, Ericsson, Nokia, Nokia Shanghai Bell, Vivo, LG Electronics, China Mobile | Rel-18 | Revision of S2-2304551r09. Approved | Agreed | |
| 9.23.2 | S2-2304610 | CR | Approval | 23.288 CR0773 (Rel-18, 'C'): Updates for Nnwdaf_MLModelTraining service | Vivo | Rel-18 | r00 agreed. Revised to S2-2306099. | Zhang (Ericsson) provides r01 Vivian(vivo) replies to Zhang (Ericsson)'s comments and provides r02. Susan (Huawei) provides r03. Costas(Lenovo) comment on r03 Vivian (vivo) replies to Costas(Lenovo) comment Zhang (Ericsson) response to Vivian Costas (Lenovo) replies to Vivian (Vivo) Vivian (vivo) replies to Costas (Lenovo) and provides r04. Bahador (NTT DOCOMO) provides r05. ==== Revisions Deadline ==== Bahador (NTT DOCOMO) supports this CR. Zhang (Ericsson) is OK with r05 and co-sign ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306099 | CR | Approval | 23.288 CR0773R1 (Rel-18, 'C'): Updates for Nnwdaf_MLModelTraining service | Vivo, NTT DOCOMO, Ericsson | Rel-18 | Revision of S2-2304610r00. Approved | Agreed | |
| 9.23.2 | S2-2304662 | CR | Approval | 23.501 CR4372 (Rel-18, 'C'): Updates for registration and discovery for FL entity | Vivo | Rel-18 | Approved | Zhang (Ericsson) provides comments Vivian (vivo) replies to Zhang (Ericsson)'s comments ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r00 ==== Comments Deadline ==== | Agreed |
| 9.23.2 | S2-2304663 | CR | Approval | 23.502 CR3883R1 (Rel-18, 'B'): Enhancement for federated leaning capability. | vivo | Rel-18 | Revision of S2-2302372 from S2#155. CR Cover sheet error! r01 agreed. Revised to S2-2306100. | Zhang (Ericsson) provides comments Vivian(vivo) replies to Zhang (Ericsson)'s comments Zhang (Ericsson) response to Vivian Vivian (vivo) replies to Zhang (Ericsson) and provides r01. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r01 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306100 | CR | Approval | 23.502 CR3883R2 (Rel-18, 'B'): TS 23.502 enhancements for federated learning. | Vivo | Rel-18 | Revision of S2-2304663r01. Approved | Agreed | |
| 9.23.2 | S2-2304927 | CR | Approval | 23.288 CR0808 (Rel-18, 'B'): Update of Procedures for Federated Learning | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2306101. | Zhang (Ericsson) provides r01 and ask for clarification Vivian (vivo) provides comments on r01 and orginal version, and asks to remove changes for clause 6.2C.2.2, 6.2C.2.3, 6.2F.1, 6.2F.2, 7.10.2 and 7.10.4 . Susan (Huawei) provides r02. Zhang (Ericsson) provides comments to r02 Susan (Huawei) provides r03. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 and co-sign ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306101 | CR | Approval | 23.288 CR0808R1 (Rel-18, 'B'): Update of Procedures for Federated Learning | Huawei, HiSilicon | Rel-18 | Revision of S2-2304927r03. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #9: Enhancement of NWDAF with finer granularity of location information | - | - | Docs:=15 | - | |
| 9.23.2 | S2-2304247 | CR | Approval | 23.288 CR0615R3 (Rel-18, 'B'): UE Mobility analytics enhancement for PSAP | Rakuten Mobile | Rel-18 | Revision of S2-2302348 from S2#155. r01 agreed. Revised to S2-2306102. | Amy (vivo) asks for clarification Aoken (Rakuten) replies to Amy(vivo) Aoken (Rakuten) replies to Thomas(Nokia) Costas (Lenovo) comments and request clarification Aoken (Rakuten) replies to Costas(Lenovo) Amy (vivo) supports this CR Thomas(Nokia) raises concerns Aoken (Rakuten) replies to Amy(vivo) and Thomas(Nokia) and provide r01 Thomas(Nokia) replies to Aoken Aoken (Rakuten) replies to Thomas(Nokia) Zhang (Ericsson) provides r02 and point out 23.032 should be referenced not 23.228 Thomas(Nokia) has concerns with r02 referencing TS 23.032 ==== Revisions Deadline ==== Aoken replies to Zhang(Ericsson) and ask OK with r01 Zhang (Ericsson) is OK with r01 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306102 | CR | Approval | 23.288 CR0615R4 (Rel-18, 'B'): UE Mobility analytics enhancement for PSAP | Rakuten Mobile | Rel-18 | Revision of S2-2304247r01. Approved | Agreed | |
| 9.23.2 | S2-2304266 | CR | Approval | 23.288 CR0742 (Rel-18, 'B'): Addressing ENs in location analytics with finer granularity location information | Lenovo, | Rel-18 | r03 agreed. Revised to S2-2306103. | Amy (vivo) asks for clarification Dimitris (Lenovo) responds to Vivo Amy (vivo) asks for revision on description of when 'more values of liner threshold' provides by NWDAF consumer Dimitris (Lenovo) provides r01 Amy (vivo) provides r02 Amy (vivo) provides r03 as r02 is uploaded wrongly. ==== Revisions Deadline ==== Dimitris (Lenovo) is ok with r03 ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306103 | CR | Approval | 23.288 CR0742R1 (Rel-18, 'B'): Addressing ENs in location analytics with finer granularity location information | Lenovo, | Rel-18 | Revision of S2-2304266r03. Approved | Agreed | |
| 9.23.2 | S2-2304268 | CR | Approval | 23.288 CR0743 (Rel-18, 'B'): Addressing ENs on location accuracy analytics | Lenovo | Rel-18 | r05 agreed. Revised to S2-2306104, merging S2-2305388 | Amy (vivo) suggests merging 1st change into 5388 and discuss only 2nd, 3rd and 4th changes here Dimitris (Lenovo) responds to Vivo Amy (vivo) responds to Lenovo Dimitris (Lenovo) comments Thomas (Nokia) provides r01 to merge 5388 Amy (vivo) responds to Lenovo and Nokia Dimitris(Lenovo) comments Thomas(Nokia) replies to Amy (vivo) Amy (vivo) replies to Lenovo and asks clarification from Nokia Amy (vivo) thanks Thomas for the spotted concern on outputting LCS accuracy and positioning method when ML model input is area. Thomas(Nokia) provides r02 to address the comments of Amy. Amy (vivo) objects r01 and provides an acceptable r02 Dimitris (Lenovo) comments that Thomas has already provided an r02 Amy (vivo) provides r03 Dimitris (Lenovo) comments on r03 Amy (vivo) replies to Dimitris (Lenovo) Thomas (Nokia) replies to Amy Dimitris (Lenovo) comments and provides r04 Amy (vivo) replies to Thomas Amy (vivo) objects r04 and asks for clarification from Dimitris (Lenovo) Dimitris (Lenovo) comments and provides r05 ==== Revisions Deadline ==== Amy (vivo) is ok with r05 and cosigning this paper. Thomas(Nokia) is fine with r05. ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306104 | CR | Approval | 23.288 CR0743R1 (Rel-18, 'B'): Addressing ENs on location accuracy analytics | Lenovo, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2304268r05, merging S2-2305388. Approved | Agreed | |
| 9.23.2 | S2-2304385 | CR | Approval | 23.288 CR0753 (Rel-18, 'B'): Update NWDAF Services and analytics information tables for KI#9 | KDDI, Samsung | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2304429 | CR | Approval | 23.288 CR0703R1 (Rel-18, 'C'): Update for UE mobility analytics using fine granularity in TS 23.288 | China Mobile. Ericsson | Rel-18 | Revision of S2-2302432 from S2#155. r04 agreed. Revised to S2-2306105. | Aihua(CMCC) provides r01 for S2-2304429 as per the offline discussion. Kenichi (KDDI) provides comment. Amy (vivo) provides comments on utilizing 'Spatial granularity size' to describe 'below cell level'. Wang Yuan (Huawei) replies to Amy(vivo) Amy (vivo) replies to Yuan (Huawei) Yannick (Convenor): To record that r02 was provided by Amy (vivo). Thomas (Nokia) comments that more changes might be required at next meeting due to renaming of 'below cell level' Amy (vivo) agrees with Thomas (Nokia) and suggests having agreement on the terminology 'longitude and latitude level' instead of 'below cell level' in this meeting Aihua(CMCC) agrees with Amy that we can use the terminology 'longitude and latitude level' instead of 'below cell level'. Aihua(CMCC) provides r04 to use the terminology 'longitude and latitude level' in clause 6.7.2. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306105 | CR | Approval | 23.288 CR0703R2 (Rel-18, 'C'): Update for UE mobility analytics using fine granularity in TS 23.288 | China Mobile. Ericsson, vivo, Huawei, HiSilicon | Rel-18 | Revision of S2-2304429r04. Approved | Agreed | |
| 9.23.2 | S2-2304665 | CR | Approval | 23.288 CR0662R2 (Rel-18, 'B'): New analytics ID for traffic flow use case | vivo | Rel-18 | Revision of S2-2302759 from S2#155. r06 agreed. Revised to S2-2306106. | Kenichi (KDDI) requires revision. Amy (vivo) provides r02 as KDDI requests Kenichi (KDDI) fine with r1. Thomas(Nokia) provides r03 Kenichi (KDDI) provides r04 and additional comment. Amy (vivo) provides r05 and replies to Kenichi, Thomas and Costas. Costas (Lenovo) further comments to Amy (vivo) Amy (vivo) replies to Costas (Lenovo), emphasizes r05 and copy paste branched discussion with Thomas and Kenichi Costas (Lenovo), replies to Amy (vivo) Amy (vivo) provides r06, and replies to Costas (Lenovo) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306106 | CR | Approval | 23.288 CR0662R3 (Rel-18, 'B'): New analytics ID for traffic flow use case | Vivo | Rel-18 | Revision of S2-2304665r06. Approved | Agreed | |
| 9.23.2 | S2-2304904 | CR | Approval | 23.288 CR0800 (Rel-18, 'C'): UE Mobility analytics enhancement | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306107. | Amy (vivo) suggests utilizing version TS23.288 i10 as baseline for the 3rd change Yuan (Huawei) provides r01. Zhang (Ericsson) provides r02 and co-sign the paper Wang Yuan (Huawei) thanks for the co-sign but asks for clarification ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.23.2 | S2-2306107 | CR | Approval | 23.288 CR0800R1 (Rel-18, 'C'): UE Mobility analytics enhancement | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2304904r02. Approved | Agreed | |
| 9.23.2 | S2-2305016 | CR | Approval | 23.288 CR0725R1 (Rel-18, 'B'): Enhancement of NWDAF with finer granularity of location information in Observed Service Experience Analytic ID | Rakuten Mobile | Rel-18 | Revision of S2-2303031 from S2#155. Approved | Agreed | |
| 9.23.2 | S2-2305388 | CR | Approval | 23.288 CR0818 (Rel-18, 'B'): Resolving Open issues for Location Accuracy Analytics of key issue 9 | Nokia, Nokia Shanghai-Bell | Rel-18 | Merged into S2-2306104 | Dimitris (Lenovo) suggests to use S2-2304268 as a baseline which includes location accuracy predictions Amy (vivo) considers this CR is not clear and asks for clarifications. Thomas(Nokia) replies to Amy and Dimitris. Accepts to merge the CR into S2-2304268 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.23.2 | - | - | - | Key issue #10: Interactions with MDAS/MDAF | - | - | Docs:=2 | - | |
| 9.23.2 | S2-2304454 | CR | Approval | 23.288 CR0597R2 (Rel-18, 'B'): Procedure for requesting and collecting analytics from MDAF | Lenovo Future Communications | Rel-18 | Revision of S2-2302833 from S2#155. Postponed | Wang Yuan (Huawei) has strong concerns for this contribution. Belen (Ericsson) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2304905 | CR | Approval | 23.288 CR0801 (Rel-18, 'B'): Procedure for analytics collection from MDAF | Huawei, HiSilicon | Rel-18 | Postponed | Costas (Lenovo) objects S2-2304905 <file:///C:/Users/ksamdanis/Downloads/Docs/S2-2304905.zip> Wang Yuan (Huawei) responds to Costas. Costas (Lenovo) responds to Yuan. Wang Yuan (Huawei) provides r01 to merge S2-2304454 into S2-2304905 to move forward, and suggest Costas(Lenovo) to initiate a LS to SA5 to check whether MDA capability can already be provided from MDAF. Costas (Lenovo) comments of proposal. Yuan (Huawei)replies to Costas. ==== Revisions Deadline ==== Costas (Lenovo) please note that this topic was not in the agenda in the previous meeting. The important part is to ensure that we standardize a solution that works. ==== Comments Deadline ==== | Postponed |
| 9.23.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=44 | - | |
| 9.23.2 | S2-2304789 | CR | Approval | 23.288 CR0788 (Rel-18, 'B'): KI#1: Resolving EN regarding Analytics feedback information | ETRI | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304078 | CR | Approval | 23.288 CR0739 (Rel-18, 'C'): Resolving ENs about requesting the accuracy report | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Check clauses affected! | NOT HANDLED | |
| 9.23.2 | S2-2304534 | CR | Approval | 23.288 CR0760 (Rel-18, 'B'): Update Analytics/ML Model Accuracy Monitoring Functional Description | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304917 | CR | Approval | 23.288 CR0805 (Rel-18, 'B'): Remove EN on accuracy deviation | China Telecom | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304538 | CR | Approval | 23.288 CR0762 (Rel-18, 'B'): AnLF Accuracy Monitoring Description and Discovery | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304465 | CR | Approval | 23.501 CR4319 (Rel-18, 'B'): NWDAF Discovery principle enhancements for Analytics/ML Model Accuracy Monitoring in TS 23.501 | China Mobile | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304464 | CR | Approval | 23.502 CR4014 (Rel-18, 'B'): Enhance NRF services for Analytics ML Model Accuracy Monitoring in TS 23.502 | China Mobile | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304042 | CR | Approval | 23.288 CR0735 (Rel-18, 'F'): Updates on Input data collection | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304044 | CR | Approval | 23.501 CR4194 (Rel-18, 'F'): PFD determination corrections | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304564 | CR | Approval | 23.501 CR4347 (Rel-18, 'F'): Updates on NEF(PFDF) support for PFD Determination | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2305083 | CR | Approval | 23.288 CR0811 (Rel-18, 'F'): KI#2 Correction on input and output tables for PFD Determination analytics | Samsung | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2305091 | CR | Approval | 23.503 CR1020 (Rel-18, 'F'): Correction on PFD Determination analytics | Samsung Electronics France SA | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.23.2 | S2-2305093 | CR | Approval | 23.503 CR1021 (Rel-18, 'F'): KI#2 PFD management based on NWDAF analytics | Samsung | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2305104 | CR | Approval | 23.288 CR0812 (Rel-18, 'C'): KI#3 Discovery of NWDAF for roaming capability | Samsung | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2305108 | CR | Approval | 23.288 CR0813 (Rel-18, 'C'): KI#3 Support of slice-specific analytics in roaming scenarios | Samsung | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304893 | CR | Approval | 23.288 CR0793 (Rel-18, 'B'): Procedures for network data analytics in roaming | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304900 | CR | Approval | 23.288 CR0797 (Rel-18, 'C'): Update the procedure of ML Model retrieval from ADRF | Huawei, HiSilicon | Rel-18 | Wang Yuan (Huawei) merges S2-2304030,S2-2304281,S2-2304462,S2-2304550,S2-2304555 into S2-2304900 and provides r01. | NOT HANDLED | |
| 9.23.2 | S2-2304281 | CR | Approval | 23.288 CR0747 (Rel-18, 'B'): ADRF model retrieval service operations | NTT DOCOMO | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304462 | CR | Approval | 23.288 CR0758 (Rel-18, 'C'): Consolidating ADRF MLmodelmanagement service in case of multiple ML models | Nokia Italy | Rel-18 | CR Cover sheet error! Check Affected Clauses! | NOT HANDLED | |
| 9.23.2 | S2-2304550 | CR | Approval | 23.288 CR0764 (Rel-18, 'C'): ADRF service operation update for ML model retrieval | Intel | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304555 | CR | Approval | 23.288 CR0769 (Rel-18, 'C'): General clause update for ML model(s) retrieval from ADRF | Intel | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304902 | CR | Approval | 23.288 CR0798 (Rel-18, 'C'): Data Storage Management Update | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304309 | CR | Approval | 23.288 CR0749 (Rel-18, 'F'): Clarification on enhanced OSE analytics | LG Electronics | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304749 | CR | Approval | 23.503 CR0996 (Rel-18, 'F'): Clarification of URSP update by Redundant Transmission Experience analytics | ETRI | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304751 | CR | Approval | 23.288 CR0781 (Rel-18, 'F'): Clarification of Redundant Transmission Experience analytics | ETRI | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304264 | CR | Approval | 23.288 CR0741 (Rel-18, 'B'): Clarification on FL discovery procedure | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304552 | CR | Approval | 23.288 CR0766 (Rel-18, 'C'): Update to discovery and registration procedure for Federated Learning | Intel | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304077 | CR | Approval | 23.288 CR0738 (Rel-18, 'C'): Extending the maximum response time for FL status report | Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! Check clauses affected! | NOT HANDLED | |
| 9.23.2 | S2-2304034 | CR | Approval | 23.288 CR0733 (Rel-18, 'F'): Solving EN in General Procedure of Federated Learning | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304907 | CR | Approval | 23.288 CR0803 (Rel-18, 'B'): Enhancements on General procedure for FL among Multiple NWDAF Instances | Lenovo Future Communications | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304992 | CR | Approval | 23.288 CR0809 (Rel-18, 'B'): FL Server NWDAF behaviour related to the maximum response time | Samsung | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304621 | CR | Approval | 23.288 CR0777 (Rel-18, 'F'): EN for termination of Federated Learning operation | LG Electronics | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.23.2 | S2-2304272 | CR | Approval | 23.288 CR0745 (Rel-18, 'B'): Local training status and training data information reporting service | NTT DOCOMO | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304609 | CR | Approval | 23.288 CR0772 (Rel-18, 'C'): Refinement for FL procedure | Vivo | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304896 | CR | Approval | 23.288 CR0795 (Rel-18, 'B'): Update the procedures for Federated Learning model training | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304611 | CR | Approval | 23.288 CR0774 (Rel-18, 'C'): Updates for Nnwdaf_MLModelTraining service | Vivo | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304274 | CR | Approval | 23.288 CR0746 (Rel-18, 'B'): Local training data information reporting by ML Model Training service | NTT DOCOMO | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304624 | CR | Approval | 23.288 CR0778 (Rel-18, 'B'): Resolve ENs for Maximum Response Time | LG Electronics | Rel-18 | CR Cover sheet error! | NOT HANDLED | |
| 9.23.2 | S2-2304032 | CR | Approval | 23.288 CR0731 (Rel-18, 'F'): Update the Procedure for Preparation of Federated Learning | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304897 | CR | Approval | 23.501 CR4429 (Rel-18, 'F'): NWDAF discovery and selection for NWDAF with FL capability | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2305062 | CR | Approval | 23.502 CR4103 (Rel-18, 'F'): Clean up NWDAF Registration and Discovery procedure | QUALCOMM JAPAN LLC. | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304666 | CR | Approval | 23.288 CR0779 (Rel-18, 'B'): Resolve several editor's notes related to the finer granularity location | vivo | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304903 | CR | Approval | 23.288 CR0799 (Rel-18, 'C'): Enhancements to Analytics Reporting Information | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.23.2 | S2-2304226 | CR | Approval | 23.288 CR0740 (Rel-18, 'F'): Corrections for Location Accuracy Analytics | KDDI | Rel-18 | NOT HANDLED | ||
| 9.24.1 | - | - | - | Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) | - | - | Docs:=0 | - | |
| 9.24.2 | - | - | - | Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | - | - | Docs:=66 | - | |
| 9.24.2 | - | - | - | General | - | - | Docs:=2 | - | |
| 9.24.2 | S2-2303956 | LS In | Action | LS from RAN WG3: Reply LS on RAN impact for NPN enhancement in Rel-18 | RAN WG3 (R3-230813) | Rel-18 | Noted | Peter Hedman (Ericsson) propose to note the LS | Noted |
| 9.24.2 | S2-2303961 | LS In | Information | LS from RAN WG3: LS on required normative work for some Rel-18 topics | RAN WG3 (R3-230954) | Rel-18 | Noted | Peter Hedman (Ericsson) propose to note the LS | Noted |
| 9.24.2 | - | - | - | KI#2 related | - | - | Docs:=7 | - | |
| 9.24.2 | - | - | - | N3IWF selection for emergency services | - | - | Docs:=9 | - | |
| 9.24.2 | S2-2303930 | LS In | Action | LS from CT WG1: LS on N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | CT WG1 (C1-231181) | Rel-18 | Responses drafted in S2-2304337, S2-2304405, S2-2304414. Final response in S2-2305729 ZTE contact | Peter Hedman (Ericsson) provides comments and proposes to first agree on general direction i.e. allowing selection of N3IWF in SNPN Josep (Deutsche Telekom) comments, prefers a minimalistic approach. Saso (Intel) supports allowing selection of N3IWF in SNPN Huan (vivo) comments Marco (Huawei) agrees with minimalistic approach Huan (vivo) agrees with minimalistic approach Haris(Qualcomm) comments Marco( Comment) on minimalistic approach Haris(Qualcomm) responds to Marco Peter Hedman (Ericsson) comments Marco (Huawei) answer to Haris(Qualcomm) | Replied to |
| 9.24.2 | S2-2304337 | LS OUT | Approval | [DRAFT] Reply to LS on N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | vivo | Response to S2-2303930. Merged into S2-2305729 Merge into S2-2305729? | Peter Hedman (Ericsson) provides comments that we should use 4414 or 4405 as reply, I hope ok ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged | |
| 9.24.2 | S2-2304405 | LS OUT | Approval | [DRAFT] Reply to LS on N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | Ericsson | Rel-18 | Response to S2-2303930. Merged into S2-2305729 Merge into S2-2305729? | Peter Hedman (Ericsson) ok to use 4414 as reply and note this one ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304414 | LS OUT | Approval | [DRAFT] Reply LS on N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | Qualcomm | Rel-18 | Response to S2-2303930. r00 agreed. Revised to S2-2305729, merging S2-2304405. | Peter Hedman (Ericsson) provides comments to give LS a rev number for cleanup ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305729 | LS OUT | Approval | Reply LS on N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | SA WG2 | Rel-18 | Revision of S2-2304414r00, merging S2-2304405. Approved | Approved | |
| 9.24.2 | S2-2304207 | CR | Approval | 23.501 CR4239 (Rel-18, 'F'): Operator Identifier based emergency SNPN N3IWF FQDN | Qualcomm Incorporated | Rel-18 | Merged into S2-2305765 | Marco (Huawei) comments Huan (vivo) comments Haris(Qualcomm) responds Peter Hedman (Ericsson) provides comments Marco (huawei) answer to Peter Hedman (Ericsson) ==== Revisions Deadline ==== Peter Hedman (Ericsson) suggests to mark as merged into 04404 Marco (Huawei) agree to merge to 4404 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304338 | CR | Approval | 23.501 CR4275 (Rel-18, 'F'): N3IWF selection for emergency services | vivo | Rel-18 | Merged into S2-2305765 | Haris(Qualcomm) comments and proposes a way forward Huan (vivo) provides r01 Marco (Huawei) provide r02 Peter Hedman (Ericsson) we still have no confirmation whether we move forward with 4404? Marco (Huawei) ok to go ahead with 4404 ==== Revisions Deadline ==== Huan (vivo) is ok to go ahead with 4404 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304404 | CR | Approval | 23.501 CR4300 (Rel-18, 'F'): N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305765, merging S2-2304338 and S2-2304207 | Marco (Huawei) comments Huan (vivo) comments Peter Hedman (Ericsson) provides comments Marco (Huawei) answer to Peter Hedman (Ericsson) Haris(Qualcomm) provides r01 Peter Hedman (Ericsson) ok with r01 Marco (Huawei) comment r01 Huan (vivo) provides r02 Peter Hedman (Ericsson) provides r03 ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with any revision Huan (vivo) is ok with r03 Marco (Huawei) OK only to r03 Marco (Huawei) ok r02, 01 objects r00 Haris(Qualcomm) is ok r01, r03. R00 and R02 are possibly incorrect ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305765 | CR | Approval | 23.501 CR4300R1 (Rel-18, 'F'): N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | Ericsson | Rel-18 | Revision of S2-2304404r03, merging S2-2304338 and S2-2304207. Approved | Agreed | |
| 9.24.2 | - | - | - | N3IWF selection for Onboarding | - | - | Docs:=8 | - | |
| 9.24.2 | S2-2304476 | LS OUT | Approval | [DRAFT] Reply LS on LI requirements applicable to non-3GPP access to SNPNs | Qualcomm | Rel-18 | Response to S2-2302197 (noted at S2#155). r01 agreed. Revised to S2-2305766. | Peter Hedman (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305766 | LS OUT | Approval | Reply LS on LI requirements applicable to non-3GPP access to SNPNs | SA WG2 | Rel-18 | Revision of S2-2304476r01. Approved | Approved | |
| 9.24.2 | S2-2304123 | CR | Approval | 23.501 CR4215 (Rel-18, 'F'): Correction to N3IWF selection for Onboarding | Intel | Rel-18 | Noted | Peter Hedman (Ericsson) provides comments and support the CR Huan (vivo) provides comments Yishan (Huawei) provides comments Haris(Qualcomm) is also ok to move fwd with this CR proposal Saso (Intel) comments Yishan (Huawei) replies to Saso (Intel) Saso (Intel) replies to Yishan and Huan ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r00, but we should either this or 4205 Yishan (Huawei): r00 should be marked as noted Saso (Intel) is OK to NOTE and move forward with 4205 ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304205 | CR | Approval | 23.501 CR4238 (Rel-18, 'F'): Additional requirements for N3IWF selection for onboarding | Qualcomm | Rel-18 | Approved | Huan (vivo) provides comments Peter Hedman (Ericsson) provides question ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r00, but we should either this or 4123 Yishan (Huawei) is ok with r00 Saso (Intel) is ok with r00 Huan (vivo) is ok with r00 ==== Comments Deadline ==== | Agreed |
| 9.24.2 | S2-2304339 | CR | Approval | 23.501 CR4276 (Rel-18, 'B'): Clarification on N3IWF selection for onboarding | vivo | Rel-18 | Noted | Haris(Qualcomm) suggests to move fwd with S2-2304205 or S2-2304123 Huan (vivo) provides feedback ==== Revisions Deadline ==== Peter Hedman (Ericsson) suggests to move forward with S2-2304205 or S2-2304123 Yishan (Huawei): r00 should be marked as noted ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304496 | CR | Approval | 23.502 CR4020 (Rel-18, 'B'): Support for onboarding via untrusted non-3GPP access | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305767. Overlaps with S2-2304879 | Zhendong (ZTE) provides r01. Yishan (Huawei) is ok with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305767 | CR | Approval | 23.502 CR4020R1 (Rel-18, 'B'): Support for onboarding via untrusted non-3GPP access | Huawei, HiSilicon, ZTE | Rel-18 | Revision of S2-2304496r01. Approved | Agreed | |
| 9.24.2 | S2-2304878 | CR | Approval | 23.501 CR4424 (Rel-18, 'F'): Clarification on the onboarding indication | ZTE | Rel-18 | Approved | Agreed | |
| 9.24.2 | - | - | - | Other KI#2 related | - | - | Docs:=10 | - | |
| 9.24.2 | S2-2304100 | CR | Approval | 23.316 CR2083 (Rel-18, 'F'): Content of home network domain when SUPI is IMSI | Ericsson | Rel-18 | r02 agreed. Revised to S2-2305768. | Marco (Huawei) comments and provide r01 Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with any revision ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305768 | CR | Approval | 23.316 CR2083R1 (Rel-18, 'F'): Content of home network domain when SUPI is IMSI | Ericsson | Rel-18 | Revision of S2-2304100r02. Approved | Agreed | |
| 9.24.2 | S2-2304244 | DISCUSSION | Discussion | On access to SNPN through wireline network using FN-RG | OPPO | Noted | Marco (Huawei) this is a discussion paper so it shall be NOTED ==== Comments Deadline ==== | Noted | |
| 9.24.2 | S2-2305336 | CR | Approval | 23.501 CR4185R1 (Rel-18, 'B'): Access to SNPN through wireline access network using FN-RG | OPPO | Rel-18 | Revision of S2-2303139 from S2#155. Noted | Marco (Huawei) comment that this is not needed Peng Tan (OPPO) provides clarification Yildirim (Charter) comments and questions the need of the CR. Peng Tan (OPPO) responded to Yildirim (Charter) comments and questions Yildirim (Charter) replies to Peng Tan (OPPO). Peng Tan (OPPO) response to Yildirim Yildirim (Charter) replies. Peng Tan (OPPO) responds to Yildirim Omkar (CableLabs) comments. Peng Tan (OPPO) responds to Omkar (CableLabs) comments. Huan (vivo) provides comments. Omkar (CableLabs) responds to Peng (Oppo). Marco (Huawei) comments and consider this CR not needed Peng (OPPO) responds to Huan (Vivo) and Omkar (CableLabs). Peng (OPPO) responds to Marco (Huawei) and Omkar (CableLabs). Marco (Huawei) even if we may agree the note, 23.501 is not the right place. Peng (OPPO) responds to Marco (Huawei), and provides r01 ==== Revisions Deadline ==== Marco (Huawei) I can live with r01. Yildirim (Charter) objects any revision because the use case intended is not applicable to FN-RG so CR is not needed. Peng (OPPO) thanks Marco (Huawei) for living with r01, and responds Yildirim (Charter) and Omkar (CableLabs) regarding the details of the use case in DP. ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304701 | CR | Approval | 23.316 CR2092 (Rel-18, 'B'): SUPI and SUCI for FN-BRG support for PLMN and SNPN | OPPO | Rel-18 | Noted | Marco (Huawei) comments Peng Tan (OPPO) provides clarification Marco (Huawei) asnwer Peng (OPPO) provides r01 Omkar (CableLabs) comments. Peng (OPPO) responds to Omkar (CableLabs) Omkar (CableLabs) seeks clarification. Omkar (CableLabs) responds to Peng (OPPO). Peng (OPPO) provides r02 ==== Revisions Deadline ==== Marco (Huawei) ok R02 object r00 & r01 ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304494 | DISCUSSION | Discussion | Discussion on N5CW device using decorated NAI | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.24.2 | S2-2304495 | CR | Approval | 23.502 CR4019 (Rel-18, 'B'): Support for N5CW device using decorated NAI | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305770. | Peter Hedman (Ericsson) provides comments Marco (Huawei) provides r01 fixing a typo ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305770 | CR | Approval | 23.502 CR4019R1 (Rel-18, 'B'): Support for N5CW device using decorated NAI | Huawei, HiSilicon | Rel-18 | Revision of S2-2304495r01. Approved | Agreed | |
| 9.24.2 | S2-2304766 | CR | Approval | 23.316 CR2095 (Rel-18, 'B'): Support of wireline access as access to NPI-NPN and to SNPN | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2305771. | Haris(Qualcomm) asks questions Marco (Huawei) answer to Haris(Qualcomm) and provides r01 Peter Hedman (Ericsson) provides comments and would prefer to not have any open FFS Marco (Huawei) provide r02 Haris(Qualcomm) provides r03 ==== Revisions Deadline ==== Marco (Huawei) OK with r03 ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305771 | CR | Approval | 23.316 CR2095R1 (Rel-18, 'B'): Support of wireline access as access to NPI-NPN and to SNPN | Huawei, HiSilicon | Rel-18 | Revision of S2-2304766r03. Approved | Agreed | |
| 9.24.2 | - | - | - | KI#4 SNPN selection for Localized Services | - | - | Docs:=22 | - | |
| 9.24.2 | S2-2303932 | LS In | Action | LS from CT WG1: Reply LS on issues related to SNPN selection for localized services | CT WG1 (C1-231198) | Rel-18 | Responses drafted in S2-2304096, S2-2304305, S2-2304545. Final response in S2-2305772 Ericsson contact | Replied to | |
| 9.24.2 | S2-2304096 | LS OUT | Approval | [DRAFT] Reply LS on issues related to SNPN selection for localized services | Ericsson | Rel-18 | Response to S2-2303932. r05 agreed. Revised to S2-2305772, merging S2-2304545 and S2-2304305 | Yishan (Huawei) asks for clarification Peter Hedman (Ericsson) provides reply Sebastian (Qualcomm) provides r01 Peter Hedman (Ericsson) provides comments Yishan (Huawei) suggests to keep the wording in r00. Guanzhou (InterDigital) comments and OK with r00 or r01. Chia-Lin (MediaTek) prefers the response in r01 Yishan (Huawei) provides r02 Jianning (Xiaomi) is ok with r00, r01 and r02 Peter Hedman (Ericsson) ok with r00, r01, r02 and provides comments Peter Hedman (Ericsson) provides r03 Sebastian (Qualcomm) provides 04 Chia-Lin (MediaTek) disagreed to ask CT1 whether user controlled prioritized should be associated with validity information. Prefers to keep r01 Peter Hedman (Ericsson) provides r05 Yishan (Huawei) provides r06 and questions what's the value to send the LS if the coordination with CT1 part is removed. ==== Revisions Deadline ==== Peter Hedman (Ericsson) provides reply to Yishan Peter Hedman (Ericsson) ok with any revision Sebastian (Qualcomm) is ok with r04 and r05; objects to other versions Chia-Lin (MediaTek) can only accept r05 Yishan (Huawei) prefers r06 but is also ok with r05 as a way forward ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305772 | LS OUT | Approval | Reply LS on issues related to SNPN selection for localized services | SA WG2 | Rel-18 | Revision of S2-2304096r05, merging S2-2304545 and S2-2304305. Approved | Approved | |
| 9.24.2 | S2-2304305 | LS OUT | Approval | [DRAFT] Reply LS on issues to SNPN selection for localized services | MediaTek Inc. | Rel-18 | Response to S2-2303932. Merged into S2-2305772 | Peter Hedman (Ericsson) provides question if we can use 04096 as basis Chia-Lin (MediaTek) is ok to use 04096 as basis for LS OUT to CT1 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304545 | LS OUT | Approval | [DRAFT] Reply CT WG1 LS on issues related to SNPN selection for localized services | OPPO | Response to S2-2303932. Merged into S2-2305772 | Peter Hedman (Ericsson) provides question if we can use 4096 as basis Peng Tan (OPPO) is ok to use 4096 as basis to reply the CT1 LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged | |
| 9.24.2 | S2-2304094 | CR | Approval | 23.501 CR4205 (Rel-18, 'C'): SNPN selection for access to localized services | Ericsson | Rel-18 | r12 agreed. Revised to S2-2305773, merging S2-2304484, S2-2304376, S2-2304375 and S2-2304303 New list, removing note i.e. location info not for aid only | Peter Hedman (Ericsson) provides comments as to discuss general direction Pallab (Nokia) respond to Peter Sebastian (Qualcomm) comments Guanzhou (InterDigital) provides comments. Myungjune (LGE) comments. Jianning (Xiaomi) provides comment Fei (OPPO) comments. Chia-Lin (MediaTek) provides comments Peter Hedman (Ericsson) provides comments and r01 Yishan (Huawei) provides comments on r01 Guanzhou (InterDigital) responds to Chia-Lin (MediaTek) Peter Hedman (Ericsson) provides r02 Yishan (Huawei) provides r03 Chia-Lin (MediaTek) responds to Chuanzhou (InterDigital) Chia-Lin (MediaTek) have concern with adding user controlled list for LS and provides r04 without the EN Yishan (Huawei) agrees with Chia-Lin (MediaTek) and provides r05 Sebastian (Qualcomm) provides r06 Pallab (Nokia) comments on user controlled list Jianning (Xiaomi) replies to Chia-Lin (Media Tek) Pallab (Nokia) provides r07 merging r01 of 4376 Jianning (Xiaomi) provide comment on r07 and provide r08 Peter Hedman (Ericsson) provides comments and r09 Chia-Lin (MediaTek) provides r10 and responds to Jianning (Xioami) Peng (OPPO) provides comments on r10 Yishan (Huawei) provides r11 Chia-Lin (MediaTek) provides r12 Jianning (Xiaomi) replies to Chia-Lin (MediaTek) ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with any of the revs, see below for attempted summary of latest revs Pallab (Nokia) proposes to approve r11. r12 needs more editorial corrections Jianning (Xiaomi) comment on r11 which is also need further updates Chia-Lin (MediaTek) can only accept r12(objects all revisions and original CR) and is ok with the changes from Pallab (Nokia) for r12 Yishan (Huawei) suggests to go with r11 and is not ok with r12 which contains technical issues Sebastian (Qualcomm) replies to Yishan Chia-Lin (MediaTek) agrees with Sebastian's view on the need for two triggers Sebastian (Qualcomm) ok with r10; also ok with r12 with the following changes: reinstation of ' Optionally if the UE supports access to an SNPN providing access for Localized Services:' and addition of ' changes from ' and 'and' into 'If a validity condition in Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services changes from met to not met (and vice versa), the UE shall attempt selection and registration on an SNPN based on the above bullets (a) to (d).'; not ok with removal of 'vice versa' as (I think) proposed by Pallab; objects to other versions Peter Hedman (Ericsson) also ok with r12 + changes from Sebastian (see draft folder) Guanzhou (InterDigital) is OK with revised r12. Yishan (Huawei) is ok with revised r12 as a way forward ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305773 | CR | Approval | 23.501 CR4205R1 (Rel-18, 'C'): SNPN selection for access to localized services | Ericsson | Rel-18 | Revision of S2-2304094r12, merging S2-2304484, S2-2304376, S2-2304375 and S2-2304303. Approved | Agreed | |
| 9.24.2 | S2-2304300 | DISCUSSION | Discussion | Discussion on Equivalent SNPN used by UE for Localized Services | MediaTek Inc. | Rel-18 | Noted | Noted | |
| 9.24.2 | S2-2304301 | CR | Approval | 23.501 CR4267 (Rel-18, 'B'): The equivalent SNPN used by the UE for Localized Services | MediaTek Inc. | Rel-18 | Postponed | Lalith (Samsung) comments Peter Hedman (Ericsson) provides comments Yishan (Huawei) provides comments Lalith (Samsung) provides comments Pallab (Nokia) comments Chia-Lin (MediaTek) provides the clarification Sebastian (Qualcomm) supports MediaTek's view Fei (OPPO) comments. Guanzhou (InterDigital) comments. Pallab (Nokia) responds to Chia-Lin (MediaTek) Chia-Lin (MediaTek) responds to Pallab(Nokia) Chia-Lin (MediaTek) responds to Guanzhou (InterDigital) Chia-Lin (MediaTek) responds to Yishan(Huawei) Yishan (Huawei) replies to Chia-Lin (MediaTek) Fei (OPPO) provides commets. Jianning (Xiaomi) provides views Chia-Lin (MediaTek) replies to Yishan (Huawei) Lalith(Samsung) agrees with Yishan (Huawei) on letting CT1 lead on aspects of SNPN selection related to ESNPN. Josep (Deutsche Telekom) comments, is also not in favour of having a different meaning of 'equivalent' for SNPNs and PLMNs. Lalith(Samsung) provides r01 Guanzhou (InterDigital) further comments. Josep (Deutsche Telekom) comments. Jianning (Xiaomi) provide comments Lalith (Samsung) requests to make actionable comments. Josep (Deutsche Telekom) supports the way forward with the assumption. Pallab (Nokia) supports the way forward proposed by Josep (Deutsche Telekom). Lalith (Samsung) provides r02 Peter Hedman (Ericsson) provides question Guanzhou (InterDigital) provides further comments Yishan (Huawei) provides question Chia-Lin (MediaTek) provides r03 Fei (OPPO) provides r04. ==== Revisions Deadline ==== Myungjune (LGE) comments Myungjune (LGE) replies to Lalith (Samsung) Fei (OPPO) replied. Pallab (Nokia) proposes to POSTPONE Peter Hedman (Ericsson) provides comments and suggests to approve r01 Yishan (Huawei) comments Chia-Lin (MediaTek) comments on r04 and suggest go with r01 Lalith(Samsung) comments Sebastian (Qualcomm) is ok with r01 and r02, objects to other versions; also ok to postpone Fei (OPPO) ok to postpone as well. Yishan (Huawei) is ok to postpone as well. Guanzhou (InterDigital) OK to postpone. Chia-Lin (MediaTek) is ok to postpone this CR ==== Comments Deadline ==== | Postponed |
| 9.24.2 | S2-2305334 | DISCUSSION | Discussion | Discussion on Equivalent SNPNs for Localized services | Samsung | Rel-18 | Noted | Noted | |
| 9.24.2 | S2-2305337 | CR | Approval | 23.501 CR4554 (Rel-18, 'F'): Equivalent SNPN for localized service | Samsung | Rel-18 | Merged into S2-2304301 (Postponed) eSNPN EN | Peter Hedman (Ericsson) provides comments and prefer to use 04301 for the discussion Lalith(Samsung) comments Pallab (Nokia) comments Lalith (Samsung) comments Sebastian (Qualcomm) objects to the CR Guanzhou (InterDigital) provides comments. Yishan (Huawei) provides comments Pallab (Nokia) responds to Lalith (Samsung) Lalith(Samsung) agrees with Yishan (Huawei) Lalith (Samsung) replies to Pallab (Nokia) Lalith(Samsung) provides comments. Lalith (Samsung) OK to mark this CR merged into 4301 Guanzhou (InterDigital) responds to Lalith(Samsung). Lalith(Samsung) replies to Guanzhou (InterDigital). ==== Revisions Deadline ==== Peter Hedman (Ericsson) author already agreed to mark as merged into 4301 ==== Comments Deadline ==== | Postponed |
| 9.24.2 | S2-2304302 | CR | Approval | 23.501 CR4268 (Rel-18, 'B'): A periodically higher priority SNPN search and selection | MediaTek Inc. | Rel-18 | Noted | Fei (OPPO) comments Pallab (Nokia) provides comments Peter Hedman (Ericsson) provides comments Josep (Deutsche Telekom) asks questions for clarificaiton. Chia-Lin (MediaTek) provides the response Yishan (Huawei) provides comments Pallab (Nokia) provides further comments Chia-Lin (MediaTek) responds to Pallab (Nokia) and Yishan (Huawei) Josep (Deutsche Telekom) comments, asks question for clarification. Pallab (Nokia) responds Chia-Lin (MediaTek) and suggests that the category of the CR needs to be changed to F and probably moved to another agenda item as it is not related to localised services Peter Hedman (Ericsson) provides r01 Yishan (Huawei) shares concerns. Pallab (Nokia) also proposes to POSTPONE the CR as it is a CAT F CR on Rel-17. Fei (OPPO) also proposes to postpone the CR. ==== Revisions Deadline ==== Josep (Deutsche Telekom) also proposes to postpone. Chia-Lin (MediaTek) is ok to postpone this CR ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304303 | CR | Approval | 23.501 CR4269 (Rel-18, 'B'): UE discover, select and access to a Hosting network for Localized services | MediaTek Inc. | Rel-18 | Merged into S2-2305773 With separate location assistance info | Peter Hedman (Ericsson) provides comments whether we can use 04094? Chia-Lin (MediaTek) is ok to use 04094 as basis? ==== Revisions Deadline ==== Peter Hedman (Ericsson) mark as merged into 04094 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304375 | CR | Approval | 23.501 CR4289 (Rel-18, 'B'): Support for validity conditions in user controlled prioritized list of preferred SNPNs. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2305773 User controlled list | Peter Hedman (Ericsson) provides comments and question the need for the changes Guanzhou (InterDigital) shares the similar view that the proposed change is not needed. Yishan (Huawei) provides comments Pallab (Nokia) responds to Ericsson, Huawei and InterDigital Pallab (Nokia) responds to Yishan (Huawei) Jianning (Xiaomi) is supportive for this CR Huan (vivo) provides comments Jianning (Xiaomi) replies to Huan (vivo) Peter Hedman (Ericsson) provides comments that content was merged into 4094 and then EN added Pallab (Nokia) agrees to mark this CR as merged to 4094 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2305158 | CR | Approval | 23.501 CR4508 (Rel-18, 'B'): Clarification for CH controlled lists for accessing Localized Services for Manual Selection | Samsung | Rel-18 | Source modified on 4/7/2023. Original source : Samsung. Noted | Peter Hedman (Ericsson) provides comments Sebastian (Qualcomm) objects to the CR Josep (Deutsche Telekom) is also not in favour of mixing automatic and manual network selection as proposed in the CR. Naman (Samsung) replies to Ericsson, Qualcomm and DT Naman (Samsung) replies and provides r01 Yishan (Huawei) asks question for r01 Naman (Samsung) repllies to Huwaei Josep (Deutsche Telekom) comments. This text belongs in TS 23.122. ==== Revisions Deadline ==== Josep (Deutsche Telekom) objects to this CR. Naman (Samsung) is okay to note the CR Peter Hedman (Ericsson) ok to note the CR Sebastian (Qualcomm) objects to the CR (all versions) ==== Comments Deadline ==== | Noted |
| 9.24.2 | S2-2304484 | CR | Approval | 23.501 CR4325 (Rel-18, 'B'): CH controlled prioritized list of preferred SNPNs and GINs for access for localized services in SNPN | Huawei, HiSilicon | Rel-18 | Merged into S2-2305773 New list, location kept as for aid | Peter Hedman (Ericsson) provides comments whether we can use 04094? Yishan (Huawei) replies to Peter (Ericsson) Sebastian (Qualcomm): should be marked merged into 4094 ==== Revisions Deadline ==== Peter Hedman (Ericsson) should be marked as merged into 4094 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304485 | CR | Approval | 23.502 CR4017 (Rel-18, 'B'): CH controlled list of preferred SNPNs and GINs for access for localized services in SNPN | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2305774, merging S2-2305240 and S2-2304908 | Peter Hedman (Ericsson) provides r01 Yishan (Huawei) replies Yishan (Huawei) provides r02 Peter Hedman (Ericsson) provides comments that intention was keep alignment Yishan (Huawei) replies to Peter (Ericsson) and provides r03 ==== Revisions Deadline ==== Huan (vivo) is OK to r03 and asks to add vivo as cosigning company Peter Hedman (Ericsson) ok with r03 ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305774 | CR | Approval | 23.502 CR4017R1 (Rel-18, 'B'): CH controlled list of preferred SNPNs and GINs for access for localized services in SNPN | Huawei, HiSilicon, Ericsson, vivo | Rel-18 | Revision of S2-2304485r03, merging S2-2305240 and S2-2304908. Approved | Agreed | |
| 9.24.2 | S2-2304304 | CR | Approval | 23.501 CR4270 (Rel-18, 'B'): Network access control when the UE accesses an SNPN that provides access for Localized Services | MediaTek Inc. | Rel-18 | r03 agreed. Revised to S2-2305775. Network access control (UDM) | Sebastian (Qualcomm) provides 01 Yishan (Huawei) provides r02 Peter Hedman (Ericsson) provides proposed rewording in r03 Chia-Lin (MediaTek) is ok with r03 ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03, objects to r02, r01, r00 ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305775 | CR | Approval | 23.501 CR4270R1 (Rel-18, 'B'): Network access control when the UE accesse an SNPN that provides access for Localized Services | MediaTek Inc., LG Electronics | Rel-18 | Revision of S2-2304304r03. Approved | Agreed | |
| 9.24.2 | S2-2304908 | CR | Approval | 23.502 CR4086 (Rel-18, 'B'): Clarification on validity condition of CH controlled prioritized lists of preferred SNPNs and GINs | vivo | Rel-18 | Merged into S2-2305774 23.502 other changes | Peter Hedman (Ericsson) provides comments and propose to merge into 04485 Pallab (Nokia) provides comments Huan (vivo) provides feedback and agree to merge into 04485 ==== Revisions Deadline ==== Peter Hedman (Ericsson) should be marked as merge into 2304485 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2305240 | CR | Approval | 23.502 CR4133 (Rel-18, 'C'): Update the list of preferred SNPN with validity condition | Xiaomi | Rel-18 | Merged into S2-2305774 23.502 not same title, overlaps but proposes to remove NOTE | Peter Hedman (Ericsson) provides comments and propose to merge into 04485. Jianning (Xiaomi) agree to meger into 04485 ==== Revisions Deadline ==== Peter Hedman (Ericsson) should be marked as merge into 2304485 ==== Comments Deadline ==== | Merged |
| 9.24.2 | - | - | - | SoR provisioning | - | - | Docs:=6 | - | |
| 9.24.2 | S2-2304332 | DISCUSSION | Agreement | Discussion on Update UE with Prioritized List of Hosting Network Information via external parameter provisioning | vivo, Huawei, HiSilicon, China Telecom | Rel-18 | Noted | Noted | |
| 9.24.2 | S2-2304374 | CR | Approval | 23.501 CR4288 (Rel-18, 'B'): Configuration of Credentials Holder for determining SNPN selection information (Annex N.x) | Nokia, Nokia Shanghai Bell | Rel-18 | r06 agreed. Revised to S2-2305776, merging S2-2305030 and S2-2304639 | Peter Hedman (Ericsson) provides r01 Yishan (Huawei) provides comments Genadi (Lenovo) looks for clarifications to the initial version and to r01. Xiaowen Sun (vivo) provides comments. Pallab (Nokia) responds to Peter Hedman (Ericsson) Pallab (Nokia) responds to Yishan (Huawei) Pallab (Nokia) responds to Genadi (Lenovo) Pallab (Nokia) responds to Xiaowen Sun (vivo) Yishan (Huawei) replies to Pallab (Nokia) Genadi (Lenovo) responds to Pallab (Nokia) and looks for further clarifications. Peter Hedman (Ericsson) provides reply Xiaowen (vivo) provides reply Yishan (Huawei) provides r02 as way forward Naman (Samsung) asks clarifications for r02 Josep (Deutsche Telekom) comments, provides r03 with clarifications. Peter Hedman (Ericsson) provides comments Xiaowen (vivo) shares the same view with Naman (Samsung) and provides r04. Pallab (Nokia) provides r05. Genadi (Lenovo) provides r06. Xiaowen (vivo) is ok with r05. Xiaowen (vivo) is fine with r05 can live with r06. Yishan (Huawei) is also fine with r05 and can live with r06 ==== Revisions Deadline ==== Pallab (Nokia) is OK with r05 and r06. Peter Hedman (Ericsson) also ok with r06 or r05 (and of course some of the earlier revisions) ==== Comments Deadline ==== | Revised |
| 9.24.2 | S2-2305776 | CR | Approval | 23.501 CR4288R1 (Rel-18, 'B'): Configuration of Credentials Holder for determining SNPN selection information (Annex N.x) | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304374r06, merging S2-2305030 and S2-2304639. Approved | Agreed | |
| 9.24.2 | S2-2304639 | CR | Approval | 23.502 CR4043 (Rel-18, 'B'): TS23.502 External Parameter Provisioning | vivo, Huawei, HiSilicon, China Telecom | Rel-18 | Merged into S2-2305776 | Peter Hedman (Ericsson) provides comments and propose to progress the approach in 04374 Sebastian (Qualcomm) comments and proposes to note Xiaowen (vivo) provides response Yishan (Huawei) shares the same view as Xiaowen (vivo) Pallab (Nokia) supports the view from Qualcomm and Ericsson and proposes to NOTE this CR. Xiaowen (vivo) responses to Pallab (Nokia). Genadi (Lenovo) supports the proposal in general and have comments. Pallab (Nokia) responds to Xiaowen (vivo) Yishan (Huawei) replies to Pallab (Nokia) Xiaowen(vivo) seconds Yishan (Huawei) Peter Hedman (Ericsson) suggests again to move forward with 04374 and note this as content wise it is merged Xiaowen (vivo) agree with Peter (Ericsson) to make 4374 as way forward. ==== Revisions Deadline ==== Peter Hedman (Ericsson) should be marked as merged into 04374 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2305029 | DISCUSSION | Agreement | Open issues on how to trigger the SOR provisioning to the UE | Lenovo | Rel-18 | Noted | Noted | |
| 9.24.2 | S2-2305030 | CR | Approval | 23.501 CR4465 (Rel-18, 'B'): Update to the SOR triggering procedure | Lenovo | Rel-18 | Merged into S2-2305776 | Peter Hedman (Ericsson) provides comments and propose to progress the approach in 04374 Sebastian (Qualcomm) supports comments by Ericsson Xiaowen Sun (vivo) asks for clarification. Pallab (Nokia) supports the view from Qualcomm and Ericsson. See also comments in S2-2304639 Genadi (Lenovo) responds to Pallab (Nokia), Peter (Ericsson) and Sebastian (Qualcomm). Genadi (Lenovo) responds to Xiaowen (vivo). Yishan (Huawei) provides comments Sebastian (Qualcomm) objects to the CR for reasons given earlier Genadi (Lenovo) responds to Yishan (Huawei). Peter Hedman (Ericsson) provides reply Yishan (Huawei) replies to Yishan (Huawei) Peter Hedman (Ericsson) proposes to note this and use 04374 Genadi (Lenovo) provides further clarifications. ==== Revisions Deadline ==== Pallab (Nokia) proposes to NOTE and responds to Genadi (Lenovo). Peter Hedman (Ericsson) should be marked as merged into 04374 Genadi (Lenovo) agrees with Peter (Ericsson) to mark this paper as merged into 04374. ==== Comments Deadline ==== | Merged |
| 9.24.2 | - | - | - | Other KI#4 related | - | - | Docs:=2 | - | |
| 9.24.2 | S2-2304376 | CR | Approval | 23.501 CR4290 (Rel-18, 'B'): UE deregistration when localised services validity conditions expire for SNPN | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2305773 | Xiaowen Sun (vivo) asks for clarification. Peter Hedman (Ericsson) provides comments Sebastian (Qualcomm) comments and proposes an alternative way forward Ashok (Samsung) comments Guanzhou (InterDigital) comments and proposes to note the CR. Yishan (Huawei) provides comments Pallab (Nokia) responds to Xiaowen Sun (vivo) Pallab (Nokia) requests Peter Hedman (Ericsson) to further clarify Pallab (Nokia) responds to Sebastian (Qualcomm) Pallab (Nokia) responds to Huawei, Samsung and InterDigital Josep (Deutsche Telekom) questions whether this is in line with the TR conclusions. Pallab (Nokia) responds to Josep (Deutsche Telekom) Chia-Lin (MediaTek) provides comments Sebastian (Qualcomm) provides r01 Pallab (Nokia) responds Sebastian (Qualcomm). OK with r01 and also OK to merge the proposal in r01 with 4094 Josep (Deutsche Telekom) comments that r01 looks OK. Yishan (Huawei) comments on r01 Pallab (Nokia) responds to Yishan (Huawei). Proposes to mark this as merged to 4094 ==== Revisions Deadline ==== Peter Hedman (Ericsson) Should be marked as merged into 04094 ==== Comments Deadline ==== | Merged |
| 9.24.2 | S2-2304562 | CR | Approval | 23.501 CR4346 (Rel-18, 'F'): Clarification for onboarding procedure for localized services | InterDigital | Rel-18 | Check Category - CR states {{No Category}}! Postponed | Xiaowen Sun (vivo) provides comments. Haris(Qualcomm) objects to the CR Pallab (Nokia) comments and also thinks the CR is not needed Peter Hedman (Ericsson) provides comments and if UE to indicate intention better to use PCO Guanzhou (InterDigital) replies to the comments. Naman (Samsung) provides comments Pallab (Nokia) responds to Guanzhou (InterDigital) Yishan (Huawei) asks for clarification Josep (Deutsche Telekom) comments, thinks this CR needs quite some polishing. Objects to r00 Guanzhou (InterDigital) responds to Pallab (Nokia) comments. Guanzhou (InterDigital) responds to the Yishan (Huawei). Yishan (Huawei) replies to Guanzhou Peter Hedman (Ericsson) provides suggestion Guanzhou (InterDigital) responds to the Josep (Deutsche Telekom) comments and provides r01. Josep (Deutsche Telekom) comments regarding SO-SNPN. Pallab (Nokia) responds to Guanzhou (InterDigital) and also comments on r01 Haris(Qualcomm) comments on r01 Peter Hedman (Ericsson) provides r02 Guanzhou (InterDigital) responds to Pallab (Nokia) and Haris (Qualcomm) comments and provide r0203. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03 or r02 Naman (Samsung) is OK with r02 or r03 as well Pallab (Nokia) provides comments on r02, r03. NOT OK to approve yet Josep (Deutsche Telekom) can live with r03. Guanzhou (InterDigital) responds to Pallab (Nokia) and suggests to approve r03. Pallab (Nokia) proposes to POSTPONE this as not all questions have been answered and we are not convinced that this new indication is needed. ==== Comments Deadline ==== | Postponed |
| 9.24.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=7 | - | |
| 9.24.2 | S2-2304879 | CR | Approval | 23.502 CR4081 (Rel-18, 'F'): Clarification on the onboarding indication | ZTE | Rel-18 | Overlaps with S2-2304496 | NOT HANDLED | |
| 9.24.2 | S2-2304095 | CR | Approval | 23.502 CR3961 (Rel-18, 'C'): SNPN selection for access to localized services | Ericsson | Rel-18 | NOT HANDLED | ||
| 9.24.2 | S2-2304245 | CR | Approval | 23.501 CR4250 (Rel-18, 'A'): SNPN automatic network selection | OPPO | Rel-18 | CR Cover sheet error! Not complete | NOT HANDLED | |
| 9.24.2 | S2-2304561 | CR | Approval | 23.501 CR4345 (Rel-18, 'B'): New Credentials Holder controlled prioritized list of preferred SNPNs for Localized Services | InterDigital Inc. | Rel-18 | Keeping validity optional, not complete, overlaps with other CRs | Guanzhou (InterDigital) considers this as merged into 4094. | NOT HANDLED |
| 9.24.2 | S2-2305239 | CR | Approval | 23.501 CR4534 (Rel-18, 'C'): Update to use new list of preferred SNPN with validity condition | Xiaomi | Rel-18 | not complete, overlaps with other CRs | Guanzhou (InterDigital) comments that the proposed change is not necessary. | NOT HANDLED |
| 9.24.2 | S2-2305359 | CR | Approval | 23.501 CR4562 (Rel-18, 'B'): On new list of CH controlled prioritized list of preferred SNPNs/GINs with validity information | OPPO | Rel-18 | not complete, overlaps with other CRs | NOT HANDLED | |
| 9.24.2 | S2-2304092 | CR | Approval | 23.501 CR4204 (Rel-18, 'C'): SoR provisioning clarification for localized service | Ericsson | Rel-18 | Xiaowen Sun (vivo) provides comments. | NOT HANDLED | |
| 9.25.1 | - | - | - | Study on Enhancement of 5G UE Policy (FS_eUEPO) | - | - | Docs:=0 | - | |
| 9.25.2 | - | - | - | Enhancement of 5G UE Policy (eUEPO) | - | - | Docs:=64 | - | |
| 9.25.2 | - | - | - | Evaluation and Conclusion for KI#3 (Provision consistent URSP to UE across 5GS and EPS) | - | - | Docs:=17 | - | |
| 9.25.2 | S2-2304027 | CR | Approval | 23.501 CR4190 (Rel-18, 'F'): KI#3 5GS to EPS mobility | Ericsson | Rel-18 | Approved | Agreed | |
| 9.25.2 | S2-2304028 | CR | Approval | 23.502 CR3952 (Rel-18, 'B'): KI#3 5GS to EPS mobility | Ericsson | Rel-18 | CC#4: r02 + changes agreed. Revised to S2-2306252. For CC#4 | Changhong (Intel) provides r01. Belen (Ericsson) is okay with the proposal to merge 4250 here DongYeon (Samsung) provides r02. ==== Revisions Deadline ==== Belen (Ericsson) is okay with r01, cannot only accept r02 without 'the possible enhancement (SM Policy Association Modification for UE policy information delivery over EPS) into the EN in 4.11.0a.2a.0.' DongYeon (Samsung) replies. DongYeon (Samsung) is Ok with r02 with this change: remove 'SM Policy Association Modification for UE policy information delivery over EPS' from the Editor's Note. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2306252 | CR | Approval | 23.502 CR3952R1 (Rel-18, 'B'): KI#3 5GS to EPS mobility | Ericsson, Intel, Samsung | Rel-18 | Revision of S2-2304028r02 + changes. CC#4: Approved | Agreed | |
| 9.25.2 | S2-2304029 | CR | Approval | 23.503 CR0946 (Rel-18, 'B'): Ki#3 UE Policy new PCRT | Ericsson | Rel-18 | Postponed | Pallab (Nokia) provides comments Zhuoyi (China Telecom) asks for clarification. Changhong (Intel) shares same view with Pallab and Zhuoyi and proposes to NOTE this paper. Belen (Ericsson) clarifies as requested. It also asks if concerns are addressed. DongYeon (Samsung) comments. DongYeon (Samsung) asks if we can postpone this CR. Belen (Ericsson) responds to comments Pallab (Nokia) agrees with the proposal from DongYeon (Samsung) Belen (Ericsson) is okay to postpone ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.25.2 | S2-2304249 | CR | Approval | 23.501 CR4253 (Rel-18, 'B'): Support URSP provisioning in EPS | Intel | Rel-18 | r04 agreed. Revised to S2-2305475. | Huazhang (vivo) provide comments and way forward to solve the ePCO negotiation. And also Huazhang wants to clarify, that the ePCO negotiation is not specific for the URSP rule provision in EPS, it is a general issue for all of the situation that UE and network wants to communicate something via ePCO in EPS. And, also, the current CT1 already has the solution or mechanism to solve this problem Changhong (Intel) replies to Huazhang and provides r01. Belen (ericsson) support r01 Huazhang (vivo) provides r02 to clarify if no indication is received from network Changhong (Intel) provides r03 to polish the text. Krisztian (Apple) provides r04. ==== Revisions Deadline ==== Huazhang (vivo) agree with r04, thanks ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305475 | CR | Approval | 23.501 CR4253R1 (Rel-18, 'B'): Support URSP provisioning in EPS | Intel, Apple, Ericsson | Rel-18 | Revision of S2-2304249r04. Approved | Agreed | |
| 9.25.2 | S2-2304250 | CR | Approval | 23.502 CR3979 (Rel-18, 'B'): Support URSP provisioning in EPS | Intel | Rel-18 | r01 agreed. Revised to S2-2305476, merging S2-2304412 | Changhong (Intel) provides r01. Zhuoyi (China Telecom) provides r02. Belen (Ericsson) objects to r02, fine with r01 Hong (Qualcomm) comments. Zhuoyi (China Telecom) replies to Belen and Hong. Huazhang (vivo), please see my comments in 2304249, the same comments and way forward. Changhong (Intel) replies to Huazhang. Belen (Ericsson) does not agree to remove the Editor´s Note with no solution. Belen (Ericsson) is okay with r01, but wants to keep the discussion open Huazhang (vivo) provides r03 to align with the 4249, but I see r01 and r02 have already here Zhuoyi (China Telecom) would likes to cosign with r01. Changhong (Intel) is not OK with r03. Huazhang (vivo) provide r04 based on r01 Changhong (Intel) replies to Huazhang and proposes to go with r01. Huazhang (vivo) is ok with Changhong's proposal, thanks ==== Revisions Deadline ==== Huazhang (vivo) agree to live with r01, thanks ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305476 | CR | Approval | 23.502 CR3979R1 (Rel-18, 'B'): Support URSP provisioning in EPS | Intel | Rel-18 | Revision of S2-2304250r01, merging S2-2304412. Approved | Agreed | |
| 9.25.2 | S2-2304409 | CR | Approval | 23.502 CR4004 (Rel-18, 'B'): Resolving EN for Discovery the Same PCF for UE serving the UE in both EPS and 5GS | China Telecom Corporation Ltd. | Rel-18 | CR Cover sheet error! Merged into S2-2305046 (noted) | Zhuoyi (China Telecom) provides r01 with corrected coversheet and editorial updates. Changhong (Intel) proposes to merge this paper into S2-2305046. Zhuoyi (China Telecom) agree to merge this paper into S2-2305046 and continue the solution using Samsung's base. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.25.2 | S2-2304412 | CR | Approval | 23.502 CR4005 (Rel-18, 'B'): Resolving EN where UE connects to standalone PGW now supporting ePCO IE | China Telecom Corporation Ltd. | Rel-18 | CR Cover sheet error! Merged into S2-2305476 | Zhuoyi (China Telecom) provides r01 with corrected coversheet and editorial updates. Changhong (Intel) proposes to merge this paper into S2-2304250. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.25.2 | S2-2304413 | CR | Approval | 23.501 CR4304 (Rel-18, 'B'): Resolving EN for Discovery the Same PCF for UE serving the UE in both EPS and 5GS | China Telecom Corporation Ltd. | Rel-18 | CR Cover sheet error! Merged into S2-2305477 | Zhuoyi (China Telecom) provides r01 with corrected coversheet and editorial updates. Changhong (Intel) proposes to merge this paper into S2-2305043. Zhuoyi (China Telecom) agrees to merge this paper into S2-2305043 and continue the solution using Samsung's base. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.25.2 | S2-2305043 | CR | Approval | 23.501 CR4470 (Rel-18, 'B'): UE Policy Association handling during EPS to 5GS mobility with N26 | Samsung, Intel, Nokia, Nokia Shanghai Bell | Rel-18 | CR Cover sheet error! r04 agreed. Revised to S2-2305477, merging S2-2304413 | DongYeon (Samsung) provides r01. Jinguo(ZTE) comments DongYeon (Samsung) replies to Jinguo. Pallab (Nokia) supports the reply from DongYeon (Samsung) Jinguo(ZTE) thanks DongYeon (Samsung) and ask one more question Belen (Ericsson) provides r02, cannot accept r01, but agree with the proposal. Pallab (Nokia) objects to r02 Changhong (Intel) replies to Jinguo. Changhong (Intel) supports Pallab's argument. Zhuoyi (China Telecom) supports Pallab's and Changhong's argument. Changhong (Intel) provides r03 with a simple resolution for the EN. Zhuoyi (China Telecom) has comment for r03. Changhong (Intel) replies to Zhuoyi's Q. Changhong (Intel) further replies to Zhuoyi's Q. Zhuoyi (China Telecom) replies to Changhong. DongYeon (Samsung) replies, and comments on r02, r03. Huazhang (vivo) provides the comments, that Huazhang thinks that we can agree the principle that only one PCF to serve the UE. If so, that it is preferred that to use the PCF discovered during the 5GS registion procedure, and release the PCF for UE that provision URSP in EPS. DongYeon (Samsung) rethink, and OK with r03. DongYeon (Samsung) is OK with r03. Pallab (Nokia) objects to r03 Changhong (Intel) provides r04. Belen (ericsson) can live with r04 Pallab (Nokia) provides comments on r04. Changhong (Intel) replies to Pallab. Zhuoyi (China Telecom) would like to cosign with r04 ==== Revisions Deadline ==== DongYeon (Samsung) is OK with r04. Huazhang (vivo) can live with r04 ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305477 | CR | Approval | 23.501 CR4470R1 (Rel-18, 'B'): UE Policy Association handling during EPS to 5GS mobility with N26 | Samsung, Intel, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2305043r04, merging S2-2304413. Approved | Agreed | |
| 9.25.2 | S2-2305046 | CR | Approval | 23.502 CR4101 (Rel-18, 'B'): UE Policy Association handling during EPS to 5GS mobility with N26 | Samsung, Intel, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Jinguo(ZTE) provides similar comment as in 5043 Pallab (Nokia) responds to Jinguo(ZTE) Changhong (Intel) proposes to NOTE this paper and use S2-2305043r03 as way forward. Pallab (Nokia) cannot accept S2-2305043r03 as way forward. So proposes to keep this CR Belen (Ericsson) does not think that AM policy is impacted. ==== Revisions Deadline ==== Changhong (Intel) proposes to NOTE it as S2-2305043r04 is accepted. ==== Comments Deadline ==== | Noted |
| 9.25.2 | S2-2305050 | CR | Approval | 23.503 CR1018 (Rel-18, 'B'): Support of UE Policy delivery in EPS | Samsung | Rel-18 | Postponed | Changhong (Intel) comments. DongYeon (Samsung) replies to Changhong, and provides r01. Pallab (Nokia) comments on r01. DongYeon (Samsung) replies to Pallab. Changhong (Intel) replies to DongYeon. Changhong (Intel) proposes to postpone this paper. DongYeon (Samsung) replies to Changhong. Jinguo(ZTE) comments that these new PCRTs are not needed. DongYeon (Samsung) provides r02. Pallab (Nokia) responds to DongYeon (Samsung). Supports Intel's suggestion to POSTPONE Changhong (Intel) thinks the two new PCRTs are not needed after careful check in 23.502 and proposes to NOTE it. Belen (Ericsson) agrees with Intel that is incorrect to add new PCRTs, objects to this CR. Changhong (Intel) replies to Belen. Belen (Ericsson) replies to Intel DongYeon (Samsung) asks if we can postpone this CR. Changhong (Intel) agrees to postpone it. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.25.2 | S2-2305141 | CR | Approval | 23.501 CR4502 (Rel-18, 'F'): Selection PCF based on indication of URSP Provisioning Support in EPS | ZTE | Rel-18 | Noted | DongYeon (Samsung) asks questions to understand. Changhong (Intel) has strong concern on indicating the URSP Provisioning Support in EPS in MM Capability to AMF. The change for EPS should be merged into S2-2304028. DongYeon (Samsung) asks question to understand. Josep (Deutsche Telekom) comments, sees also no clear benefit to adding 'PCF for UE which supporting this feature'. Jinguo(ZTE) replies to DongYeon (Samsung) and Changhong(Intel) Jinguo(ZTE) replies to Josep (Deutsche Telekom) Zhuoyi(China Telecom) asks for clarification. Jinguo(ZTE) replies to Zhuoyi(China Telecom) Josep (Deutsche Telekom) replies to Jinguo (ZTE). Jinsook(DISH) Seems the ME box need to ticked Changhong (Intel) proposes to NOTE this paper in order to save our energy in eMeeting based on the comments received. Jinguo(ZTE) provides r01 Changhong (Intel) cannot accept r01. Belen (Ericsson) provides comments, asks questions. Jinguo(ZTE) replies to Belen (Ericsson) Changhong (Intel) replies to Jinguo and thinks we can have a better design in 6G. ==== Revisions Deadline ==== Changhong (Intel) objects to r00 and r01. ==== Comments Deadline ==== | Noted |
| 9.25.2 | S2-2304680 | CR | Approval | 23.501 CR4375 (Rel-18, 'B'): Handling UE policy association when UE registered over both 3GPP and Non-3GPP access | vivo | Rel-18 | Postponed | Changhong (Intel) comments. DongYeon (Samsung) comments. Hong (Qualcomm) comments. Huazhang (vivo) provides r01 to reflect the concerns Pallab (Nokia) comments on r01. Huazhang (vivo) reply to Pallab that you understand is right, that the question is Should a new UE policy association be established from PCF for PDU session to PCF for UE? Or shall the PCF for UE reject the UE policy association est request from the PCF for PDU session? Changhong (Intel) comments on Option#1 and propose to NOTE this paper. Huazhang (vivo) provides r02, and clarify that this is the same PCF serve two UE policy, not the same as in S2-2305043. In S2-2305043, it is two PCFs serve one UE. Pallab (Nokia) provides r03 based on r02. Huazhang (vivo) is ok for the general wording, it depends on configuration, thanks Pallab that you can got my point for this. ==== Revisions Deadline ==== DongYeon (Samsung) objects to r03,r02,r01,r00 and propose to NOTE. Changhong (Intel) tends to agree with DongYeon. Huazhang (vivo) is ok to postpone, and come back next meeting. Pallab (Nokia) OK to POSTPONE. Belen (Ericsson) OK to POSTPONE. ==== Comments Deadline ==== | Postponed |
| 9.25.2 | - | - | - | Evaluation and Conclusion for KI#4 (Support standardized and operator-specific traffic categories in URSP) | - | - | Docs:=3 | - | |
| 9.25.2 | S2-2304478 | CR | Approval | 23.503 CR0931R1 (Rel-18, 'B'): Support of Standardized Traffic Categories | T-Mobile USA | Rel-18 | Revision of S2-2303004 from S2#155. CR Cover sheet error! Revised to S2-2304559 | Revised | |
| 9.25.2 | S2-2304559 | CR | Approval | 23.503 CR0931R2 (Rel-18, 'B'): Support of Standardized Traffic Categories | T-Mobile USA | Rel-18 | Revision of S2-2304478. Approved. CC#4: Noted | Noted | |
| 9.25.2 | S2-2304679 | CR | Approval | 23.503 CR0987 (Rel-18, 'B'): CR 23.503 Reflect conclusion of Traffic Category in 23.503 | vivo | Rel-18 | Noted | Changhong (Intel) comments. Huazhang (vivo) replies to Changhong (Intel) Haiyang (Huawei) comments. Yang (OPPO) comments Hong (Qualcomm) comments and propose to NOTE. Josep (Deutsche Telekom) comments, also thinks that this is already covered by existing normative text. Huazhang (vivo) provide r01, that in conclusion of TR, that the traffic category can also the combination of other TDs. Josep (Deutsche Telekom) comments. Huazhang (vivo) reply to Josep Changhong (Intel) comments on r01 and propose to NOTE as well. Krisztian (Apple) also proposes to NOTE the CR. DongYeon (Samsung) comments to Huazhang. Huazhang (vivo) provides r02 to move the wording into note and clarify this is out of scope Belen (Ericsson) provides comments, cannot accept r02 or previous versions. Pallab (Nokia) provides comments and proposes to NOTE the CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.25.2 | - | - | - | Evaluation and Conclusion for KI#1 (URSP in VPLMN) | - | - | Docs:=21 | - | |
| 9.25.2 | S2-2304024 | CR | Approval | 23.502 CR3951 (Rel-18, 'B'): KI#1 - List of PSIs provided at the Initial Registration | Ericsson | Rel-18 | Postponed | Dimitris (Lenovo) provides comments. There are related proposals in 4270,4271,4310 and 5313,5314 Changhong (Intel) comments on SNPN part. Pallab (Nokia) comments Josep (Deutsche Telekom) comments on SNPN aspects, also thinkgs it is not in WI scope. Wen (vivo) shares same views with Pallab (Nokia) for the SNPN and the list of tuple ID(s) reporting Yang (OPPO) share the same view with previous speakers that the SNPN rule is a separate issue and not addressed in TR study. Belen (Ericsson) provides r01 removing SNPN related aspects. Belen (Ericsson) replies to Nokia Yang (OPPO) replies to Belen Belen (Ericsson) replies to OPPO Hong (Qualcomm) comments. Changhong (Intel) shares same view with Hong. Yang (OPPO) replies to Ericsson Wen (vivo) shares the same logic from Yang (OPPO) on the PSI usage and also think it has no need for the Tuple ID. Dimitris (Lenovo) comments on the need for the UE to indicate what tuples are stored in the UE Changhong (Intel) replies to Dimitris. Dimitris (Lenovo) replies further Yang (OPPO) comments Belen (Ericsson) proposes to postpone the CR. Changhong (Intel) also proposes to postpone the CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.25.2 | S2-2304025 | CR | Approval | 23.503 CR0945 (Rel-18, 'B'): Ki#1 Removal of Editor s Notes | Ericsson | Rel-18 | r02 agreed. Revised to S2-2305478. | Changhong (Intel) comments on SNPN part. Pallab (Nokia) also shares the concerns from Changhong (Intel) regarding SNPN part and has same comments as mentioned in S2-2304024 Josep (Deutsche Telekom) comments that there is definitely no roaming in SNPNs. Has concerns. Wen (vivo) shares same comments on the SNPN case in eUEPO with others Yang (OPPO) share the same view that SNPN policy is not in the scope LaeYoung (LGE) also shares the same concern about extending this topic to SNPN in this release with previous comment providers. Krisztian (Apple) also shares the concern about including SNPN in the scope for R18. Belen (Ericsson) provide r01, SNPN related aspects are removed. Yang (OPPO) asks question for clarification Changhong (Intel) provides r02. Belen (Ericsson) is okay with r02, replies to OPPO Yang (OPPO) is fine to r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305478 | CR | Approval | 23.503 CR0945R1 (Rel-18, 'B'): Ki#1 Removal of Editor s Notes | Ericsson | Rel-18 | Revision of S2-2304025r02. Approved | Agreed | |
| 9.25.2 | S2-2304210 | LS OUT | Approval | [DRAFT] KI#1 - LS OUT - Provision of URSP to route traffic to wild-carded VPLMN | Oracle, Verizon, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom | Rel-18 | WITHDRAWN | Hong (Qualcomm) comments and proposes to bring this issue directly to CT1 as a CR instead of using LS from SA2. Uri (Oracle) replies to Hong's (Qualcomm) comments. Hong (Qualcomm) replies to Uri. Changhong (Intel) shares same view with Hong. Uri (Oracle) replies to comments from Changhong (Intel) and Hong (Qualcomm) and provide rev01 of the CR (S2-2304209). Changhong (Intel) asks Uri to provide r01 link in the thread of S2-2304209. Belen (Ericsson) can live with r01, prefers initial version. Pallab (Nokia) supports sending an LS OUT to avoid any confusion and questions back during stage 3 discussion Uri (Oracle) responds to Hong (Qualcomm) comments wrt/ sending or not sending an LS to CT1. ==== Revisions Deadline ==== Hong (Qualcomm) objects to send the LS. Uri (Oracle) responds to Hong (Qualcomm), withdrawing the LS. ==== Comments Deadline ==== | Withdrawn |
| 9.25.2 | S2-2304209 | CR | Approval | 23.503 CR0957 (Rel-18, 'B'): KI#1 - Provision of URSP to route traffic to wild-carded VPLMN | Oracle, Verizon UK Ltd, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom | Rel-18 | r03 agreed. Revised to S2-2305479. | Changhong (Intel) copies the link for r01 in this thread. Uri provides r02 of the CR to address a comment from Belen (Ericsson) on a different thread. Hong (Qualcomm) provide r03. Uri (Oracle) replies to Hong (Qualcomm). ==== Revisions Deadline ==== Hong (Qualcomm) replies to Uri. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305479 | CR | Approval | 23.503 CR0957R1 (Rel-18, 'B'): KI#1 - Provision of URSP to route traffic to wild-carded VPLMN | Oracle, Verizon UK Ltd, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, Qualcomm Incorporated | Rel-18 | Revision of S2-2304209r03. Approved | Agreed | |
| 9.25.2 | S2-2304270 | CR | Approval | 23.503 CR0961 (Rel-18, 'B'): Clarification on provisioning tuple (PLMN ID, list of PSIs associated with the PLMN ID) within UE policies | Lenovo | Rel-18 | r05 agreed. Revised to S2-2305480. | Pallab (Nokia) provides comments Changhong (Intel) thinks the proposal contradicts the TR conclusion and Sol#6 Option#1. Dimitris (Lenovo) responds to Nokia Yang (OPPO) comments Mike (InterDigital) comments Dimitris (Lenovo) responds to Oppo Changhong (Intel) replies to Dimitris Hong (Qualcomm) provides r01. Krisztian (Apple) provides r02. Changhong (Intel) provides r03 and cosigns. Dimitris (Lenovo) comments on the tuple semantics Wen (vivo) comments. Ericsson (Belen) is okay r03 Pallab (Nokia) comments Changhong (Intel) replies to Pallab comments Mike (InterDigital) co-signs Dimitris (Lenovo) provides r04 Belen (Ericsson) co-signs Dimitris (Lenovo) provides r05 adding Ericsson as co-signer ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305480 | CR | Approval | 23.503 CR0961R1 (Rel-18, 'C'): Clarification on provisioning tuple (PLMN ID, list of PSIs associated with the PLMN ID) within UE policies | Lenovo, Apple, Intel, Interdigital, Ericsson | Rel-18 | Revision of S2-2304270r05. Approved | Agreed | |
| 9.25.2 | S2-2304271 | CR | Approval | 23.502 CR3985 (Rel-18, 'B'): UE capability for supporting applying PSIs in a specific PLMN | Lenovo | Rel-18 | r02 agreed. Revised to S2-2305481. | Pallab (Nokia) has same comments as in S2-2304270 Changhong (Intel) supports this paper. Krisztian (Apple) provides r01. Wen (vivo) shares the comments in4270 and question for the necessary of the VPLMN specific URSP indication. Belen (Ericsson) is okay with r01 Pallab (Nokia) comments Yang (OPPO) comments Mike (InterDigital) comments Dimitris (Lenovo) provides r02 ==== Revisions Deadline ==== Belen (Ericsson) is okay with r02, would like to co-sign ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305481 | CR | Approval | 23.502 CR3985R1 (Rel-18, 'C'): UE capability for supporting applying PSIs in a specific PLMN | Lenovo, Apple,Ericsson | Rel-18 | Revision of S2-2304271r02. Approved | Agreed | |
| 9.25.2 | S2-2304310 | CR | Approval | 23.503 CR0962 (Rel-18, 'B'): Clarification on provisioning tuple (PLMN ID, list of PSIs associated with the PLMN ID) within UE policies | Lenovo | Rel-18 | Noted | Changhong (Intel) thinks the proposal contradicts the TR conclusion and Sol#6 Option#1. Dimitris (Lenovo) responds to Intel Mike (InterDigital) comments Changhong (Intel) replies to DK and Mike. Hong (Qualcomm) comments and suggest leaving this to CT1. Krisztian (Apple) also proposes to NOTE the CR and leave the tuple encoding for CT1 to define. Belen (Ericsson) disagree with the proposal in this CR, also disagree to leave discussions to CT1 as proposed. Dimitris (Lenovo) comments on the tuple semantics ==== Revisions Deadline ==== Changhong (Intel) replies to DK and proposes to NOTE it. ==== Comments Deadline ==== | Noted |
| 9.25.2 | S2-2305024 | CR | Approval | 23.503 CR1017 (Rel-18, 'F'): Update of Provision of URSP to route traffic to the VPLMN | OPPO | Rel-18 | r05 agreed. Revised to S2-2305482. | Changhong (Intel) provides r01. Yang (OPPO) provides r02 Krisztian (Apple) provides r03. Yang (OPPO) responds to Krisztian and provides r04 Changhong (Intel) confirms that non-VPLMN specific URSP rule was introduced at SA2#155 and supports r04. Dimitris (Lenovo) indicates a clash with 4025 Changhong (Intel) provides r05 by taking out the First Change part. Belen (Ericsson) is okay with r05 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305482 | CR | Approval | 23.503 CR1017R1 (Rel-18, 'F'): Update of Provision of URSP to route traffic to the VPLMN | OPPO | Rel-18 | Revision of S2-2305024r05. Approved | Agreed | |
| 9.25.2 | S2-2305312 | DISCUSSION | Agreement | Backwards Compatibility of VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Noted | Noted | |
| 9.25.2 | S2-2305313 | CR | Approval | 23.503 CR1036 (Rel-18, 'C'): Adding a Support Indication for VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Check Affected Clauses! R04 + changes agreed. Revised to S2-2306237. Agree r04? Change “can” to “may” in the new text. For CC#4 | Pallab (Nokia) provides comments Mike (InterDigital) replies Changhong (Intel) proposes to merge changes except for the last one in this paper into S2-2304270. Hong (Qualcomm) also suggests merging the indicator aspect to S2-2304270. Mike (InterDigital) provides r01 which removes the indicator part and agrees that the indicator part can be merged into S2-2304270 Belen (Ericsson) objects to both initial revision and r01 Pallab (Nokia) also objects to r01 and initial version Mike (InterDigital) replies and provides r02. Pallab (Nokia) comments and maintains objection Mike (InterDigital) asks Pallab what part he is objecting to. Pallab (Nokia) responds to Mike (InterDigital) Yang (OPPO) thinks the ME impact should be 'No' given the first original change has been merged to another paper Mike (InterDigital) replies and provides r03. Also, agrees with Yang that the ME impact is No in all revisions except r00. Belen (Ericsson) provides comments to r02, and asks questions on Mike´s responses. Mike (InterDigital) replies to Belen (Ericsson) and Pallab (Nokia) and provides r04. ==== Revisions Deadline ==== Pallab (Nokia) is OK with r04 with below change: - Change 'can' to 'may' in the new text that is added as it is a normative text Belen (Ericsson) is okay with r04. Mike (InterDigital) proposes to APPROVE r04 + change 'H-PCF can trigger' to 'H-PCF may trigger'. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2306237 | CR | Approval | 23.503 CR1036R1 (Rel-18, 'C'): Adding a Support Indication for VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Revision of S2-2305313r04 + changes. Approved | Agreed | |
| 9.25.2 | S2-2305314 | CR | Approval | 23.502 CR4145 (Rel-18, 'C'): Adding a Support Indication for VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Check Affected Clauses! Postponed | Pallab (Nokia) provides comments Mike (InterDigital) replies Changhong (Intel) thinks the indication is useful. Pallab (Nokia) replies Pallab (Nokia) provides further comments Mike (InterDigital) replies and provides r01. Pallab (Nokia) responds to Mike (InterDigital) ==== Revisions Deadline ==== Pallab (Nokia) proposes to POSTPONE Mike (InterDigital) agrees that POSTPONE is the only way forward for this meeting. ==== Comments Deadline ==== | Postponed |
| 9.25.2 | S2-2305315 | CR | Approval | 23.501 CR4547 (Rel-18, 'F'): Clarifications in the Definition of VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Check Affected Clauses! Should be a 23.503 CR. Allocated to 23.503 CR 1040. r01 agreed. Revised to S2-2305483. | Mike (InterDigital) provides r01 to fix the cover page - this is 23.503 CR 1040 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305483 | CR | Approval | 23.503 CR1040 (Rel-18, 'F'): Clarifications in the Definition of VPLMN Specific URSP Rules | InterDigital Inc. | Rel-18 | Revision of S2-2305315r01 (corrected TS and CR numbers). Approved | Agreed | |
| 9.25.2 | S2-2304526 | CR | Approval | 23.503 CR0978 (Rel-18, 'B'): Update of the provision of URSP to route traffic to the VPLMN | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2305484. | Haiyang (Huawei) provides r01 Belen (Ericsson) asks a question on r01, thinks it is incorrect Haiyang (Huawei) provides clarification to Belen (Ericsson) ==== Revisions Deadline ==== Belen (Ericsson) is okay with r01. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305484 | CR | Approval | 23.503 CR0978R1 (Rel-18, 'B'): Update of the provision of URSP to route traffic to the VPLMN | Huawei, HiSilicon | Rel-18 | Revision of S2-2304526r01. Approved | Agreed | |
| 9.25.2 | - | - | - | Evaluation and Conclusion for KI#2 (5GC awareness of URSP enforcement) | - | - | Docs:=8 | - | |
| 9.25.2 | S2-2304026 | CR | Approval | 23.288 CR0728 (Rel-18, 'B'): KI#2- Removing Editor s Note | Ericsson | Rel-18 | r04 + changes agreed. Revised to S2-2305485. | Dimitris (Lenovo) provides r01 adding an EN Haiyang (Huawei) provides a question. Yang (OPPO) provides comments Kenichi (KDDI) provides a comment. Changhong (Intel) asks Dimitris how to resolve the new EN. Changhong (Intel) asks someone to provide a revision. Kenichi (KDDI) provides r02. Jicheol (Samsung) ask a clarification for Application ID. Huazhang (vivo) provides r03, to clairfy some other TD can also be translated into APP ID Belen (Ericsson) objects to r02, can accept with r01. Kenichi (KDDI) provides comment. Haiyang (Huawei) clarifies the comments. Yang (OPPO) agrees with Haiyang way forward Belen (Ericsson) agrees with Huawei that we need to update 23.503 if this CR is accepted. Jicheol (Samsung) comments. Jicheol (Samsung) ask clarification questions on how NWDAF identifies TD that the traffic does not match TD Belen (Ericsson) replies to Samsung, provide r04 Dimitris (Lenovo) comments on r04 ==== Revisions Deadline ==== Changhong (Intel) replies to DK and asks for answer. Dimitris (Lenovo) suggests to keep the EN provided in r01. Can accept r04 with the additional EN Belen (Ericsson) asks Lenovo, cannot accept adding this EN as such Dimitris (Lenovo) agrees the proposed EN by Ericsson is helpful Belen (Ericsson) provides r02 Kenichi (KDDI) Revision number could be r05. Ask to upload it to revision folder. Dimitris (Lenovo) accept r04+EN ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305485 | CR | Approval | 23.288 CR0728R1 (Rel-18, 'B'): KI#2- Removing Editor s Note | Ericsson | Rel-18 | Revision of S2-2304026r04 + changes. CC#4: Approved | Agreed | |
| 9.25.2 | S2-2304069 | CR | Approval | 23.502 CR3959 (Rel-18, 'B'): Forwarding of UE reporting of URSP rule enforcement between SM-PCF and UE-PCF | Deutsche Telekom | Rel-18 | Check Affected Clauses! r13 + changes agreed. Revised to S2-2305486. | Josep (Deutsche Telekom) provides r01, comments. Haiyang (Huawei) provides r02 and r03, comments. Josep (Deutsche Telekom) comments on r02, provides r04 based on r02. Jicheol (Samsung) ask a justification for introducing a new NF service Jicheol (Samsung) ask a question how the UE-PCF identifies which PDU Session is reported on? Josep (Deutsche Telekom) responds to Jicheol (Samsung), provides r05. Haiyang (Huawei) responds to Jicheol (Samsung) and comments. Josep (Deutsche Telekom) responds to Haiyang (Huawei). Jicheol (Samsung) comments. Josep (Deutsche Telekom) comments, provides r06. Haiyang (Huawei) comments to Jicheol (Samsung). Belen (Ericsson) objects to r05, provides comments. Belen (Ericsson) also asks about r03 Haiyang (Huawei) responds to Belen (Ericsson) Josep (Deutsche Telekom) tries to address Belén's (Ericsson) objection with r07. Haiyang (Huawei) responds to Josep (Deutsche Telekom). Haiyang (Huawei) comments on r07. Josep (Deutsche Telekom) comments. Huazhang (vivo) provide comments Josep (Deutsche Telekom) answers Huazhang (vivo). Haiyang (Huawei) comments to Josep (Deutsche Telekom) and Belen (Ericsson) Haiyang (Huawei) agrees with Huazhang (vivo) Josep (Deutsche Telekom) comments, provides r08. Iskren (NEC) comments. Haiyang (Huawei) provides r09 based on Josep (Deutsche Telekom)'s suggestion. Pallab (Nokia) provides comments and raises concerns with modifying BSF APIs Jicheol (Samsung) objects r09. Josep (Deutsche Telekom) comments on r09. Haiyang (Huawei) clarifies to Jicheol (Samsung) and Josep (Deutsche Telekom). Haiyang (Huawei) responds to Pallab (Nokia). Pallab (Nokia) responds to Haiyang (Huawei) Haiyang (Huawei) further responds to Pallab (Nokia). Haiyang (Huawei) provides r10. Belen (Ericsson) objects to r10, provides r11 Josep (Deutsche Telekom) comments, asks Belén a question for clarification regarding r11, provides 12 just in case. Haiyang (Huawei) comments to Pallab (Nokia). Haiyang (Huawei) seeks clarification from Belen (Ericsson), suggests to go with r03. Josep (Deutsche Telekom) comments to Haiyang (Huawei). Josep (Deutsche Telekom) replies to Haiyang (Huawei). Josep (Deutsche Telekom) provides r13 with +EN. ==== Revisions Deadline ==== Haiyang (Huawei) provides r14 (which is r13+removing ' and PDU session information'). Can only accept r02, r03, r09, r10 and r14. Prefer r03. Josep (Deutsche Telekom) proposes to go with r13. Offers summary Josep (Deutsche Telekom) answer to Haiyang, provides r15 in drafts folder with additional EN. Haiyang (Huawei) can also accept r15 (which is r13+removing ' and PDU session information'+ ' Editor's note: whether 'and PDU session information' should be mentioned in step 9 as part of Npcf_PolicyAuthorization_Notify is FFS '). Belen (Ericsson) is okay with r13 (and r14, r15) Pallab (Nokia) OK with r13. Also OK with r14, r15 in the drafts folder. Objects to r00-r10 Jicheol (Samsung) also supports r13 and objects r14. can live with r15. Haiyang (Huawei) suggests to change the EN in r15 ' Editor's note: whether 'and PDU session information' should be mentioned in step 9 as part of Npcf_PolicyAuthorization_Notify is FFS '). Into ' Editor's note: whether PDU Session ID should be mentioned in step 9 as part of Npcf_PolicyAuthorization_Notify is FFS ' Josep (Deutsche Telekom) proposes to mark the topic '+EN people can live with' for CC#3. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305486 | CR | Approval | 23.502 CR3959R1 (Rel-18, 'B'): Forwarding of UE reporting of URSP rule enforcement between SM-PCF and UE-PCF | Deutsche Telekom, Samsung, NEC, OPPO | Rel-18 | Revision of S2-2304069r13 + changes. Approved | Agreed | |
| 9.25.2 | S2-2304070 | CR | Approval | 23.503 CR0947 (Rel-18, 'B'): Forwarding of UE reporting of URSP rule enforcement between SM-PCF and UE-PCF | Deutsche Telekom | Rel-18 | CC#4: r17 + changes agreed. Revised to S2-2306253. For CC#4 | Josep (Deutsche Telekom) provides r01, comments, add Interdigital as co-signer. Josep (Deutsche Telekom) corrects his last comment. Josep (Deutsche Telekom) provides r02 based on comments from S2-2304069. Jicheol (Samsung) provides r03 Belen (Ericsson) provides comments to r03. Josep (Deutsche Telekom) comments, provides r04 addressing prior comments from belén (Ericsson). Haiyang (Huawei) provides r06 (r05 is skipped), replies to Belen (Ericsson). Ellen (Google) provides r07 to rephrase the note 1 to align with conclusion Ellen (Google) provides r08 to merge 5291 to align with conclusion Krisztian (Apple) supports r08 and provides r09 on top of r08 to clarify the wording and fix the examples. Jicheol comments on the support of the URSP enforcement in EPC Josep (Deutsche Telekom) provides r10 with clean-up on top of r09. Josep (Deutsche Telekom) provides r1 based on the discussion in S2-2304069. Yang (OPPO) has concern on indicating which URSP for enforcement reporting, thus concern r08-r11. Provides r12 with removing this part. Pallab (Nokia) comments and asks clarification on PCF subscribing to UPF. Pallab (Nokia) provides further comments on PCF subscribing to UPF. The CR needs revision Pallab (Nokia) provides r13, r14 Josep (Deutsche Telekom) provides a clearer version based on r14, provides r15. Belen (Ericson) objects to r14, and r15 provides r16 Yang (OPPO) provides r17 based on r16, cleaning change over change in NOTE 1 in 6.6.2.4. ==== Revisions Deadline ==== Josep (Deutsche Telekom) proposes to go forward with r17. Haiyang (Huawei) proposes to go forward with r17 + restoring the EN 'Editor's note: the description on PCC rule generation based on pre-configured URSP rules is FFS.'. Objects to r08~r11, r16, r17. Huazhang (vivo) supports Haiyang's comments, that the PCC rule generation should be discussed, because if not, how to UPF detect the traffic of Connection Capability is FFS. But it is ok to discuss next meeting. Josep (Deutsche Telekom) is OK with Haiyang's (Huawei) proposal. Puts r18 in drafts folder. Changhong (Intel) comments on the restored EN and proposes a resolution for it. Haiyang (Huawei) comments to Changhong (Intel). Pallab (Nokia) is OK to approve r17. Objects to r00-r13 Belen (Ericsson) is okay with r17 (and r18). Jicheol also prefer r17, okay with r18. Ellen (Google) can only accept r010 or r11, and object to any other versions that are without or remove indication for reporting URSP rule enforcement. Josep (Deutsche Telekom) asks Ellen to re-consider her objection. It goes against agreed TR conclusions. Changhong (Intel) asks Yang to reconsider his objection as you are objecting the TR conclusion. Yang (OPPO) also suggest Ellen (Google) to reconsider the objection because the proposal from Google (S2-2305291) is unhandled one. And r17/18 does not clash to it at all. Yang (OPPO) answered and sustain the objection to the new indication because it is merged from an unhandled contribution, which is lack of full discussion Changhong (Intel) answers to Yang and asks Ellen to reconsider her objection. Josep (Deutsche Telekom) answer to ChangHong (Intel) that the text in tS 23.503 is was (at the time) clear. Does not see an error in the TR's implementation. Proposes to discuss this aspect in the next meeting as agreement is not possible. Let's focus on agreeing on the support of SM-PCF/UE-PCF architecture. Haiyang (Huawei) answers to Belen (Ericsson) Haiyang (Huawei) comments that the TR conclusion clearly means the CC will implicitly indicate the UE to do the report. Changhong (Intel) proposes to postpone the paper. Josep (Deutsche Telekom) summarizes that the majority's proposal is to go with r17 + reinstate EN ' Editor's note: the description on PCC rule generation based on pre-configured URSP rules is FFS' -> r18 in drafts folder. Asks Ellen (Google) to reconsider objection. Josep (Deutsche Telekom) clarifies to Changhong that his stated reason is not an impediment. Proposes this CR for CC#4 Yang (OPPO) support put it into CC#4 Huazhang (vivo) ask a question further, if so, does it means that all of the connection capability that UE enforced should be reported to network? But maybe only some of the connection capability is interested by the network, and UE still consumes power to report the uninterested result... Changhong (Intel) comments and OK to mark it for CC#4. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2306253 | CR | Approval | 23.503 CR0947R1 (Rel-18, 'B'): Forwarding of UE reporting of URSP rule enforcement between SM-PCF and UE-PCF | Deutsche Telekom, InterDigital Inc., Samsung, Huawei, NEC, OPPO | Rel-18 | Revision of S2-2304070r17 + changes. CC#4: Approved | Agreed | |
| 9.25.2 | S2-2304251 | CR | Approval | 23.502 CR3980 (Rel-18, 'B'): Clarification on URSP rule enforcement | Intel, vivo, Deutsche Telekom | Rel-18 | r01 agreed. Revised to S2-2305487. | Ellen (Google) comments Josep (Deutsche Telekom) asks if the comment was meant for this CR. Ellen (Google) replies to Josep (DT) question and provides r01 Josep (Deutsche Telekom) apologizes for the confusion, answers to Ellen (Google). Changhong (Intel) provides r02 based on Ellen's comments . Ellen (Google) provides r03 based on Josep (DT) comment and Changhong (Intel) r02. Josep (Deutsche Telekom) comments. Belen (Ericsson) asks about r03. Ellen (Google) replies Belen (Ericsson) and Josep (DT) Krisztian (Apple) supports r03 as a way forward. Yang (OPPO) has concern on the finer granularity reporting than Connection Capability Josep (Deutsche Telekom) comments on the granularity. Changhong (Intel) provides r04. Josep (Deutsche Telekom) comments, r04 seems OK. Yang (OPPO) is fine to r04. Changhong (Intel) provides r05 to update the coversheet based on r04. Ellen (Google) upload 'r6' with small fix adding 's'. Ellen (Google) upload r5 with small fix adding 's'. ==== Revisions Deadline ==== Belen (Ericsson) can accept r06 if the cover page is updated and if the text that says that UE Policy information including an indication for reporting URSP Rule enforcement is removed. Ellen (Google) can only accept r01 (cat D with editorial changes only) or r03 (the best) or r06, and object to any other versions. Josep (Deutsche Telekom) can go with r00, r01. Objects to r02, r03, r06. Yang (OPPO) can only agree r01 Changhong (Intel) asks Yang to reconsider his objection as you are objecting the TR conclusion. Ellen (Google) proposes to accept r01 to avoid overlapping changes on UE policy information which is already referred to TS23.503 in the text. r00 is not acceptable, which is anyhow against the TR conclusion. Changhong (Intel) proposes to approve r01 and postpone the controversial part. Yang (OPPO) comments there are three options. Fine to go with r01 ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2305487 | CR | Approval | 23.502 CR3980R1 (Rel-18, 'D'): Clarification on URSP rule enforcement | Intel, vivo, Deutsche Telekom | Rel-18 | Revision of S2-2304251r01. Approved | Agreed | |
| 9.25.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=15 | - | |
| 9.25.2 | S2-2304252 | CR | Approval | 23.503 CR0959 (Rel-18, 'B'): Clarification on URSP rule enforcement | Intel, vivo, Deutsche Telekom | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304312 | CR | Approval | 23.288 CR0750 (Rel-18, 'B'): Removing EN on URSP enforcement analytics | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304315 | CR | Approval | 23.503 CR0963 (Rel-18, 'B'): Additional procedure for URSP awareness without UE assistance | Lenovo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304372 | CR | Approval | 23.288 CR0752 (Rel-18, 'B'): Update URSP enforcement analytics | KDDI, Lenovo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304527 | CR | Approval | 23.502 CR4027 (Rel-18, 'B'): Remove the ENs for URSP awareness | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304528 | CR | Approval | 23.503 CR0979 (Rel-18, 'B'): Remove the ENs for URSP awareness | Huawei, HiSilicon | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304681 | CR | Approval | 23.502 CR4051 (Rel-18, 'B'): Principle of PCC rule generation based on URSP rule and URSP rule enforcement delivery procedure. | vivo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304682 | CR | Approval | 23.503 CR0988 (Rel-18, 'B'): Not reporting URSP rule enforcement other then connection capability | vivo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304683 | CR | Approval | 23.503 CR0989 (Rel-18, 'B'): Principle of PCC rule generation based on URSP rule and URSP rule enforcement delivery procedure. | vivo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2304820 | CR | Approval | 23.503 CR0999 (Rel-18, 'B'): PCF functionalities update | vivo | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2305007 | CR | Approval | 23.503 CR1015 (Rel-18, 'B'): UE reporting of URSP rule enforcement to the UE-PCF | Samsung | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2305020 | CR | Approval | 23.288 CR0810 (Rel-18, 'F'): Update of NWDAF analytics of URSP enforcement | OPPO | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2305207 | CR | Approval | 23.503 CR1027 (Rel-18, 'F'): UE reporting restrictions | Apple | Rel-18 | NOT HANDLED | ||
| 9.25.2 | S2-2305291 | CR | Approval | 23.503 CR1033 (Rel-18, 'B'): Clarification on UE reporting enforcement of URSP rule | Rel-18 | NOT HANDLED | |||
| 9.25.2 | S2-2305316 | CR | Approval | 23.501 CR4548 (Rel-18, 'F'): Considering the Allowed NSSAI with URSP Enforcement Information | InterDigital Inc. | Rel-18 | Check Affected Clauses! | NOT HANDLED | |
| 9.26.1 | - | - | - | Study on System Enabler for Service Function Chaining (FS_SFC) | - | - | Docs:=0 | - | |
| 9.26.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | Docs:=8 | - | |
| 9.26.2 | S2-2304101 | CR | Approval | 23.503 CR0949 (Rel-18, 'C'): Policy subscription data for service function chaining | Ericsson | Rel-18 | r01 agreed. Revised to S2-2306233. | Mirko (Huawei) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.26.2 | S2-2306233 | CR | Approval | 23.503 CR0949R1 (Rel-18, 'C'): Policy subscription data for service function chaining | Ericsson | Rel-18 | Revision of S2-2304101r01. Approved | Agreed | |
| 9.26.2 | S2-2304548 | CR | Approval | 23.501 CR4341 (Rel-18, 'C'): Update to Application Function influence on Service Function Chaining | Intel | Rel-18 | Merged into S2-2306234 | Megha(Intel) comments this document can be marked as merged with S2-2304846. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.26.2 | S2-2304846 | CR | Approval | 23.501 CR4415 (Rel-18, 'F'): Corrections and alignments of SFC terminology | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306234, merging S2-2304548 | Dongjoo (Nokia) provides comments. Stefan (Ericsson) comments and provides r01 Mirko (Huawei) responds and provides r02. Dongjoo (Nokia) provides feedback to Mirko (Huawei). Mirko (Huawei) responds. Dongjoo (Nokia) can live with the change based on the clarification from Mirko (Huawei) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.26.2 | S2-2306234 | CR | Approval | 23.501 CR4415R1 (Rel-18, 'F'): Corrections and alignments of SFC terminology | Huawei, HiSilicon, Deutsche Telekom | Rel-18 | Revision of S2-2304846r02, merging S2-2304548. Approved | Agreed | |
| 9.26.2 | S2-2304847 | CR | Approval | 23.502 CR4078 (Rel-18, 'F'): Corrections and alignments of SFC terminology | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2306235. | Stefan (Ericsson) comments and provides r01 Mirko (Huawei) responds. Stefan (Ericsson) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.26.2 | S2-2306235 | CR | Approval | 23.502 CR4078R1 (Rel-18, 'F'): Corrections and alignments of SFC terminology | Huawei, HiSilicon, Deutsche Telekom | Rel-18 | Revision of S2-2304847r02. Approved | Agreed | |
| 9.26.2 | S2-2304848 | CR | Approval | 23.503 CR1007 (Rel-18, 'F'): Corrections and alignments of SFC terminology | Huawei, HiSilicon | Rel-18 | Approved | Stefan (Ericsson) provides r01 Mirko (Huawei) responds. Stefan (Ericsson) ok with r00 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.27.1 | - | - | - | Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) | - | - | Docs:=0 | - | |
| 9.27.2 | - | - | - | Extensions to the TSC Framework to support DetNet (DetNet) | - | - | Docs:=12 | - | |
| 9.27.2 | S2-2304127 | CR | Approval | 23.503 CR0952 (Rel-18, 'F'): Updates to 5GS DetNet integration | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305488. | Saubhagya (Nokia) provides r01 Haiyang (Huawei) provides questions György (Ericsson) provides r02 György (Ericsson) responds to Huawei. Saubhagya (Nokia) supports r02, request to co-source Haiyang (Huawei) provides comments Haiyang (Huawei) comments György (Ericsson) comments Haiyang (Huawei) further comments György (Ericsson) provides r03 Haiyang (Huawei) is OK with r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.27.2 | S2-2305488 | CR | Approval | 23.503 CR0952R1 (Rel-18, 'F'): Updates to 5GS DetNet integration | Ericsson, Nokia | Rel-18 | Revision of S2-2304127r03. Approved | Agreed | |
| 9.27.2 | S2-2304224 | DISCUSSION | Discussion | Discussion on IETF DetNet Topology YANG for 5GS DetNet Provisioning | China Mobile | Rel-18 | Noted | Noted | |
| 9.27.2 | S2-2304225 | CR | Approval | 23.503 CR0958 (Rel-18, 'F'): IETF DetNet Topology YANG for 5GS DetNet Provisioning | China Mobile | Rel-18 | Noted | György (Ericsson) comments Tianji <CMCC> reply comments Tianji <CMCC> created the revision r01 György (Ericsson) responds to CMCC. Tianji <CMCC> replies to comments (Ericsson) Saubhagya (Nokia) shares concerns Tianji <CMCC> replies to comments (Nokia) ==== Revisions Deadline ==== Tianji <CMCC> replies to comments (Ericsson), and propose to Note the paper. ==== Comments Deadline ==== | Noted |
| 9.27.2 | S2-2304354 | CR | Approval | 23.501 CR4280 (Rel-18, 'F'): Architectural diagram change for DetNet | Nokia, Nokia Shanghai Bell | Rel-18 | r02 agreed. Revised to S2-2305489. | György (Ericsson) comments Saubhagya (Nokia) provides r01 György (Ericsson) provides r02 to include some of the changes already agreed in S2-2303886 at S2#155 but not fully implemented in 23.501 version 18.1.0 (this has been confirmed with Maurice). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.27.2 | S2-2305489 | CR | Approval | 23.501 CR4280R1 (Rel-18, 'F'): Architectural diagram change for DetNet | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2304354r02. Approved | Agreed | |
| 9.27.2 | S2-2304355 | CR | Approval | 23.503 CR0966 (Rel-18, 'F'): Text alignment for 3gpp extension for DetNet YANG | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2305490. | György (Ericsson) comments Saubhagya (Nokia) provide comments György (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.27.2 | S2-2305490 | CR | Approval | 23.503 CR0966R1 (Rel-18, 'F'): Text alignment for 3gpp extension for DetNet YANG | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304355r01. Approved | Agreed | |
| 9.27.2 | S2-2304356 | CR | Approval | 23.501 CR4281 (Rel-18, 'B'): UPF discovery and Selection for DetNet | Nokia, Nokia Shanghai Bell | Rel-18 | r01 + changes agreed. Revised to S2-2305491. | Haiyang (Huawei) comments Saubhagya (Nokia) responds to Haiyang (Huawei) Haiyang (Huawei) further comments Saubhagya (Nokia) provide comments György (Ericsson) comments. Zhendong (ZTE) share similar view with György. György (Ericsson) provides r01. ==== Revisions Deadline ==== Haiyang (Huawei) suggests to note this paper. Haiyang (Huawei) comments. György (Ericsson) proposes to go with r01 which should be in line with Huawei expectations. Haiyang (Huawei) further comments. Saubhagya (Nokia) provides a draft revision for CC#3, where DetNet capability is removed György (Ericsson) agrees with the way forward proposed by Nokia Haiyang (Huawei) is OK with the draft. Qianghua (Huawei) notes should be recorded as r01+removal of the DetNet capability ==== Comments Deadline ==== | Revised |
| 9.27.2 | S2-2305491 | CR | Approval | 23.501 CR4281R1 (Rel-18, 'B'): UPF discovery and Selection for DetNet | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2304356r01 + changes. Approved | Agreed | |
| 9.27.2 | S2-2304357 | CR | Approval | 23.501 CR4282 (Rel-18, 'B'): TSCTSF discovery for DetNet | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Haiyang (Huawei) comments György (Ericsson) proposes to note this document Saubhagya (Nokia) given the comments and disagreements, proposes to withdraw the paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Withdrawn |
| 9.27.2 | S2-2304358 | CR | Approval | 23.501 CR4283 (Rel-18, 'B'): Different port encoding for DetNet | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | György (Ericsson) comments György (Ericsson) proposes to note the document ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.28.1 | - | - | - | Study on Seamless UE context recovery (FS_SUECR) | - | - | Docs:=0 | - | |
| 9.28.2 | - | - | - | Seamless UE context recovery (SUECR) | - | - | Docs:=0 | - | |
| 9.29 | - | - | - | MBS support for V2X services (TEI18_MBS4V2X) | - | - | Docs:=0 | - | |
| 9.30 | - | - | - | Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) | - | - | Docs:=0 | - | |
| 9.31 | - | - | - | Enhancement of application detection event exposure (TEI18_ADEE) | - | - | Docs:=0 | - | |
| 9.32 | - | - | - | General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) | - | - | Docs:=0 | - | |
| 9.33 | - | - | - | New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18_DCAMP_Ph2) | - | - | Docs:=8 | - | |
| 9.33 | S2-2304016 | DISCUSSION | Agreement | Dynamically Changing AM Policy for LBO roaming | Ericsson | Rel-18 | Noted | Noted | |
| 9.33 | S2-2304017 | CR | Approval | 23.501 CR4189 (Rel-18, 'B'): Dynamically changing AM policies for inbound roamers using LBO | Ericsson | Rel-18 | Approved | Agreed | |
| 9.33 | S2-2304018 | CR | Approval | 23.503 CR0942 (Rel-18, 'B'): Dynamically changing AM policies for inbound roamers using LBO | Ericsson | Rel-18 | Merged into S2-2305493 | Yubing (China Telecom) propose to merge S2-2304018 into S2-2304838, so that we can discuss 23.503 update in a single stream. Judy (Ericsson) agrees to Yubing (China Telecom)'s merging proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.33 | S2-2304019 | CR | Approval | 23.502 CR3948 (Rel-18, 'B'): Dynamically changing AM policies for inbound roamers using LBO | Ericsson | Rel-18 | r03 agreed. Revised to S2-2305492, merging S2-2304832 | Yubing (China Telecom) propose to use S2-2304019 as baseline and merge S2-2304832 into this CR, so that we can discuss 23.502 update in a single stream. Judy (Ericsson) agree to Yubing (China Telecom)'s proposal and provide r01 Pallab (Nokia) comments and provides r02 Judy (Ericsson) is fine with r02 Yubing (China Telecom) comments and provides r03 ==== Revisions Deadline ==== Judy (Ericsson) is fine with r03 Pallab (Nokia) is fine with r03 ==== Comments Deadline ==== | Revised |
| 9.33 | S2-2305492 | CR | Approval | 23.502 CR3948R1 (Rel-18, 'B'): Dymically changing AM policies for inbound roamers using LBO | Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, Oracle | Rel-18 | Revision of S2-2304019r03, merging S2-2304832. Approved | Agreed | |
| 9.33 | S2-2304832 | CR | Approval | 23.502 CR4075 (Rel-18, 'B'): 23.502 Supporting DCAMP in LBO roaming scenario | China Telecom | Rel-18 | Merged into S2-2305492 | Yubing (China Telecom) propose to merge S2-2304832 into S2-2304019, so that we can discuss 23.502 update in a single stream. Judy (Ericsson) supports Yubing (China Telecom)'s merging proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 9.33 | S2-2304838 | CR | Approval | 23.503 CR1003 (Rel-18, 'B'): 23.503 Supporting DCAMP in LBO roaming scenario | China Telecom | Rel-18 | r06 agreed. Revised to S2-2305493, merging S2-2304018 | Yubing (China Telecom) propose to use S2-2304838 as baseline and merge S2-2304018 into this CR, so that we can discuss 23.503 update in a single stream. Judy (Ericsson) provides r01 Pallab (Nokia) comments and provides r02 Judy (Ericsson) comments Yubing (China Telecom) replies and provides r03 Judy (Ericsson) comments on r03 Pallab (Nokia) responds to Judy (Ericsson), Yubing (China Telecom) Yubing (China Telecom) responds to Pallab (Nokia) and Judy (Ericsson), and provides r04 Judy (Ericsson) provides r05 Yubing (China Telecom) comments and provides r06 Judy (Ericsson) is fine with r06 ==== Revisions Deadline ==== Judy (Ericsson) can accept only r06 (and objects to other revisions), just for the sake of clarity Pallab (Nokia) is fine to go with r06 ==== Comments Deadline ==== | Revised |
| 9.33 | S2-2305493 | CR | Approval | 23.503 CR1003R1 (Rel-18, 'B'): 23.503 Supporting DCAMP in LBO roaming scenario | China Telecom, Nokia, Nokia Shanghai Bell, Oracle, Ericsson | Rel-18 | Revision of S2-2304838r06, merging S2-2304018. Approved | Agreed | |
| 9.34 | - | - | - | Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | - | - | Docs:=4 | - | |
| 9.34 | S2-2305139 | CR | Approval | 23.501 CR4500 (Rel-18, 'B'): Introduction of the Support of Counting of UEs with at least one PDU sessions in the 5GS option 1 | ZTE | Rel-18 | r05 + changes agreed. Revised to S2-2305494, merging S2-2305237. | George Foti (Ericsson) objects to the CR. It has SMF impacts which is not needed. Jinguo(ZTE) provides r01 based on offline discussion. George (Ericsson) provides comments Fenqin (Huawei) provides comments . Alessio(Nokia) can also live with r01 Iskren (NEC) comments on r01 Ashok (Samsung) responds to Iskren George (Ericsson) I agree. This cluttered the CR even more. George (Ericsson) provides response Fenqin (Huawei) support the view from Ashok Jinguo(ZTE) explains why the description on 3 architectures for the new attribute is needed. provides r02 Iskren (NEC) express concerns with r02 Jinguo(ZTE) replies to Iskren Iskren (NEC) asks Jinguo(ZTE) question, Ashok (Samsung) explains to Iskren (NEC) Jinguo(ZTE) provides r03 Iskren (NEC) comments on r03 by Jinguo(ZTE) Iskren (NEC) replies to Ashok (Samsung) Iskren (NEC) provides r04 Jinguo(ZTE) provides r05 Ashok (Samsung) comments that 5237 can be marked as merged to this 5139 ==== Revisions Deadline ==== George Foti (Ericsson) proposes to postpone the CR. We are not agreeing with what is being proposed. See additional comments Jinguo(ZTE) suggests to approve or technique endorse 5139r05 at this meeting. We can further work on it as basis and the related 502 CR at next meeting Alessio(Nokia) proposes a way forward to agree the CR: remove the hierarchical/ non hierarchical considerations and change the cyan ext this way: From ' i.e. the number of UEs with at least one PDU Session/PDN connection is not counted again in 5GC' to ' i.e. the number of UEs with at least one PDU Session/PDN connection is not updated upon mobility between EPS and 5GS' Fenqin (Huawei) support r05. Jinguo(ZTE) agrees the proposal from Alessio, i.e. 1) remove the hierarchical/ non hierarchical considerations 2)change the cyan ext this way: From ' i.e. the number of UEs with at least one PDU Session/PDN connection is not counted again in 5GC' to ' i.e. the number of UEs with at least one PDU Session/PDN connection is not updated upon mobility between EPS and 5GS' Iskren (NEC) supports the proposed updates by Alessio and Jinguo to r05. Ashok (Samsung) comments that to address George's point to make text under Hierarchical and central NSAC architecture simple the proposal from Jinguo is very good. One liner and simple. Then Alessio proposed text on the paragraph also make it very clear. So now we can agree to r05+ these changes and mark for CC#3 Fenqin (Huawei) agree with Ashok's view. Jinguo(ZTE) suggest to approve 5139r05 with the following changes: 1) replace 5.15.11.1a.2 and 5.15.11.1a.3 with following: 5.15.11.1a.2 Hierarchical NSAC architecture Same mechanisms in clause 5.15.11.2.2 are used with the following differences: - The number of PDU Session is replaced with number of UEs with at least one PDU session/PDN connection. 5.15.11.1a.3 Centralized NSAC architecture Same mechanisms in clause 5.15.11.2.3 are used 2)change the cyan text in clause 5.15.11.5: From ' i.e. the number of UEs with at least one PDU Session/PDN connection is not counted again in 5GC' to ' i.e. the number of UEs with at least one PDU Session/PDN connection is not updated upon mobility between EPS and 5GS' Iskren (NEC) supports the proposed updates to r05 by Jinguo ==== Comments Deadline ==== | Revised |
| 9.34 | S2-2305494 | CR | Approval | 23.501 CR4500R1 (Rel-18, 'B'): Introduction of the Support of Counting of UEs with at least one PDU sessions in the 5GS option 1 | ZTE, NEC | Rel-18 | Revision of S2-2305139r05 + changes, merging S2-2305237. CC#4: Further changes made. Approved | Agreed | |
| 9.34 | S2-2305140 | CR | Approval | 23.501 CR4501 (Rel-18, 'B'): Introduction of the Support of Counting of UEs with at least one PDU sessions in the 5GS option 2 | ZTE | Rel-18 | Noted | George Foti (Ericsson) provides r01 Ashok (Samsung) objects to the CR. It has huge impacts on NSACF and overall on the system Jinguo(ZTE) replies to Ashok(Samsung) Ashok (Samsung) responds to Jinguo Alessio(Nokia) comments that maybe the way forward is to accommodate both behaviours, wo merge 139 and 140 and let the market decide Jinguo(ZTE) replies to Ashok (Samsung) Ashok (Samsung) provides further reply to Jinguo George (Ericsson) provides comments Alessio(Nokia) can live with r01 Ashok (Samsung) object to this CR and suggest to focus on 0139 paper for option 1 solution ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.34 | S2-2305237 | CR | Approval | 23.501 CR4533 (Rel-18, 'B'): UE counting with at least one PDU session and one PDN connection | Samsung, Xiaomi | Rel-18 | Merged into S2-2305494 | George Foti (Ericsson) objects to the CR. It has SMF impacts which is not needed. Myungjune (LGE) asks question. Ashok (Samsung) responds Jinguo(ZTE) replies to Ashok (Samsung) Ashok (Samsung) provides comments to Jinguo George (Ericsson) provides comments Ashok (Samsung) provides response Prabhu (NEC) provides comments. Alessio(Nokia) comments that irrespective of option chosen the event of new PDU session creation will trigger NSACF interaction for counting number of UEs with at least one PDU session with exception of the case of a SMF that already has same UE for another session DNN in which case an optimization can be made (but this may be a corner case). Even for option 1 the UE counting interaction needs to be invoked at every session establishment for a new UE at the SMF. Overall option 2 optimizes the behaviour for the case where a rejection happens for any of the two causes (hence our preference) but we can live with both options being allowed. Ashok (Samsung) comments that it can be marked as merged to 5137 Ashok (Samsung) comments that it can be marked as merged to 5139 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 10 | - | - | - | Project Planning and Management | - | - | Docs:=0 | - | |
| 10.1 | - | - | - | Revised Rel-18 Study Items | - | - | Docs:=0 | - | |
| 10.2 | - | - | - | TS/TR Cover sheets | - | - | Docs:=0 | - | |
| 10.3 | - | - | - | New and revised Rel-18 Work Items | - | - | Docs:=2 | - | |
| 10.3 | S2-2304854 | WID REVISED | Approval | Revised WID: Dynamically Changing AM Policies in the 5GC Phase 2 | China Telecom | Rel-18 | Revision of SP-230102. r01 agreed. Revised to S2-2306236. | Yubing (China Telecom) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 10.3 | S2-2306236 | WID REVISED | Approval | Revised WID: Dynamically Changing AM Policies in the 5GC Phase 2. | China Telecom | Rel-18 | Revision of S2-2304854r01. Approved | Approved | |
| 10.4 | - | - | - | Rel-18 SID/WID Status Reports | - | - | Docs:=27 | - | |
| 10.4 | S2-2305397 | WI STATUS REPORT | Information | WI Status report for 5G System with Satellite Backhaul (5GSATB) | 5GSATB Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305398 | WI STATUS REPORT | Information | WI Status report for Satellite access Phase 2 (5GSAT_Ph2) | 5GSAT_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305399 | WI STATUS REPORT | Information | WI Status report for Personal IoT Networks (PIN) | PIN Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305401 | WI STATUS REPORT | Information | WI Status report for Ranging based services and sidelink positioning (Ranging_SL) | Ranging_SL Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305402 | WI STATUS REPORT | Information | WI Status report for 5GC LoCation Services Phase 3 (5G_eLCS_Ph3) | 5G_eLCS_Ph3 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305403 | WI STATUS REPORT | Information | WI Status report for Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | 5G_ProSe_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305404 | WI STATUS REPORT | Information | WI Status report for Generic group management, exposure and communication enhancements (GMEC) | GMEC Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305405 | WI STATUS REPORT | Information | WI Status report for System Support for AI/ML-based Services (AIMLsys) | AIMLsys Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305406 | WI STATUS REPORT | Information | WI Status report for 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | 5MBS_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305407 | WI STATUS REPORT | Information | WI Status report for Network Slicing Phase 3 (eNS_Ph3) | eNS_Ph3 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305408 | WI STATUS REPORT | Information | WI Status report for XR (Extended Reality) and media services (XRM) | XRM Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305409 | WI STATUS REPORT | Information | WI Status report for RedCap Phase 2 (NR_RedCAP_Ph2) | NR_RedCAP_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305410 | WI STATUS REPORT | Information | WI Status report for Evolution of IMS multimedia telephony service (NG_RTC) | NG_RTC Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305411 | WI STATUS REPORT | Information | WI Status report for Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | ATSSS_Ph3 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305412 | WI STATUS REPORT | Information | WI Status report for UPF enhancement for Exposure And SBA (UPEAS) | UPEAS Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305413 | WI STATUS REPORT | Information | WI Status report for Edge Computing Phase 2 (EDGE_Ph2) | EDGE_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305414 | WI STATUS REPORT | Information | WI Status report for 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | TRS_URLLC Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305415 | WI STATUS REPORT | Information | WI Status report for Vehicle Mounted Relays (VMR) | VMR Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305416 | WI STATUS REPORT | Information | WI Status report for Support for 5WWC Phase 3 (5WWC_Ph2) | 5WWC_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305417 | WI STATUS REPORT | Information | WI Status report for Stage 2 of MPS_WLAN (MPS_WLAN) | MPS_WLAN Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305418 | WI STATUS REPORT | Information | WI Status report for Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | eNA_Ph3 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305419 | WI STATUS REPORT | Information | WI Status report for Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | eNPN_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305420 | WI STATUS REPORT | Information | WI Status report for Enhancement of 5G UE Policy (eUEPO) | eUEPO Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305421 | WI STATUS REPORT | Information | WI Status report for System Enabler for Service Function Chaining (SFC) | SFC Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305422 | WI STATUS REPORT | Information | WI Status report for Extensions to the TSC Framework to support DetNet (DetNet) | DetNet Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305423 | WI STATUS REPORT | Information | WI Status report for New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18_DCAMP_Ph2) | TEI18_DCAMP_Ph2 Rapporteur | Rel-18 | Noted | Noted | |
| 10.4 | S2-2305424 | WI STATUS REPORT | Information | WI Status report for Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | eNSAC Rapporteur | Rel-18 | Noted | Noted | |
| 10.5 | - | - | - | Review of the Work Plan | - | - | Docs:=3 | - | |
| 10.5 | S2-2304706 | WORK PLAN | Endorsement | SA WG2 Work Planning | SA WG2 Chair | Revision of S2-2303663 from S2#155. CC#4: Revised to S2-2306262. For CC#4 | Revised | ||
| 10.5 | S2-2306262 | WORK PLAN | Endorsement | SA WG2 Work Planning | SA WG2 Chair | - | Revision of S2-2304706. CC#4: The TUs for meeting SA WG2#157 were endorsed | Endorsed | |
| 10.5 | S2-2305227 | DISCUSSION | Discussion | The Discussion on ISAC | CMDI | Rel-19 | Not on agenda for this meeting. Not Handled | NOT HANDLED | |
| 10.6 | - | - | - | Planning future meetings | - | - | Docs:=0 | - | |
| 11 | - | - | - | Close of e-meeting | - | - | Docs:=0 | - | |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=480 | - | |
| 99 | S2-2305400 | WI STATUS REPORT | Information | WI Status report for Phase 2 for UAS, UAV and UAM (UAS_Ph2) | UAS_Ph2 Rapporteur | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304836 | CR | Approval | 23.503 CR1002 (Rel-18, 'B'): Update to expose dynamic satellite backhaul information from SMF to PCF | CMDI | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305012 | CR | Approval | 23.501 CR4456 (Rel-18, 'B'): AF triggered EAS Re-discovery Procedure in HR-SBO Roaming scenarios | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305348 | CR | Approval | 23.501 CR4558 (Rel-18, 'F'): Clarifications related to discontinuous coverage | Samsung | Rel-18 | Corrupt File (DRM)! WITHDRAWN | Withdrawn | |
| 99 | S2-2304737 | CR | Approval | 23.501 CR4393 (Rel-18, 'B'): Providing user location information of MBSR to the AMF | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304739 | CR | Approval | 23.501 CR4395 (Rel-18, 'B'): MT-LR procedure for when a MBSR is involved in the location of a UE | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304022 | CR | Approval | 23.503 CR0943 (Rel-17, 'F'): Change of SUPI to PEI association | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304023 | CR | Approval | 23.503 CR0944 (Rel-18, 'A'): Change of SUPI to PEI association | Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304334 | CR | Approval | 23.501 CR4273 (Rel-17, 'F'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | vivo | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304335 | CR | Approval | 23.501 CR4274 (Rel-18, 'A'): Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | vivo | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304387 | CR | Approval | 23.502 CR3998 (Rel-18, 'B'): Update to support of Satellite Edge Computing | China Mobile | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304772 | DISCUSSION | Agreement | PIN External Group ID or Internal Group vs PIN ID | Huawei, Hisilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304114 | CR | Approval | 23.502 CR3966 (Rel-18, 'C'): Addressing Editor s note related to AF requested QoS for a group of UEs | Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304633 | CR | Approval | 23.501 CR4365 (Rel-18, 'B'): Support for 5G VN group communication | NEC | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304625 | CR | Approval | 23.501 CR4362 (Rel-18, 'F'): NEF capability for the new AIML service | Samsung | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2305086 | CR | Approval | 23.501 CR4477 (Rel-18, 'B'): UE counting with at least one PDU session and one PDN connection | Samsung, Xiaomi | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304631 | CR | Approval | 23.502 CR3782R2 (Rel-18, 'B'): RAN Bitrate Report via the Control Plane Path | CATT | Rel-18 | Revision of S2-2302233 from S2#155. WITHDRAWN | Withdrawn | |
| 99 | S2-2304088 | LS OUT | Approval | [DRAFT] Reply LS on Paging Policy Information for Network Triggered Connection Resume INACTIVE and on INACTIVE eDRX above 10.24sec and SDT | Intel | Rel-18 | Response to S2-2303936 and S2-2303947. WITHDRAWN | Withdrawn | |
| 99 | S2-2304989 | CR | Approval | 23.228 CR1311 (Rel-18, 'B'): 23.228 Supporting AR Telephony Communication | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304990 | CR | Approval | 23.228 CR1312 (Rel-18, 'B'): 23.228 DCMF Service | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304991 | CR | Approval | 23.228 CR1313 (Rel-18, 'B'): 23.228 Trigger and Control of DC Media Negotiation | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304054 | CR | Approval | 23.501 CR4198 (Rel-18, 'C'): MBSR Allowed indication | KPN N.V. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304744 | CR | Approval | 23.501 CR4396 (Rel-18, 'B'): Non-3GPP Device Category Definitions | CableLabs | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304746 | DISCUSSION | Discussion | Non-3GPP Device Category Definitions | CableLabs | WITHDRAWN | Withdrawn | ||
| 99 | S2-2304424 | CR | Approval | 23.503 CR0969 (Rel-18, 'B'): Clarification on NWDAF-assisted PFD management in TS23.503 | CMDI | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2304533 | CR | Approval | 23.288 CR0759 (Rel-18, 'B'): Update procedure for accuracy monitoring at NWDAF containing AnLF | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304537 | CR | Approval | 23.501 CR3764R3 (Rel-18, 'B'): Extension of NWDAF registration information to reflect new accuracy checking capability | Huawei, HiSilicon, vivo | Rel-18 | Revision of S2-2302412 from S2#155. WITHDRAWN | Withdrawn | |
| 99 | S2-2304333 | CR | Approval | 23.501 CR4272 (Rel-18, 'B'): TS23.502 External Parameter Provisioning | vivo | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304543 | CR | Approval | 23.501 CR4338 (Rel-18, 'F'): On new list of CH controlled prioritized list of preferred SNPNs/GINs with validity information | OPPO | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2304102 | CR | Approval | 23.501 CR4208 (Rel-18, 'C'): Improving AF specific UE ID retrieval | Ericsson | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2305221 | LS OUT | Approval | [DRAFT] LS on OAM input data for QoS Sustainability Analytics | Orange | Withdrawn | |||
| 99 | S2-2304001 | CR | Approval | 23.501 CR4186 (Rel-18, 'C'): MBSR Authorization Update | KPN N.V. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304002 | CR | Approval | 23.501 CR4187 (Rel-18, 'C'): MBSR Allowed Indication | KPN N.V. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304003 | CR | Approval | 23.502 CR3945 (Rel-18, 'C'): MBSR Authorization Update in UCU | KPN N.V. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304004 | DISCUSSION | Discussion | Discussion on MBSR authorization indication and update | KPN N.V. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304043 | CR | Approval | 23.501 CR4193 (Rel-18, 'B'): High level feature description for AIML | Ericsson, Samsung | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304363 | CR | Approval | 23.502 CR3994 (Rel-18, 'F'): AMF support of CN to handle mobile terminated (MT) communication when UE is in RRC-Inactive state. | Sony | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304383 | CR | Approval | 23.501 CR4291 (Rel-18, 'D'): Terminology correction to avoid (almost) duplicate definition | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304384 | CR | Approval | 23.501 CR4292 (Rel-18, 'B'): Satellite coverage availability information provisioning to the AMF | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304460 | CR | Approval | 23.288 CR0757 (Rel-18, 'B'): DCCF Discovery principle enhancements for DCCF relocation | CMDI | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304752 | DISCUSSION | Discussion | Support for NAUN3 device connected behind FN-RG | CableLabs | WITHDRAWN | Withdrawn | ||
| 99 | S2-2304758 | CR | Approval | 23.316 CR2094 (Rel-18, 'B'): Differentiated service for NAUN3 devices connected behind a FN-RG | CableLabs | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304785 | CR | Approval | 23.548 CR0128 (Rel-18, 'F'): KI#4 Coordination among SMFs for Common EASDNAI determination | Huawei, HiSilicon | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2304790 | CR | Approval | 23.501 CR4407 (Rel-18, 'B'): NEF capability for the new AIML service | Samsung | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2304932 | CR | Approval | 23.501 CR4439 (Rel-18, 'F'): Update for the description of the Nupf interface in 5G reference architecture | China Telecommunications | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305025 | CR | Approval | 23.501 CR4462 (Rel-18, 'F'): Clarification for Clock quality reporting control information KI#1 | Spreadtrum Communications | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2305028 | CR | Approval | 23.501 CR4464 (Rel-18, 'F'): Providing clock quality metrics to UE KI#1 | Spreadtrum Communications | Rel-18 | CR Cover sheet error! WITHDRAWN | Withdrawn | |
| 99 | S2-2305061 | CR | Approval | 23.228 CR1315 (Rel-18, 'B'): 23.228 IMS Service | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305088 | CR | Approval | 23.503 CR1019 (Rel-18, 'B'): Clarify the usage of QoS monitoring for dynamic satellite backhaul | CATT | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305090 | CR | Approval | 23.502 CR4106 (Rel-18, 'B'): Satellite coverage information exposure to AMF from the AF | CATT | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2305170 | CR | Approval | 23.501 CR4515 (Rel-18, 'B'): Extension of NWDAF registration information to reflect new accuracy checking capability | Huawei, HiSilicon, Vivo | Rel-18 | Withdrawn | ||
| 99 | S2-2305327 | CR | Approval | 23.502 CR4147 (Rel-18, 'C'): Creating an RA when a Slice is Partially Supported in the RA | InterDigital Inc. | Rel-18 | Withdrawn | ||
| 99 | S2-2305346 | CR | Approval | 23.501 CR4556 (Rel-18, 'F'): 23.501 General Clause Update for AIMLsys | OPPO | Rel-18 | CR Cover sheet error! | Withdrawn | |
| 99 | S2-2305349 | CR | Approval | 23.501 CR4559 (Rel-18, 'F'): 23.501 Member UE terminology update | OPPO | Rel-18 | CR Cover sheet error! | Withdrawn | |
| 99 | S2-2305355 | CR | Approval | 23.502 CR4151 (Rel-18, 'F'): 23.502 Member UE terminology update | OPPO | Rel-18 | CR Cover sheet error! | Withdrawn | |
| 99 | S2-2305356 | CR | Approval | 23.501 CR4560 (Rel-18, 'B'): On new list of CH controlled prioritized list of preferred SNPNs/GINs with validity information | OPPO | Rel-18 | CR Cover sheet error! | Withdrawn | |
| 99 | S2-2305357 | CR | Approval | 23.502 CR4152 (Rel-18, 'F'): Update 23.502 for Multi-member AF session | OPPO | Rel-18 | CR Cover sheet error! | Withdrawn | |
| 99 | S2-2305358 | CR | Approval | 23.501 CR4561 (Rel-18, 'F'): MBSR authorization | Samsung | Rel-18 | Withdrawn |