TDoc | Title | Source |
---|---|---|
S2-2501354 | SA2#167 meeting Agenda | SA WG2 Chair |
S2-2501410 | SA WG2#167 meeting schedule | SA WG2 Chair |
S2-2502013 | Plan for the meeting | SA WG2 Chair |
TDoc | Title | Source |
---|---|---|
S2-2501356 | Draft (AutoGenerated) Report of SA WG2 meeting #166AHE | SA WG2 Secretary |
S2-2501409 | TSG/WG Leadership Elections | 3GPP MCC & TSG Chairs |
TDoc | Title | Source |
---|---|---|
S2-2501377 | LS from GSMA TSGNS: OSAppID usage by AppToken use case | GSMA TSGNS |
S2-2501379 | LS from ITU-T SG20: LS on the initiation of a new work item on draft Supplement ITU-T Y.Sup-DIoT-logistics 'Use cases for decentralized scheduling service of logistics' | ITU-T SG20 |
S2-2501380 | LS from GSMA NRG: LS to 3GPP on publication of a new version of NG.116 and request for a new SST for guaranteed bit rate NEST | GSMA NRG |
S2-2501381 | LS from CEN TC 278 WG 15: LS on Next Generation eCall | CEN TC 278 WG 15 |
S2-2501382 | LS from GSMA NRG: LS from GSMA NG to 3GPP on SMS to emergency center | GSMA NRG |
S2-2501415 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia |
S2-2501495 | [DRAFT] LS response on OSAppID usage by AppToken use case | Qualcomm France |
S2-2501497 | Discussion paper on OSAppID usage by AppToken use case | Qualcomm Incorporated |
S2-2501498 | [DRAFT] Reply LS on Robust Notification Alert for NTN-NR | EchoStar |
S2-2501523 | [DRAFT] Reply LS for OSAppID usage by AppToken use case | China Mobile |
S2-2501538 | [DRAFT] Reply LS for OSAppID usage by AppToken use case | Samsung |
S2-2501604 | [DRAFT] LS from GSMA TSGNS: OSAppID usage by AppToken use case | Ericsson |
S2-2501809 | [DRAFT] Reply LS for OSAppID usage by AppToken use case | ZTE |
S2-2502143 | [DRAFT] Reply LS to 'OSAppID usage by AppToken use case' | Apple |
S2-2502146 | New SST for Guaranteed Bit Rate Streaming Services | Qualcomm Incorporated |
S2-2502163 | [DRAFT] Reply LS for OSAppID usage by AppToken use case | Verizon Denmark |
S2-2502178 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia |
S2-2502179 | New SST for Guaranteed Bit Rate Streaming Services | Qualcomm Incorporated |
S2-2502180 | [DRAFT] Reply LS on publication of a new version of NG.116 and request for a new SST for guaranteed bit rate NEST | SA WG2 |
S2-2502644 | [DRAFT] LS on Next Generation eCall | Qualcomm |
S2-2502645 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia |
S2-2502775 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia |
S2-2502776 | LS on Next Generation eCall | SA WG2 |
TDoc | Title | Source |
---|---|---|
S2-2501637 | RAN Paging Priority corrections | Peraton Labs, CISA ECD, AT&T, Verizon |
S2-2502171 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
S2-2502173 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, Nokia, AT&T, T-Mobile USA, Verizon |
S2-2502297 | RAN Paging Priority corrections | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA |
S2-2502298 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA |
S2-2502299 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, Nokia, AT&T, Verizon, T-Mobile USA |
S2-2502534 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, Nokia, AT&T, Verizon, T-Mobile USA, Ericsson |
S2-2502535 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA, Ericsson |
S2-2502536 | RAN Paging Priority corrections | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA, Ericsson |
S2-2502576 | RAN Paging Priority corrections | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA, Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2501633 | MPS Subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
S2-2501634 | MPS Subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
S2-2502300 | MPS-subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA |
S2-2502325 | MPS-subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA |
S2-2502532 | MPS-subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA, Ericsson |
S2-2502533 | MPS-subscribed UE definition correction | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA, Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2502068 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2502069 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2502175 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2502176 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2502302 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2502303 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
TDoc | Title | Source |
---|---|---|
S2-2501599 | Clarification of Routing Indicator update via UPU | Ericsson, AT&T |
S2-2501600 | Update of Routing Indicator in SMF, SMSF | Ericsson, AT&T |
S2-2501601 | Update of Routing Indicator in SMF, SMSF | Ericsson, AT&T |
S2-2501602 | Update of Routing Indicator in SMF, SMSF | Ericsson, AT&T |
S2-2502304 | Clarification of Routing Indicator update via UPU | Ericsson, AT&T |
S2-2502305 | Update of Routing Indicator in SMF, SMSF | Ericsson, AT&T |
S2-2502537 | Clarification of Routing Indicator update via UPU | Ericsson, AT&T |
S2-2502538 | Update of Routing Indicator in SMF, SMSF | Ericsson, AT&T |
TDoc | Title | Source |
---|---|---|
S2-2502023 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502024 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502025 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502026 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502326 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502327 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502539 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
S2-2502540 | Common Procedure Types Sync with 38.305 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S2-2501748 | Discussion on the epoch issue for 5G Residence time calculation | ZTE |
S2-2501749 | Epoch for 5G Residence time calculation | ZTE |
S2-2501750 | Epoch for 5G Residence time calculation | ZTE |
S2-2501751 | Epoch for 5G Residence time calculation | ZTE |
S2-2501752 | Epoch for 5G Residence time calculation | ZTE |
S2-2501817 | Epoch reconstruction for residence time calculation | Nokia |
S2-2501818 | Epoch reconstruction for residence time calculation | Nokia |
TDoc | Title | Source |
---|---|---|
S2-2501711 | Correlate the Slice Load to an AOI when location is provided | Verizon, Oracle |
S2-2501964 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2501965 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2501966 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2502285 | Correlate the Slice Load to an AOI when location is provided | Verizon, Oracle, CATT |
S2-2502286 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2502287 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2502288 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
S2-2502529 | User consent check when correlating UE data collection and NWDAF data request | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2501362 | LS from CT WG4: LS on UUAA Unsubscribe procedure | CT WG4 (C4-245436) |
S2-2501621 | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Ericsson |
S2-2501622 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2501623 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2501624 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2501649 | [DRAFT] Reply LS on UUAA Unsubscribe procedure | CATT |
S2-2501650 | UUAA Unsubscribe | CATT |
S2-2501651 | UUAA Unsubscribe | CATT |
S2-2501652 | UUAA Unsubscribe | CATT |
S2-2501811 | [DRAFT] Reply LS on UUAA Unsubscribe procedure | LG Electronics |
S2-2501812 | UUAA Implicit Unsubscribe | LG Electronics |
S2-2501814 | UUAA Implicit Unsubscribe | LG Electronics |
S2-2501815 | UUAA Implicit Unsubscribe | LG Electronics |
S2-2501889 | Discussion on UUAA Unsubscribe Procedure | Huawei, HiSilicon |
S2-2501890 | Clarification on UUAA unsubscribe procedure | Huawei, HiSilicon |
S2-2501891 | Clarification on UUAA unsubscribe procedure | Huawei, HiSilicon |
S2-2501892 | Clarification on UUAA unsubscribe procedure | Huawei, HiSilicon |
S2-2501893 | [DRAFT] LS Reply to CT WG4 on UUAA Unsubscribe | Huawei, HiSilicon |
S2-2502089 | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Samsung |
S2-2502090 | Unsubscribe service operation with UAS NF | Samsung |
S2-2502091 | Unsubscribe service operation with UAS NF | Samsung |
S2-2502092 | Unsubscribe service operation with UAS NF | Samsung |
S2-2502334 | [DRAFT] Reply LS on UUAA Unsubscribe procedure | LG Electronics |
S2-2502335 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2502336 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2502337 | Unsubscribing from the UUAA-related notifications | Ericsson |
S2-2502545 | Reply LS on UUAA Unsubscribe procedure | SA WG2 |
TDoc | Title | Source |
---|---|---|
S2-2501500 | Clarification about MBS service area encoding | Nokia |
S2-2501867 | Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon, Nokia, Ericsson |
S2-2502354 | Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon, Nokia, Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2501881 | Update for terminology alignment between relative location and relative position | OPPO |
S2-2501885 | Update on application layer ID | OPPO |
S2-2502030 | Range concept usage instead of undefined direction | Nokia, Nokia Shanghai Bell |
S2-2502031 | Ranging_SL Application Layer ID decouple with Layer 2 ID | Nokia, Nokia Shanghai Bell |
S2-2502546 | Range concept usage instead of undefined distance | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S2-2501607 | Analysis on the number of LCS-UPP connections | Ericsson |
S2-2501608 | Clarify number of user plane connections for user plane positioning | Ericsson |
S2-2501609 | Clarify number of user plane connections for user plane positioning | Ericsson |
S2-2501657 | Discussion on user plane connection modification | CATT |
S2-2501658 | Update the user plane connection modification procedure | CATT |
S2-2501659 | Update the user plane connection modification procedure | CATT |
S2-2501744 | Clarification on the LCS-UP context release and update | ZTE |
S2-2501745 | Clarification on the LCS-UP context release and update | ZTE |
S2-2501746 | Clarification on the max number of LCS-UP connection per UE | ZTE |
S2-2501747 | Clarification on the max number of LCS-UP connection per UE. | ZTE |
S2-2501887 | Clarification on Positioning Procedure over User Plane | Huawei, HiSilicon |
S2-2501888 | Clarification on Positioning Procedure over User Plane | Huawei, HiSilicon |
S2-2502027 | Clarification of Notification Target Address between AMF and LMF | Nokia, Nokia Shanghai Bell |
S2-2502028 | Clarification of Notification Target Address between AMF and LMF | Nokia, Nokia Shanghai Bell |
S2-2502064 | Issues on LMF relocation for multiple LCS-UPP connection maintanence | OPPO |
S2-2502065 | Update to LCS-UPP procedures for multiple connections | OPPO |
S2-2502066 | Update to LCS-UPP procedures for multiple connections | OPPO |
S2-2502328 | Update the user plane connection modification procedure | CATT |
S2-2502329 | Clarify number of user plane connections for user plane positioning | Ericsson |
S2-2502330 | Clarify number of user plane connections for user plane positioning | Ericsson |
S2-2502331 | Clarification on the LCS-UP context release and update | ZTE |
S2-2502332 | Clarification on the LCS-UP context release and update | ZTE |
S2-2502333 | Clarification on Positioning Procedure over User Plane | Huawei, HiSilicon |
S2-2502541 | Update the user plane connection modification procedure | CATT |
S2-2502542 | Clarify number of user plane connections for user plane positioning | Ericsson |
S2-2502543 | Clarification on the LCS-UP context release and update | ZTE |
S2-2502544 | Clarification on the LCS-UP context release and update | ZTE |
TDoc | Title | Source |
---|---|---|
S2-2501411 | Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon |
S2-2501412 | Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon |
S2-2501413 | Allow NSSF to provide slice validity time during slice selection | Oracle, Verizon |
S2-2501414 | DP - slice validity time during NS Selection R19 | Oracle, Verizon |
S2-2501575 | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT DOCOMO, Nokia |
S2-2501577 | Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia |
S2-2501578 | Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia |
S2-2501579 | Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia. |
S2-2501580 | Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia |
S2-2501755 | Update on UE Context in AMF to support Network Slice Replacement | LG Electronics |
S2-2501805 | Clarification on temporary slice and NS-AoS | ZTE |
S2-2501806 | Clarification on temporary slice and NS-AoS | ZTE |
S2-2501807 | Clarification on always-on PDU Session | ZTE |
S2-2501808 | Clarification on always-on PDU Session | ZTE |
S2-2501937 | Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE |
S2-2501938 | Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE |
S2-2502125 | Clarification on Configured NSSAI for temporary slice | Samsung |
S2-2502126 | Clarification on Configured NSSAI for temporary slice _23.501_R19 | Samsung |
S2-2502399 | Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon |
S2-2502400 | Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon |
S2-2502649 | Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon |
TDoc | Title | Source |
---|---|---|
S2-2501445 | Clarifications on ECN marking for L4S | Apple |
S2-2501446 | Clarifications on ECN marking for L4S | Apple |
S2-2501905 | Clarifications for activation of QoS monitoring | Huawei, HiSilicon, Oracle |
S2-2501906 | Clarifications for activation of QoS monitoring | Huawei, HiSilicon, Oracle |
S2-2501907 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2501908 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2501909 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2501910 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2502110 | Discussion on Averaging Window in AQP | Ericsson |
S2-2502111 | Removal of Averaging Window from the AQP | Ericsson |
S2-2502112 | Removal of Averaging Window from the AQP | Ericsson |
S2-2502157 | Clarification on PSIHI and retransmissions | Nokia |
S2-2502158 | Clarification on PSIHI and retransmissions-mirror | Nokia |
S2-2502406 | Clarifications on ECN marking for L4S | Apple |
S2-2502407 | Clarifications on ECN marking for L4S | Apple |
S2-2502408 | Clarification on PSIHI and retransmissions-mirror | Nokia |
S2-2502660 | Clarifications for activation of QoS monitoring | Huawei, HiSilicon, Oracle |
S2-2502671 | Clarifications for activation of QoS monitoring | Huawei, HiSilicon, Oracle |
TDoc | Title | Source |
---|---|---|
S2-2501373 | LS from SA WG4: Reply LS on Binding Information | SA WG4 |
S2-2501877 | Discussion on DC App Info mismatches in ADC procedures | Samsung |
S2-2501878 | Clarification on DC App Info mismatches in ADC procedures | Samsung |
S2-2501879 | Clarification on DC App Info mismatches in ADC procedures | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2501801 | Clarification on the UPF event subscription | ZTE |
S2-2501802 | Clarification on the UPF event subscription | ZTE |
S2-2501843 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon |
S2-2501844 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon |
S2-2501859 | Clarification on the UPF Event Exposure | Huawei, HiSilicon |
S2-2501860 | Clarification on the UPF Event Exposure | Huawei, HiSilicon |
S2-2502348 | Clarification on the UPF event subscription | ZTE |
S2-2502349 | Clarification on the UPF event subscription | ZTE |
S2-2502350 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon |
S2-2502351 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon |
S2-2502352 | Clarification on the UPF Event Exposure | Huawei, HiSilicon, Nokia |
S2-2502353 | Clarification on the UPF Event Exposure | Huawei, HiSilicon, Nokia, Ericsson |
S2-2502547 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon, Nokia |
S2-2502548 | Clarification on the UPF Event Exposure | Huawei, HiSilicon, Nokia, Ericsson |
S2-2502549 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon, Nokia |
S2-2502550 | Correction on the UPF event subscription via I-SMF | Huawei, HiSilicon, Nokia |
S2-2502785 | Clarification on the UPF Event Exposure | Huawei, HiSilicon, Nokia, Ericsson |
S2-2502786 | Clarification on the UPF Event Exposure | Huawei, HiSilicon, Nokia, Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2501514 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung |
S2-2501515 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung |
S2-2501516 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung |
S2-2501517 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung |
S2-2501839 | AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon |
S2-2501840 | AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon |
S2-2501841 | AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon |
S2-2501842 | AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon |
S2-2501864 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2501865 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2501866 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2501872 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2501873 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2501874 | Failure notification for Simultaneous Connectivity | LG Electronics |
S2-2502409 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
S2-2502410 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
S2-2502411 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
S2-2502412 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
S2-2502413 | AF subscription for Simultaneous Connectivity | LG Electronics |
S2-2502414 | Failure notification for Simultaneous Connectivity | LG Electronics |
S2-2502415 | AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon |
S2-2502661 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
S2-2502662 | SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung, LG Electronics |
TDoc | Title | Source |
---|---|---|
S2-2501436 | Supplement of functional description of NWDAF | ZTE |
S2-2501437 | Supplement of functional description of NWDAF | ZTE |
S2-2501438 | ML Model storage description alignment | ZTE |
S2-2501439 | ML Model storage description alignment | ZTE |
S2-2501496 | Add Nnef_UeAddress Service to NEF services | Nokia |
S2-2501710 | Addition of delay threshold match indication | Verizon, Oracle |
S2-2501959 | Correction on accuracy monitoring description and procedure | vivo |
S2-2501960 | Correction on accuracy monitoring description and procedure | vivo |
S2-2502289 | Supplement of functional description of NWDAF | ZTE |
S2-2502290 | Supplement of functional description of NWDAF | ZTE |
S2-2502291 | ML Model storage description alignment | ZTE |
S2-2502292 | ML Model storage description alignment | ZTE |
S2-2502293 | Add Nnef_UeAddress Service to NEF services | Nokia |
S2-2502294 | Addition of delay threshold match indication | Verizon, Oracle |
S2-2502295 | Correction on accuracy monitoring description and procedure | vivo |
S2-2502296 | Correction on accuracy monitoring description and procedure | vivo |
S2-2502530 | Addition of delay threshold match indication | Verizon, Oracle |
S2-2502531 | Supplement of functional description of NWDAF | ZTE |
TDoc | Title | Source |
---|---|---|
S2-2501368 | LS from RAN WG2: LS on Satellite IDs for store-and-forward operation | RAN WG2 |
S2-2501518 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], Nokia |
S2-2501519 | Control Plane Service Request procedure updates for S&F | Nokia |
S2-2501520 | Mode transition between S&F and Normal Mode | Nokia |
S2-2501521 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Nokia |
S2-2501610 | AMF selection for regenerative payload | Ericsson |
S2-2501611 | Split MME handling of UE attach with PDN connection | Ericsson |
S2-2501612 | Handling of UE access to satellite which has no UE context | Ericsson |
S2-2501613 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], Ericsson |
S2-2501614 | Considerations and proposal for the S&F mode change behaviour | Ericsson |
S2-2501615 | Support for satellite access with regenerative payload | Ericsson |
S2-2501666 | Update on UE-Satellite-UE communication determination | vivo |
S2-2501686 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], vivo |
S2-2501687 | Transition between S&F and normal | vivo |
S2-2501688 | Clarification on S&F wait timer | vivo |
S2-2501689 | PDN connection handling under S&F operation | vivo |
S2-2501695 | Clarification on support of Store and Forward Satellite Operation | ZTE Corporation |
S2-2501726 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], Sateliot |
S2-2501729 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | [CATT], Sateliot |
S2-2501740 | Procedure updates for S&F | [Vivo, Huawei, HiSilicon], Sateliot |
S2-2501778 | Define UE behaviour when SF Wait Timer is running | MediaTek Inc. |
S2-2501780 | No Necessity to define UE in S&F mode | MediaTek Inc. |
S2-2501783 | Support of Attach with PDN connection for split MME architecture | LG Electronics, NEC, Samsung, vivo |
S2-2501784 | Transitioning between operation in S&F mode and normal mode | LG Electronics |
S2-2501785 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], LG Electronics |
S2-2501810 | Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | [NTT DOCOMO, Nokia], China Telecom |
S2-2501813 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], China Telecom |
S2-2501816 | Update on S&F Satellite Operation for UE and MME | China Telecom |
S2-2501821 | Discussion on the enhanced discontinuous network coverage for satellite access under S&F mode | China Telecom |
S2-2501924 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | CATT |
S2-2501925 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], CATT |
S2-2501926 | Transition between S&F Mode and Normal Mode | [Qualcomm Incorporated], CATT |
S2-2501929 | Support of UE-satellite-UE communications when serving satellite changes | [vivo, CSCN, Tencent, Honor, Thales,] CATT, [NTT DOCOMO, China Telecom] |
S2-2501930 | Procedure update for UE-Satellite-UE communication | [NTT DOCOMO, China Telecom, Samsung,] CATT |
S2-2501931 | Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | [NTT DOCOMO, Nokia, China Telecom,] CATT |
S2-2501932 | Mobility procedure for UE-Satellite-UE communication in IMS - continuation of optimized media routing | [NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom,] CATT |
S2-2501933 | Mobility procedure for UE-Satellite-UE communication in IMS - ground fallback | [NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom,] CATT |
S2-2501934 | Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | [Huawei, HiSilicon, NTT DOCOMO, China Telecom,] CATT |
S2-2501940 | Support of UE-satellite-UE communications when serving satellite changes | [vivo, CSCN, Tencent, Honor, Thales, CATT,] NTT DOCOMO[, China Telecom] |
S2-2501941 | Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | [Huawei, HiSilicon,] NTT DOCOMO[, China Telecom, CATT] |
S2-2501961 | Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon [, Samsung] |
S2-2501962 | Align terminology for store and forward operations | Huawei, HiSilicon |
S2-2501963 | Support of UE-satellite-UE communications when serving satellite changes | [vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO], Huawei, HiSilicon, China Telecom |
S2-2501985 | Transition between S&F and normal for the UE in ECM-CONNECTED | OPPO |
S2-2501986 | Support of Regenerative Payload with NG-RAN Node Onboard Satellite | OPPO, Huawei, HiSilicon |
S2-2501987 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], OPPO |
S2-2501988 | DP on UE accessing to a satellite not in the monitoring list | Xiaomi |
S2-2501989 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], Xiaomi |
S2-2501990 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Xiaomi |
S2-2501991 | 23401 Transition between S&F Mode and Normal Mode | [Qualcomm Incorporated], Xiaomi |
S2-2501992 | Description alignment for S&F procedure | Xiaomi |
S2-2502016 | Remove NOTE 6 for S&F | Xiaomi |
S2-2502038 | Support of Attach with PDN connection for split MME architecture | [LG Electronics, NEC, Samsung],CATT |
S2-2502058 | Update for support of UE-Satellite-UE communication | CATT |
S2-2502060 | Clarification on the condition for UE indicating S&F capability | ZTE |
S2-2502061 | Update S&F Monitoring List info in the SERVICE REQUEST procedure | ZTE |
S2-2502062 | Clarification on the MME's authentication behavior in NAS procedure | ZTE |
S2-2502063 | Update to Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], ZTE |
S2-2502075 | HSS table clarification | Samsung, Ericsson |
S2-2502100 | Procedure update for UE-Satellite-UE communication | NTT DOCOMO, [China Telecom, Samsung] |
S2-2502101 | Procedure update for UE-Satellite-UE communication | NTT DOCOMO, [Samsung, China Telecom] |
S2-2502123 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Samsung |
S2-2502129 | Clarification related to terminology and on MME providing list in detach procedure. | Samsung |
S2-2502140 | Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | [NTT DOCOMO, Nokia], CSCN |
S2-2502166 | UE Detach for S&F Mode Access | Qualcomm Incorporated |
S2-2502167 | Transition between S&F Mode and Normal Mode | Qualcomm Incorporated, NEC |
S2-2502172 | Support of S&F Monitoring List in S&F Mode | [Huawei, HiSilicon, Samsung], Ericsson |
S2-2502185 | AMF selection for regenerative payload | Ericsson |
S2-2502186 | Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon [, Samsung] |
S2-2502187 | Procedure updates for S&F | [vivo, Huawei, HiSilicon], Sateliot, [Nokia, ZTE, Xiaomi] |
S2-2502188 | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | CATT |
S2-2502189 | Transition between S&F Mode and Normal Mode | Qualcomm Incorporated, NEC |
S2-2502190 | No Necessity to define UE in S&F mode | MediaTek Inc. |
S2-2502191 | UE Detach for S&F Mode Access | Qualcomm Incorporated |
S2-2502192 | Update on S&F Satellite Operation for UE and MME | China Telecom |
S2-2502236 | Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | [NTT DOCOMO, Nokia], China Telecom, vivo, CSCN |
S2-2502237 | Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | [NTT DOCOMO, Nokia, China Telecom,] CATT |
S2-2502238 | Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | Huawei, HiSilicon, NTT DOCOMO, China Telecom, CATT |
S2-2502239 | Mobility procedure for UE-Satellite-UE communication in IMS – continuation of optimized media routing | [NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom,] CATT |
S2-2502240 | Mobility procedure for UE-Satellite-UE communication in IMS – ground fallback | [NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom,] CATT |
S2-2502241 | Support of UE-satellite-UE communications when serving satellite changes | [vivo, CSCN, Tencent, Honor, Thales,] CATT, [NTT DOCOMO, China Telecom] |
S2-2502242 | Update for support of UE-Satellite-UE communication | CATT |
S2-2502243 | Procedure update for UE-Satellite-UE communication | NTT DOCOMO, [China Telecom], Samsung |
S2-2502244 | Procedure update for UE-Satellite-UE communication | NTT DOCOMO, [Samsung, China Telecom] |
S2-2502245 | Clarification on support of Store and Forward Satellite Operation | ZTE Corporation |
S2-2502246 | Clarification related to terminology and on MME providing list in detach procedure. | Samsung |
S2-2502247 | Align terminology for store and forward operations | Huawei, HiSilicon |
S2-2502248 | Clarification on the condition for UE indicating S&F capability | ZTE |
S2-2502275 | Procedure updates for S&F | [vivo, Huawei, HiSilicon], Sateliot, [Nokia, ZTE, Xiaomi] |
S2-2502448 | Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon [, Samsung] |
S2-2502449 | Procedure updates for S&F | [vivo, Huawei, HiSilicon], Sateliot, [Nokia, ZTE, Xiaomi] |
S2-2502450 | Reply LS on Satellite IDs for store-and-forward operation | SA WG2 |
S2-2502451 | Transition between S&F Mode and Normal Mode | Qualcomm Incorporated |
S2-2502452 | Update on S&F Satellite Operation for UE and MME | China Telecom |
S2-2502453 | Clarification on S&F wait timer | vivo |
S2-2502454 | Clarification on support of Store and Forward Satellite Operation | ZTE Corporation |
S2-2502455 | Clarification related to terminology and on MME providing list in detach procedure. | Samsung |
S2-2502456 | Align terminology for store and forward operations | Huawei, HiSilicon |
S2-2502457 | Clarification on the condition for UE indicating S&F capability | ZTE |
S2-2502458 | Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia, China Telecom, vivo, CSCN |
S2-2502459 | Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia, China Telecom, CATT |
S2-2502506 | UE Detach for S&F Mode Access | Qualcomm Incorporated |
S2-2502507 | Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | Huawei, HiSilicon, NTT DOCOMO, China Telecom, CATT, Ericsson |
S2-2502508 | Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom, CATT |
S2-2502509 | Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom, CATT |
S2-2502510 | Support of UE-satellite-UE communications when serving satellite changes | Vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO, China Telecom, Huawei, HiSilicon |
S2-2502511 | Update for support of UE-Satellite-UE communication | CATT |
S2-2502512 | Procedure update for UE-Satellite-UE communication | NTT DOCOMO, China Telecom, Samsung |
S2-2502513 | Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon, Samsung |
S2-2502514 | Procedure updates for S&F | Vivo, Huawei, HiSilicon, Sateliot, Nokia, ZTE, Xiaomi, Samsung |
S2-2502525 | Transition between S&F Mode and Normal Mode | Qualcomm Incorporated, NEC |
S2-2502526 | Support of UE-satellite-UE communications when serving satellite changes | Vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO, China Telecom, Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S2-2501374 | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 |
S2-2501378 | LS from SA WG3: LS on IMS support for AF authorization and IMS avatar communication | SA WG3 |
S2-2501501 | KI#1: Editorial updates to IMS Subscribe/Notify Framework Architecture | Ericsson |
S2-2501502 | KI#1: Update to NEF Services | Ericsson |
S2-2501503 | KI#8: Update to Architecture for avatar communications | Ericsson |
S2-2501504 | KI#3: Update to DC interworking with MTSI UE | Ericsson |
S2-2501505 | KI#2: Generalizing Information Retrieval | Ericsson |
S2-2501660 | Update on multiplexing handling | vivo |
S2-2501661 | De-multiplexing ADC to avoid multiplexing ADCs with same stream ID | vivo |
S2-2501662 | Abbreviations of ADC and BDC | vivo |
S2-2501663 | Adding more event filters for ADC media type | vivo |
S2-2501664 | Update on support of DC interworking | vivo |
S2-2501665 | Modification on general description for standalone IMS DC session | vivo |
S2-2501731 | Correction of detection criteria for event exposure | China Mobile |
S2-2501732 | Updates on procedure and service of DC interworking via DC AS | China Mobile |
S2-2501733 | Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile |
S2-2501734 | Service updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile, Samsung |
S2-2501735 | Correction on DC multiplexing procedures | China Mobile |
S2-2501736 | KI#2: Update to Network Capability Exposure Procedures | China Mobile, [Ericsson, NTT DOCOMO] |
S2-2501737 | Updates on downloading Avatar representation in UE centric rendering mode | China Mobile |
S2-2501738 | Updates on HSS Nhss_ImsEventExposure service | China Mobile |
S2-2501739 | KI#2: Procedure of adding bootstrap DC to existing IMS session | China Mobile |
S2-2501790 | Resolving ENs on Avatar communication | Qualcomm Incorporated |
S2-2501792 | Clarification on third-party user ID provisioning procedure | Qualcomm Incorporated |
S2-2501861 | KI#4: Update of procedure description | Nokia, Samsung, Qualcomm |
S2-2501862 | KI#2: Update of procedures | Nokia |
S2-2501883 | Resolving ENs on Avatar ID List | Qualcomm Incorporated, ZTE |
S2-2501950 | Clarification on DC Application Server | ZTE |
S2-2501951 | Address EN on Avatar Representation Downloading | ZTE |
S2-2501952 | KI#2: Update to Network Capability Exposure Procedures | [Ericsson, NTT DOCOMO], ZTE |
S2-2501953 | Clarification on Third Party ID Signing and Verification Procedure | ZTE |
S2-2501954 | [DRAFT] Reply LS on IMS support for AF authorization and IMS avatar communication | ZTE |
S2-2502076 | [DRAFT] LS on IMS DC multiplexing | Huawei, HiSilicon |
S2-2502077 | KI#8 update architecture description for avatar communication | Huawei, HiSilicon |
S2-2502078 | Update NEF services to align with IMS AS services | Huawei, HiSilicon |
S2-2502079 | Update Network Capability Exposure Procedure | Huawei, HiSilicon |
S2-2502094 | Complete the details for KI#2 | NTT DOCOMO |
S2-2502095 | HSS handling for subscription with IMS | Samsung |
S2-2502096 | MMTel media removal clarification | Samsung |
S2-2502135 | KI#7: Updates on determination and handling of multiplexing | Samsung |
S2-2502136 | KI#3: Updates on the ADC Interworking via DC AS procedure | Samsung |
S2-2502137 | KI#8: EN resolutions for Avatar communication | Samsung |
S2-2502138 | KI#3: Updates on interworking with MTSI UE procedures | Samsung |
S2-2502139 | [DRAFT] Reply to LS on IMS support for AF authorization and IMS avatar communication | Samsung |
S2-2502193 | [DRAFT] Reply to LS on IMS support for AF authorization and IMS avatar communication | Samsung |
S2-2502194 | Resolving ENs on Avatar communication | Qualcomm Incorporated |
S2-2502195 | Address EN on Avatar Representation Downloading | ZTE |
S2-2502196 | Updates on downloading Avatar representation in UE centric rendering mode | China Mobile |
S2-2502197 | KI#8: Update to Architecture for avatar communications | Ericsson |
S2-2502198 | Update network-centric procedure of Avatar Communication | Huawei, HiSilicon, Ericsson, ZTE, Samsung |
S2-2502199 | Resolving ENs on Avatar ID List | Qualcomm Incorporated, ZTE |
S2-2502200 | Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile |
S2-2502201 | Service updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile, Samsung |
S2-2502202 | [DRAFT] LS on IMS DC multiplexing | Huawei, HiSilicon |
S2-2502249 | Update on multiplexing handling | vivo |
S2-2502266 | KI#2: Update to Network Capability Exposure Procedures | [Ericsson, NTT DOCOMO], China Mobile, ZTE |
S2-2502267 | KI#2: Update of procedures | Nokia |
S2-2502268 | KI#2: Procedure of adding bootstrap DC to existing IMS session | China Mobile |
S2-2502269 | Update Network Capability Exposure Procedure | Huawei, HiSilicon |
S2-2502270 | KI#2: Generalizing Information Retrieval | Ericsson |
S2-2502271 | Complete the details for KI#2 | NTT DOCOMO |
S2-2502272 | KI#1: Update to NEF Services | Ericsson |
S2-2502273 | KI#4: Update of procedure description | Nokia, Samsung, Qualcomm |
S2-2502274 | HSS handling for subscription with IMS | Samsung |
S2-2502434 | Reply to LS on IMS support for AF authorization and IMS avatar communication | SA WG2 |
S2-2502435 | Resolving ENs on Avatar communication | Qualcomm Incorporated |
S2-2502436 | Updates on downloading Avatar representation in UE centric rendering mode | China Mobile |
S2-2502437 | Address EN on Avatar Representation Downloading | ZTE |
S2-2502438 | KI#8: Update to Architecture for avatar communications | Ericsson |
S2-2502439 | Update network-centric procedure of Avatar Communication | Huawei, HiSilicon, Ericsson, ZTE, Samsung |
S2-2502440 | Resolving ENs on Avatar ID List | Qualcomm Incorporated, ZTE |
S2-2502441 | Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile |
S2-2502442 | Update on multiplexing handling | vivo |
S2-2502443 | Service updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile, Samsung |
S2-2502444 | [DRAFT] LS on IMS DC multiplexing | Huawei, HiSilicon |
S2-2502445 | KI#2: Update to Network Capability Exposure Procedures | Ericsson, NTT DOCOMO, China Mobile, ZTE |
S2-2502446 | KI#2: Procedure of adding bootstrap DC to existing IMS session | China Mobile |
S2-2502447 | Update Network Capability Exposure Procedure | Huawei, HiSilicon |
S2-2502460 | KI#4: Update of procedure description | Nokia, Samsung, Qualcomm |
S2-2502499 | Complete the details for KI#2 | NTT DOCOMO |
S2-2502500 | Update Network Capability Exposure Procedure | Huawei, HiSilicon |
S2-2502501 | KI#2: Update of procedures | Nokia |
S2-2502502 | KI#4: Update of procedure description | Nokia, Samsung, Qualcomm |
S2-2502503 | Resolving ENs on Avatar communication | Qualcomm Incorporated |
S2-2502504 | Address EN on Avatar Representation Downloading | ZTE |
S2-2502505 | Update network-centric procedure of Avatar Communication | Huawei, HiSilicon, Ericsson, ZTE, Samsung |
S2-2502521 | Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile |
S2-2502522 | LS on IMS DC multiplexing | SA WG2 |
S2-2502523 | KI#2: Update of procedures | Nokia |
S2-2502524 | KI#4: Update of procedure description | Nokia, Samsung, Qualcomm, ZTE |
TDoc | Title | Source |
---|---|---|
S2-2501358 | LS from RAN WG2: Reply to SA2 LS on multi-modality awareness | RAN WG2 (R2-2409272) |
S2-2501359 | LS from RAN WG3: Reply LS on multi-modality awareness at RAN | RAN WG3 (R3-245682) |
S2-2501360 | LS from SA WG4: Reply LS on Introduction of Extensions to IP Packet Filters for Differentiated QoS Handling for Multiplexed Media Flows | SA WG4 (S4-242065) |
S2-2501361 | LS from SA WG4: LS Reply on multi-modality awareness | SA WG4 (S4-242223) |
S2-2501365 | LS from RAN WG2: Reply LS to SA2 on PDU set | RAN WG2 |
S2-2501366 | LS from RAN WG2: Reply LS on Application-Layer FEC Awareness at RAN | RAN WG2 |
S2-2501369 | LS from RAN WG2: LS on XR UL bit rate control | RAN WG2 |
S2-2501370 | LS from RAN WG3: Reply LS on multi-modality awareness | RAN WG3 |
S2-2501371 | LS from RAN WG3: Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | RAN WG3 |
S2-2501376 | LS from TSG SA: LS on multi-modality awareness | TSG SA |
S2-2501383 | LS from SA WG4: Reply to LS on Application-Layer FEC Awareness at RAN | SA WG4 |
S2-2501385 | LS from RAN WG3: Reply LS on FS_XRM Ph2 for available data rate report | RAN WG3 |
S2-2501423 | KI#1, Support the PDU Set Information Marking Support Indication | Vivo, Nokia |
S2-2501424 | KI#1, Support the PDU Set Information Marking Support Indication | vivo |
S2-2501425 | KI#1, Support the PDU Set Information Marking Support Indication | vivo |
S2-2501426 | KI#9, Support of Available Data Rate | vivo |
S2-2501427 | KI#9, Support of Rate limitation | Vivo, [Meta USA], Tencent, [Nokia] |
S2-2501428 | Discussion on Multiplexed Media Identification Information for end-to-end ciphered traffic | vivo |
S2-2501429 | Support of DL Multiplexed Media Identification Information for end-to-end ciphered traffic | vivo |
S2-2501430 | Support of multi-modality awareness | vivo |
S2-2501431 | Support of multi-modality awareness | vivo |
S2-2501432 | Traffic detection and QoS handling of multiplexed data flows | OPPO, China Mobile, Lenovo, Xiaomi, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, Google, [vivo] |
S2-2501433 | [DRAFT] LS reply on multi-modality awareness | ZTE |
S2-2501434 | Optimization on Multi-modal service | ZTE |
S2-2501435 | Optimization on Multi-modal service | ZTE |
S2-2501463 | Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, ZTE |
S2-2501464 | Support for RAN Multimodality awareness | [Qualcomm, Nokia], China Mobile, Xiaomi, OPPO |
S2-2501465 | [DRAFT] Reply to LS on multi-modality awareness | China Mobile |
S2-2501470 | Correction on the Support of MoQ | Nokia |
S2-2501471 | Procedures for handling end-to-end encrypted XRM flows | Nokia [Google, Futurewei, InterDigital Inc., China Mobile, Huawei, HiSilicon, Ericsson, Nokia, Apple] |
S2-2501508 | Support multiplexing media traffic with additional Packet Filter | CATT, Nokia, OPPO, Lenovo, Samsung, Xiaomi |
S2-2501509 | The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo |
S2-2501510 | The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo |
S2-2501513 | Corrections for KI#2 Support of transferring media related information over N6 | China Mobile, [Huawei, Hisilicon,] Interdigital, [Xiaomi, Ericsson, NTT DOCOMO, Nokia] |
S2-2501536 | Support of multi-modal awareness at NG-RAN | China Telecom |
S2-2501537 | Support of multi-modal awareness at NG-RAN | China Telecom |
S2-2501629 | Available Data Rate Reporting for GBR QoS Flows | InterDigital Inc. |
S2-2501632 | KI#3: Align the mapping of PSI value to DSPC Drop Precedence setting | China Mobile |
S2-2501641 | KI#4: Resolve the incorrect multiplex support in NOTE | China Mobile |
S2-2501642 | 23.502 Support of sending MMSID from CN to the RAN | Lenovo |
S2-2501643 | 23.503 Support of sending MMSID from CN to the RAN | Lenovo |
S2-2501644 | 23.503 Support of AL-FEC awareness at NG-RAN | Lenovo, OPPO, Tencent, Tencent Cloud, China Telecom |
S2-2501667 | Multi-modality awareness at RAN | OPPO |
S2-2501668 | Multi-modality awareness at RAN | OPPO |
S2-2501724 | Support Alternative QoS profile with PDU Set QoS and Notification Control | [CATT, Nokia, Tencent, vivo, Samsung, Xiaomi], China Mobile |
S2-2501781 | KI#9, Support of Rate limitation | [Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson], Samsung |
S2-2501786 | Support for Multimodality awareness at RAN | Samsung |
S2-2501787 | Support for Multimodality awareness at RAN | Samsung |
S2-2501788 | Support for Multimodality awareness at RAN | Samsung |
S2-2501791 | [DRAFT] LS Reply on multi-modality awareness | Samsung |
S2-2501793 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung |
S2-2501794 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung |
S2-2501795 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung |
S2-2501797 | [DRAFT] LS Reply on Application-Layer FEC Awareness at RAN | Samsung |
S2-2501851 | Corrections for 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, [CATT, China Telecom, Meta USA, CMCC, Xiaomi, Samsung, Huawei, HiSilicon, Ericsson, Nokia, Apple] |
S2-2501852 | Enhancements for AF/AS triggered expedite data transfer | [Nokia, InterDigital Inc.] Lenovo, Tencent, Tencent Cloud |
S2-2501853 | 23.502 PDU set based handling without PDU set QoS parameters | Lenovo |
S2-2501875 | Support for Multi-modal Service ID awareness at RAN | LG Electronics |
S2-2501876 | Support for PDU Set Content Ratio | LG Electronics |
S2-2501884 | Procedures for handling end-to-end encrypted XRM flows | [Google, Futurewei, InterDigital Inc.,] China Mobile, [Huawei, HiSilicon, Ericsson, Nokia, Apple ] |
S2-2501911 | Support Alternative QoS profile with PDU Set QoS and Notification Control | [CATT, Nokia, Tencent, vivo, Samsung, Xiaomi], Huawei, HiSilicon |
S2-2501912 | PDU Set support in QoS Notification Control and Alternative QoS | [Nokia, vivo,] Huawei, HiSilicon, [Xiaomi] |
S2-2501913 | XRM_Ph2_KI3 Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network | [Intel, InterDigital Inc, China Telecom, Nokia, Tencent, Xiaomi], Huawei, HiSilicon |
S2-2501914 | Enhancements for AF/AS triggered expedite data transfer | [Nokia, Tencent, Tencent Cloud, InterDigital Inc.], Huawei, HiSilicon |
S2-2501915 | 23.501 Data boosting triggered by AS/AF | [Lenovo, Tencent, Tencent Cloud, CATT, China Telecom, Meta USA, CMCC, Xiaomi, Samsung,] Huawei, HiSilicon, [Ericsson, Nokia, Apple] |
S2-2501916 | KI#9, Support of Rate limitation | [vivo, Meta USA, Tencent, Nokia], Huawei, HiSilicon |
S2-2501917 | KI#9, Support of Rate limitation | [Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson], Huawei, HiSilicon |
S2-2501918 | Support of available data rate exposure | Huawei, HiSilicon, Nokia |
S2-2501919 | Support of available data rate exposure | Huawei, HiSilicon |
S2-2501920 | Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon |
S2-2501921 | Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon |
S2-2502003 | Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO, [vivo] |
S2-2502004 | Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO |
S2-2502005 | Enhancements for AF/AS triggered expedite data transfer | Nokia, [Tencent, Tencent Cloud, InterDigital] |
S2-2502006 | KI#9, Support of Available Data Rate | Nokia |
S2-2502067 | Traffic detection and QoS handling of multiplexed data flows | NTT DOCOMO, Nokia |
S2-2502070 | XRM_Ph2_KI1 PDU Set Information Marking witout DL Set QoS | Xiaomi, OPPO, |
S2-2502071 | XRM_Ph2_KI1 PDU Set Information Marking witout DL Set QoS | Xiaomi, |
S2-2502072 | Discussion on AL-FEC awareness at NG-RAN | Xiaomi |
S2-2502073 | XRM_Ph2_KI1_AL-FEC support | Xiaomi |
S2-2502074 | XRM_Ph2_KI1_AL-FEC support | Xiaomi |
S2-2502085 | 23.501 CR5952: Providing Multi-Modal Awareness to NG-RAN | InterDigital Inc. |
S2-2502088 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson |
S2-2502103 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson |
S2-2502108 | PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson [, InterDigital] Nokia, Google, Huawei, HiSilicon] |
S2-2502109 | Solving KI#4 with N6 metadata using KI#2 mechanisms | Ericsson |
S2-2502113 | KI#4 EN removal | Ericsson |
S2-2502114 | KI#4 EN removal and MPQUIC recomendation | Ericsson |
S2-2502115 | Multi-modality awareness | Sony |
S2-2502118 | Multi-modality awareness | Sony |
S2-2502119 | Multi-modality awareness | Sony |
S2-2502130 | Support Differentiated QoS handling for encrypted multiplexed media flows | [Nokia, NTT DOCOMO, vivo], Google |
S2-2502131 | KI#4-Way Forward Discussion for encrypted multiplexed media flows | |
S2-2502148 | Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit NG-RAN indication | [CATT,] Nokia [, Tencent, vivo, Samsung, Xiaomi] |
S2-2502149 | Indication of PDU Set QoS in Notification Control | Nokia |
S2-2502150 | Discussion of PDU Set QoS notification control | Nokia |
S2-2502151 | Procedures updates on DL PDU set information marking without (AF-provided) PDU set QoS params | Nokia |
S2-2502152 | Support AL-FEC awareness at NG-RAN | Nokia, Qualcomm Incorporated, InterDigital Inc. |
S2-2502153 | Support AL-FEC awareness at NG-RAN 23503 | Nokia, Qualcomm Incorporated, InterDigital Inc. |
S2-2502154 | [DRAFT] LS Reply on AL-FEC awareness at RAN | Nokia |
S2-2502155 | Correction on PDU set based DSCP marking | Nokia |
S2-2502156 | PCF enhancements to support multi-modal Service ID awareness at RAN | Nokia |
S2-2502159 | Discussion on Addressing the EN: KI#4 parameters processing for end-to-end ciphered XRM flows | China Mobile |
S2-2502160 | KI#2-KI#4: Resolve the ki2-ki4 integration EN | China Mobile |
S2-2502162 | KI#2-Ki4: Handling the ciphered (S)RTP Multiplexed Media Identification Information | [OPPO, Xiaomi, Lenovo, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, vivo, Google], China Mobile |
S2-2502203 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson, Nokia, Xiaomi, CMCC, Huawei |
S2-2502204 | Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, ZTE, Qualcomm?, Ericsson?, Huawei?, Nokia |
S2-2502205 | [DRAFT] Reply to LS on multi-modality awareness | China Mobile |
S2-2502206 | Procedures for handling end-to-end encrypted XRM flows | [Google, Futurewei, InterDigital Inc.,] China Mobile, [Huawei, HiSilicon, Ericsson, Nokia, Apple ] |
S2-2502207 | PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson [, InterDigital] Nokia, Google, Huawei, HiSilicon] |
S2-2502208 | KI#1, Support the PDU Set Information Marking Support Indication | Vivo, Nokia |
S2-2502209 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung;Nokia |
S2-2502210 | Support multiplexing media traffic with additional Packet Filter | CATT, Nokia, OPPO, Lenovo, Samsung, Xiaomi |
S2-2502211 | Traffic detection and QoS handling of multiplexed data flows | OPPO, China Mobile, Lenovo, Xiaomi, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, Google, [vivo] |
S2-2502212 | Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO, [vivo], Ericsson |
S2-2502213 | KI#9, Support of Available Data Rate | vivo, CATT |
S2-2502214 | KI#9, Support of Available Data Rate | Nokia |
S2-2502215 | Support of available data rate exposure | Huawei, HiSilicon |
S2-2502216 | Corrections for 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, China Telecom, InterDigital [CATT, , Meta USA, CMCC, Xiaomi, Samsung, Huawei, HiSilicon, Ericsson, Nokia, Apple] |
S2-2502217 | Enhancements for AF/AS triggered expedite data transfer | [Nokia, InterDigital Inc.] Lenovo, Tencent, Tencent Cloud |
S2-2502218 | KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson, Samsung |
S2-2502219 | KI#9, Support of Rate limitation | Vivo, [Meta USA], Tencent, [Nokia] |
S2-2502220 | Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi, Huawei, HiSilicon |
S2-2502276 | Support of multi-modal awareness at NG-RAN | China Telecom |
S2-2502277 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson, Nokia, Xiaomi, CMCC, Huawei, Interdigital |
S2-2502278 | Support of multi-modal awareness at NG-RAN | China Telecom |
S2-2502279 | Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, ZTE, Qualcomm, Ericsson, Huawei, Nokia, MediaTek, Xiaomi, CATT, Samsung |
S2-2502280 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsungj, Nokia, Lenovo |
S2-2502281 | KI#1, Support the PDU Set Information Marking Support Indication | vivo |
S2-2502282 | KI#1, Support the PDU Set Information Marking Support Indication | vivo, Nokia |
S2-2502283 | Traffic detection and QoS handling of multiplexed data flows | OPPO, China Mobile, Lenovo, Xiaomi, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, Google, [vivo],Tencent |
S2-2502284 | KI#9, Support of Available Data Rate | vivo, CATT, Tencent, Lenovo, InterDigital, Nokia, Huawei |
S2-2502429 | Support of available data rate exposure | Huawei, HiSilicon |
S2-2502430 | Support for PDU Set Content Ratio | LG Electronics, Ofinno? |
S2-2502431 | Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO, vivo, Ericsson |
S2-2502432 | Corrections for 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, China Telecom, InterDigital, Nokia, Apple, Samsung [CATT, Meta USA, CMCC, Xiaomi, Huawei, HiSilicon, Ericsson] |
S2-2502433 | Enhancements for AF/AS triggered expedite data transfer | [InterDigital Inc.] Lenovo, Tencent, Tencent Cloud, CATT, Nokia, |
S2-2502461 | Procedures for handling end-to-end encrypted XRM flows | Google, Futurewei, InterDigital Inc., China Mobile, Huawei, HiSilicon, Ericsson, Nokia, Apple |
S2-2502462 | PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson, InterDigital, Nokia, [Google, Huawei, HiSilicon] |
S2-2502463 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson, Nokia, Xiaomi, CMCC, Huawei, Interdigital, CATT, China Telecom, Futurewei, Samsung, Sony |
S2-2502464 | Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, ZTE, Qualcomm, Ericsson, Huawei, Nokia, MediaTek, Xiaomi, CATT, Samsung, Futurewei, Lenovo, tencent, OPPO, vivo |
S2-2502465 | LS reply on multi-modality awareness | SA WG2 |
S2-2502466 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung, Nokia, Lenovo |
S2-2502467 | KI#1, Support the PDU Set Information Marking Support Indication | vivo, Nokia |
S2-2502468 | KI#1, Support the PDU Set Information Marking Support Indication | vivo |
S2-2502469 | Traffic detection and QoS handling of multiplexed data flows | OPPO, China Mobile, Lenovo, Xiaomi, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, Google, [vivo],Tencent |
S2-2502470 | KI#9, Support of Available Data Rate | vivo, CATT, Tencent, Lenovo, InterDigital, Nokia, Huawei |
S2-2502471 | Support of available data rate exposure | Huawei, HiSilicon |
S2-2502472 | Corrections for 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, China Telecom, InterDigital, Nokia, Apple, Samsung, CATT, Meta USA, CMCC, Xiaomi, Huawei, HiSilicon, Ericsson |
S2-2502473 | Enhancements for AF/AS triggered expedite data transfer | Lenovo, Tencent, Tencent Cloud, CATT, Huawei, HiSilicon, Nokia, Ericsson, InterDigital Inc |
S2-2502474 | KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson, Samsung, Huawei |
S2-2502475 | KI#9, Support of Rate limitation | Vivo, Meta USA, Tencent, Nokia, Huawei |
S2-2502476 | Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi, Huawei, HiSilicon |
S2-2502477 | Support Alternative QoS profile with PDU Set QoS and Notification Control | [CATT,] Nokia [, Tencent, vivo, Samsung, Xiaomi] |
S2-2502498 | Support of multi-modal awareness at NG-RAN | China Telecom, Nokia, CATT, vivo, Lenovo |
S2-2502672 | KI#1, Support the PDU Set Information Marking Support Indication | Vivo, Nokia, Huawei, Samsung, Lenovo |
S2-2502673 | Support PDU Set based handling without DL PDU Set QoS parameters | Samsung, Nokia, Lenovo, Huawei |
S2-2502674 | Traffic detection and QoS handling of multiplexed data flows | OPPO, China Mobile, Lenovo, Xiaomi, Ericsson, Huawei, HiSilicon, Samsung, Nokia, NTT DOCOMO, Google, vivo, Tencent, CATT |
S2-2502675 | KI#9, Support of Available Data Rate | Vivo, CATT, Tencent, Lenovo, InterDigital, Nokia, Huawei |
S2-2502676 | KI#9, Support of Available Data Rate | Nokia |
S2-2502677 | KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson, Samsung, Huawei, CATT |
S2-2502678 | Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi, Huawei, HiSilicon |
S2-2502683 | PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson, InterDigital, Nokia, Google, Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S2-2501457 | Discussion on Energy Saving Indicator. | Nokia, Deutsche Telekom |
S2-2501458 | Resolution of editor's note on whether the Energy Saving indicator is one value or multiple values. | Nokia, Deutsche Telekom |
S2-2501466 | Resolution of editor's note on PCF taking EIF information into account | Nokia, ZTE, Deutsche Telekom, Qualcomm Inc, Ericsson, |
S2-2501467 | Update of the Energy consumption calculation formulae | Nokia |
S2-2501507 | Policy control with energy saving consideration. | [Vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom, CATT], Samsung |
S2-2501511 | Update for Nudm service operation consumer | China Mobile |
S2-2501512 | Clarification regarding energy collection and exposure | [Huawei, HiSilicon, ETRI], China Mobile, |
S2-2501540 | Resolving EN for the multiple values of Energy Saving indicator | Samsung |
S2-2501542 | Resolving EN on the Energy Saving indicator in UDR | Samsung |
S2-2501548 | Correction on Energy Saving indicator | Samsung |
S2-2501549 | Policy control with energy saving consideration. | [Vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom, CATT], Samsung |
S2-2501550 | Energy saving subscription and AM policy. | [Vivo, Qualcomm Incorporated, ZTE, Deutsche Telekom, CATT], Samsung |
S2-2501551 | Energy Saving indicator | [Ericsson, AT&T, Deutsche Telekom, NEC], Samsung |
S2-2501556 | Discussion on Energy Saving Indicator | Huawei |
S2-2501557 | Energy saving indicator | Huawei, HiSilicon |
S2-2501558 | Policy control with energy saving consideration | [vivo], [Qualcomm Incorporated], [MediaTek Inc], [ZTE], [Deutsche Telekom], [CATT], [Samsung], Huawei, Hisilicon |
S2-2501559 | Energy saving subscription and AM policy. | [vivo], [Qualcomm Incorporated], [ZTE], [Deutsche Telekom], [CATT], [Samsung], Huawei, Hisilicon |
S2-2501560 | Energy Saving indicator | [Ericsson], [AT&T], [Deutsche Telekom], [NEC], [Samsung]. Huawei |
S2-2501561 | Discussion on event reporting | Huawei |
S2-2501562 | Clarification regarding energy collection and exposure | Huawei, HiSilicon, [ETRI] |
S2-2501563 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
S2-2501564 | Clarification regarding energy collection and exposure | Huawei, HiSilicon |
S2-2501565 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
S2-2501566 | Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon [, NTT DOCOMO] |
S2-2501581 | Support for S-NSSAI granularity energy consumption exposure | NEC |
S2-2501582 | Support for S-NSSAI granularity energy consumption exposure | NEC |
S2-2501583 | Energy Saving indicator | NEC [Ericsson, AT&T, Deutsche Telekom, NEC, Samsung] |
S2-2501584 | Energy saving subscription and AM policy. | NEC [Vivo, Qualcomm Incorporated, ZTE, Deutsche Telekom, CATT, Samsung] |
S2-2501603 | Energy Saving indicator | NEC |
S2-2501605 | Energy Attribution sensitivity and robustness | Ericsson |
S2-2501606 | Energy Saving Indicator | Ericsson, AT&T, Deutsche Telekom, [NEC,] Samsung |
S2-2501690 | Policy control with energy saving consideration | Vivo, [Qualcomm Incorporated], MediaTek Inc, [ZTE, Deutsche Telekom, CATT, Samsung] |
S2-2501691 | Architecture and interface update with EIF | vivo |
S2-2501712 | An update to Suspicion of DDoS attack | Verizon |
S2-2501713 | Update on EIF services to solve the Editor's notes | vivo, MediaTek Inc. |
S2-2501714 | Clarification regarding energy collection and exposure | [Huawei, HiSilicon, ETRI], vivo |
S2-2501715 | Energy Saving indicator | [Ericsson, AT&T, Deutsche Telekom, NEC, Samsung], vivo |
S2-2501716 | Update on SMF services | vivo |
S2-2501717 | Update on energy consumption information collection and exposure to solve the Editor's notes | vivo |
S2-2501718 | Update on subscription information and policy control aspects | vivo |
S2-2501719 | Energy Saving indicator | [Ericsson, AT&T, Deutsche Telekom, NEC, Samsung] China Mobile |
S2-2501720 | Update for BDT based on network energy related information | China Mobile |
S2-2501721 | Update for BDT based on network energy related information | China Mobile |
S2-2501730 | Clarification regarding energy collection and exposure | ETRI, CATT |
S2-2501753 | Clarification regarding energy collection and exposure | [Huawei, HiSilicon], ETRI, CATT |
S2-2501774 | Enhancement for BDT with Energy related information | KDDI |
S2-2501775 | Resolving ENs in Clause 5.51.5 and 5.51.6 | MediaTek Inc., vivo, CATT |
S2-2501825 | Clarification on support of Energy Efficiency and Energy Saving | CATT, ETRI |
S2-2501826 | Data collection for energy information calculation and exposure | CATT, ETRI |
S2-2501828 | Energy related subscription data and policy control | CATT |
S2-2501830 | Policy control with energy saving consideration. | [vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom,] CATT, [Samsung] |
S2-2501833 | Update for BDT based on network energy related information | China Mobile |
S2-2501838 | Clean up the architecture and interface for energysys | Qualcomm Incorporated, Nokia, Ericsson |
S2-2501895 | Discussion on QoS Flow vs. Service Data Flow granularity | Huawei |
S2-2501957 | Energy Saving indicator for UE Policy | Samsung |
S2-2501997 | Resolving editor's note on the interface between EIF and OAM | NTT DOCOMO |
S2-2501998 | Updating EIF service operations | NTT DOCOMO[, Deutsche Telekom, Vivo, China Mobile] |
S2-2502000 | Resolving Roaming editor's note in the architecture | NTT DOCOMO |
S2-2502001 | Negotiation for future background data transfer considering energy | NTT DOCOMO |
S2-2502002 | Corrections for energy saving related AF input on BDT policy negotiation | [Huawei, HiSilicon,] NTT DOCOMO |
S2-2502022 | Energy-Efficient User Plane for 6G Core Service-Based Architecture Leveraging Nndwaf_MLModelProvision Service | IIT, Kharagpur |
S2-2502042 | Adding per UE per Application level Energy consumption exposure | ZTE, China Mobile, NTT DOCOMO, Vivo |
S2-2502043 | Adding per UE per Application level Energy consumption exposure filter | ZTE |
S2-2502044 | Clarification on the BDT based on network energy related information | ZTE |
S2-2502045 | Adding Energy indication to BDT procedure and service operation | ZTE |
S2-2502046 | Clarification on the BDT policy decision | ZTE |
S2-2502047 | Resolving the ENs about the Energy Consumption information exposure | ZTE |
S2-2502048 | Resolving the EN on the UE Energy saving Subscription | ZTE |
S2-2502049 | Energy saving indicator to RAN in mobility | ZTE |
S2-2502050 | Correcting the input and output of SMF exposure for Energy data collection | ZTE |
S2-2502051 | Resolve the EN in the architecture clause | ZTE |
S2-2502127 | Update on the BDT procedures | vivo |
S2-2502161 | BDT Energy Negotiation Procedures | Motorola Mobility UK Ltd., Lenovo |
S2-2502164 | Energy Enhacements on BDT Policy Control Services | Motorola Mobility UK Ltd., Lenovo |
S2-2502165 | Energy Saving indicator | [Ericsson, AT&T, Deutsche Telekom, NEC, Samsung], Lenovo |
S2-2502169 | Clean-up on the policy control | Lenovo |
S2-2502306 | Energy Saving Indicator | Ericsson, AT&T, Deutsche Telekom, NEC, Samsung, China Mobile, Toyota |
S2-2502307 | Resolution of editor’s note on whether the Energy Saving indicator is one value or multiple values. | Nokia, Deutsche Telekom, NTT Docomo, Verizon |
S2-2502308 | Energy saving indicator to RAN in mobility | ZTE |
S2-2502309 | Resolution of editor's note on PCF taking EIF information into account | Nokia, ZTE, Deutsche Telekom, Qualcomm Inc, Ericsson, Lenovo |
S2-2502310 | Corrections for energy saving related AF input on BDT policy negotiation | [Huawei, HiSilicon,] NTT DOCOMO |
S2-2502311 | Update for BDT based on network energy related information | China Mobile |
S2-2502312 | Clarification on the BDT based on network energy related information | ZTE |
S2-2502313 | Enhancement for BDT with Energy related information | KDDI, NTT DOCOMO, ZTE, China Mobile, vivo, Motorola Mobility UK Ltd., Lenovo, TOYOTA MOTOR CORPORATION |
S2-2502314 | Energy Enhacements on BDT Policy Control Services | Motorola Mobility UK Ltd., Lenovo |
S2-2502315 | Policy control with energy saving consideration. | Vivo, [Qualcomm Incorporated], MediaTek Inc, [ZTE, Deutsche Telekom, CATT, Samsung] |
S2-2502316 | Update of the Energy consumption calculation formulae | Nokia, Huawei, HiSilicon, Vivo |
S2-2502317 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
S2-2502355 | Adding per UE per Application level Energy consumption exposure | ZTE, China Mobile, NTT DOCOMO, Vivo, NEC, Huawei,? HiSilicon? |
S2-2502356 | Clarification regarding energy collection and exposure | [Huawei, HiSilicon, ETRI], China Mobile, |
S2-2502357 | Update on energy consumption information collection and exposure to solve the Editor's notes | vivo, ZTE? |
S2-2502358 | Update on EIF services to solve the Editor's notes | vivo, MediaTek Inc. |
S2-2502359 | Adding per UE per Application level Energy consumption exposure filter | ZTE |
S2-2502360 | Support for S-NSSAI granularity energy consumption exposure | NEC |
S2-2502361 | Support for S-NSSAI granularity energy consumption exposure | NEC |
S2-2502362 | Resolve the EN in the architecture clause | ZTE |
S2-2502363 | Clean up the architecture and interface for energysys | Qualcomm Incorporated, Nokia, Ericsson |
S2-2502371 | Resolution of editor s note on whether the Energy Saving indicator is one value or multiple values. | Nokia, Deutsche Telekom, NTT Docomo, Verizon, Ericsson |
S2-2502372 | Energy Saving Indicator | Ericsson, AT&T, Deutsche Telekom, NEC, Samsung, China Mobile, Toyota, Vivo |
S2-2502373 | Resolution of editor's note on PCF taking EIF information into account | Nokia, ZTE, Deutsche Telekom, Qualcomm Inc, Ericsson, Lenovo |
S2-2502374 | Policy control with energy saving consideration. | Vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom, CATT, Samsung |
S2-2502375 | Resolve the EN in the architecture clause | ZTE, NTT DOCOMO, China Mobile |
S2-2502376 | Update of the Energy consumption calculation formulae | Nokia, Huawei, HiSilicon, Vivo |
S2-2502377 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon, ETRI, Vivo, CMCC, ZTE |
S2-2502378 | Update on energy consumption information collection and exposure to solve the Editor's notes | vivo, ZTE |
S2-2502379 | Clarification regarding energy collection and exposure | [Huawei, HiSilicon, ETRI], China Mobile, |
S2-2502380 | Adding per UE per Application level Energy consumption exposure | ZTE, China Mobile, NTT DOCOMO, Vivo, NEC, Huawei, HiSilicon |
S2-2502381 | Adding per UE per Application level Energy consumption exposure filter | ZTE, NEC |
S2-2502382 | Support for S-NSSAI granularity energy consumption exposure | NEC, Samsung |
S2-2502554 | Update on EIF services to solve the Editor's notes | vivo, MediaTek Inc. |
S2-2502567 | Clarification regarding energy collection and exposure | Huawei, HiSilicon, ETRI, China Mobile, vivo |
S2-2502568 | Policy control with energy saving consideration. | Vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom, CATT, Samsung |
S2-2502569 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon, ETRI, Vivo, CMCC, ZTE, Samsung, NEC |
S2-2502570 | Update on energy consumption information collection and exposure to solve the Editor's notes | Vivo, ZTE, Samsung |
S2-2502571 | Update on EIF services to solve the Editor's notes | vivo, MediaTek Inc. |
S2-2502572 | Adding per UE per Application level Energy consumption exposure | ZTE, China Mobile, NTT DOCOMO, Vivo, NEC, Huawei, HiSilicon, CATT |
S2-2502573 | Resolve the EN in the architecture clause | ZTE, NTT DOCOMO, China Mobile, Huawei, HiSilicon, Nokia |
S2-2502574 | Update on EIF services to solve the Editor's notes | vivo, MediaTek Inc. |
S2-2502575 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon, ETRI, Vivo, CMCC, ZTE, Samsung, NEC, CATT |
S2-2502782 | Adding per UE per Application level Energy consumption exposure | ZTE, China Mobile, NTT DOCOMO, Vivo, NEC, Huawei, HiSilicon, CATT |
S2-2502783 | Adding per UE per Application level Energy consumption exposure filter | ZTE, NEC |
TDoc | Title | Source |
---|---|---|
S2-2501417 | Clarification of location services when a UE is served by a MWAB-gNB | Nokia |
S2-2501418 | Clarification of regulatory services support | Nokia |
S2-2501419 | Clarification of mobility clause | Nokia |
S2-2501420 | Clarification of the network slicing clause | Nokia |
S2-2501421 | Clarification of QoS Clause | Nokia |
S2-2501422 | Solve the Editor s Note related to the Additional ULI | [CATT, Ericsson] Nokia, Vodafone |
S2-2501448 | Discussion on the Additional ULI | Nokia, Vodafone |
S2-2501594 | [DRAFT] LS on MWAB-UE handover control | Ericsson |
S2-2501595 | MWAB-UE HO considering preventable multiple-hop | Ericsson, Huawei, HiSilicon, Samsung |
S2-2501596 | MWAB configuration and Additional ULI Clarification | Ericsson, Samsung, Huawei, HiSilicon |
S2-2501597 | PWS handling with Additional ULI | Ericsson, Qualcomm Incorporated |
S2-2501598 | PWS handling update for VMR | Ericsson, Qualcomm Incorporated |
S2-2501631 | Corrections to remove EN on QoS handling for Xn interface over BH PDU session | Qualcomm Incorporated |
S2-2501653 | MWAB configuration and Additional ULI Clarification | [Ericsson, Samsung], CATT |
S2-2501654 | Update the handover procedure | CATT |
S2-2501655 | Update location procedure involving MWAB | CATT |
S2-2501656 | Update the support of regulatory service | CATT |
S2-2501692 | Clarification on MWAB mobility | LG Electronics |
S2-2501693 | Clarification on N2 connection setup | LG Electronics |
S2-2501694 | Clarification on MWAB-UE aspect | LG Electronics |
S2-2501850 | Correction on shifting N3 traffic to the new BH PDU sessions | China Telecom |
S2-2501868 | Determination of UE served by a MWAB cell | Huawei, HiSilicon |
S2-2501869 | Correction of TS 23.273 for MWAB | Huawei, HiSilicon |
S2-2501870 | Backhaul PDU Session handling for MWAB | Huawei, HiSilicon |
S2-2501871 | MWAB-UE authorization | Huawei, HiSilicon |
S2-2502052 | Clarification on the location service when the MWAB is involved | ZTE |
S2-2502053 | Discussion on the HO for prevent multi-hop MWAB | ZTE |
S2-2502054 | Clarification on the S-NSSAI for BH PDU session | ZTE |
S2-2502055 | MWAB configuration and Additional ULI Clarification | [Ericsson, Samsung], ZTE |
S2-2502056 | Clarification on HO procedure | ZTE |
S2-2502416 | Solve the Editor s Note related to the Additional ULI | [CATT, Ericsson] Nokia, Vodafone |
S2-2502417 | Determination of UE served by a MWAB cell | Huawei, HiSilicon |
S2-2502418 | Clarification of mobility clause | Nokia |
S2-2502419 | Clarification on MWAB mobility | LG Electronics |
S2-2502420 | Corrections to remove EN on QoS handling for Xn interface over BH PDU session | Qualcomm Incorporated, Nokia |
S2-2502421 | Clarification of regulatory services support | Nokia |
S2-2502422 | Clarification of location services when a UE is served by a MWAB-gNB | Nokia |
S2-2502648 | MWAB configuration and Additional ULI Clarification | Ericsson, Samsung, Huawei, HiSilicon, ZTE, Nokia, LG Electronics |
S2-2502663 | Solve the Editor s Note related to the Additional ULI | [CATT, Ericsson] Nokia, Vodafone |
S2-2502664 | Determination of UE served by a MWAB cell | Huawei, HiSilicon, Ericsson |
S2-2502665 | MWAB configuration and Additional ULI Clarification | Ericsson, Samsung, Huawei, HiSilicon, ZTE, Nokia, LG Electronics, CATT |
S2-2502666 | Clarification of regulatory services support | Nokia |
S2-2502667 | Clarification of location services when a UE is served by a MWAB-gNB | Nokia, CATT |
TDoc | Title | Source |
---|---|---|
S2-2501554 | Clarification on CAG information provisioning | Huawei, HiSilicon |
S2-2501741 | Term alignment and roaming clarification | ZTE |
S2-2501742 | Update CAG information provisioning | ZTE |
S2-2501756 | Discussion on NR Femto cell shared by PLMN and PNI-NPN | LG Electronics |
S2-2501757 | [DRAFT] LS on NR Femto cell shared by PLMN and PNI-NPN | LG Electronics |
S2-2501776 | Fix NR Femto architecture description | Samsung |
S2-2501777 | CAG Information Provisioning parameters | Samsung |
S2-2502144 | CAG Information provisioning functionality | Nokia |
S2-2502391 | CAG Information Provisioning parameters | Samsung, ZTE |
S2-2502392 | Term alignment and roaming clarification | ZTE |
S2-2502393 | Fix NR Femto architecture description | Samsung |
S2-2502394 | [DRAFT] LS on NR Femto cell shared by PLMN and PNI-NPN | LG Electronics |
S2-2502633 | Term alignment and roaming clarification | ZTE |
S2-2502634 | [DRAFT] LS on NR Femto cell shared by PLMN and PNI-NPN | LG Electronics |
S2-2502777 | [DRAFT] LS on NR Femto cell shared by PLMN and PNI-NPN | LG Electronics |
S2-2502787 | LS on NR Femto node shared by PLMN and PNI-NPN | SA WG2 |
TDoc | Title | Source |
---|---|---|
S2-2501384 | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 |
S2-2501525 | Conclusion update for KI#1 | vivo |
S2-2501526 | Conclusion update for KI#2 | vivo |
S2-2501527 | Conclusion update for KI#3 | vivo |
S2-2501543 | Topic #3, Conclusions on AIoT KI#1 for aggregation | Samsung |
S2-2501585 | KI#1#3 Conclusion Update of Aggregation | Ericsson |
S2-2501586 | KI#2 Conclusion Update of Subscription Data for AF Authorization | Ericsson |
S2-2501680 | Conclusion update for EN resolution on aggregation | OPPO |
S2-2501696 | Update on BS reader selection in KI#1 | China Mobile |
S2-2501697 | Conclusions for KI#1 on the aggregation aspects | China Mobile |
S2-2501698 | Removing one EN related to format of Part2 of Identification in KI#2 | China Mobile |
S2-2501704 | Conclusions on the KI#1 general part correcting NGAP description. | China Mobile |
S2-2501762 | KI#1 Addressing EN on AIoT service responses aggregation | Lenovo |
S2-2501771 | Resolution of Editor's notes with SA WG3 dependencies | CATT |
S2-2501901 | TR KI#1 conclusion Topic3 aggregation | Nokia |
S2-2501902 | TR KI#3 latency requirement from AF | Nokia |
S2-2501904 | Conclusions for KI#1 on aggregation aspects | NTT DOCOMO |
S2-2501967 | ENs on Ambient IoT Device Temporary ID | Huawei, HiSilicon |
S2-2501968 | Clarifications on aggregation assistance information | Huawei, HiSilicon |
S2-2501969 | Resolve the editor's notes related to security aspect | Huawei, HiSilicon |
S2-2502107 | KI#2: Clarifications for Ambient IoT Device ID | Qualcomm Incorporated |
S2-2502318 | TR KI#1 conclusion Topic3 aggregation | Nokia |
S2-2502319 | Conclusion update for KI#2 | vivo |
S2-2502320 | Resolve the editor's notes related to security aspect | Huawei, HiSilicon |
S2-2502321 | KI#2 Conclusion Update of Subscription Data for AF Authorization | Ericsson |
S2-2502364 | TR KI#1 conclusion Topic3 aggregation | Nokia |
S2-2502365 | Conclusion update for KI#2 | vivo |
S2-2502366 | Resolve the editor's notes related to security aspect | Huawei, HiSilicon |
S2-2502367 | KI#2 Conclusion Update of Subscription Data for AF Authorization | Ericsson |
S2-2502577 | KI#2 Conclusion Update of Subscription Data for AF Authorization | Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2501528 | PCR to TS 23.xyz: AIoT device Identifiers | Vivo, NTT DOCOMO, Deutsche Telekom, T-Mobile USA |
S2-2501529 | PCR to TS 23.xyz: Procedure for inventory | vivo |
S2-2501530 | PCR to TS 23.xyz: Procedure for command | vivo |
S2-2501531 | PCR to TS 23.xyz: NF Services | vivo |
S2-2501532 | PCR to TS 23.xyz: Network Functions | vivo |
S2-2501533 | PCR to TS 23.xyz: Architecture Update | vivo |
S2-2501534 | PCR to TS 23.xyz: Protocol Stacks Update | vivo |
S2-2501682 | PCR to 23.xyz: NF description for AIoT | OPPO |
S2-2501683 | PCR to 23.xyz: Inventory procedure | OPPO |
S2-2501684 | PCR to 23.xyz: Command procedure | OPPO |
S2-2501705 | PCR to 23.xyz: NF description for AIoT | [OPPO], China Mobile |
S2-2501706 | PCR to 23.xyz: Reader selection for Ambient IoT service request | China Mobile |
S2-2501707 | PCR to TS 23.xyz: Network Functions Services | [Huawei, HiSilicon], China Mobile |
S2-2501758 | Ambient IoT Services | InterDigital Inc. |
S2-2501759 | AIoT Reader Selection | InterDigital Inc. |
S2-2501760 | AIoT Device Information Configure Service | InterDigital Inc. |
S2-2501763 | PCR to TS 23.xyz: AIOTF Functionality | Lenovo |
S2-2501764 | PCR to TS 23.xyz: AF authorization to the Ambient IoT Services | Lenovo |
S2-2501765 | PCR to TS 23.xyz: NRF Functionality | Lenovo |
S2-2501766 | PCR to TS 23.xyz: AF and NEF Functionality | Lenovo |
S2-2501767 | PCR to TS 23.xyz: Ambient IoT Services | CATT |
S2-2501768 | PCR to TS 23.xyz: AIoT Reader Selection | CATT |
S2-2501769 | PCR to TS 23.xyz: AF authorization | CATT |
S2-2501770 | PCR to TS 23.xyz: Procedure for Inventory | CATT |
S2-2501849 | Resolving EN about assistance information (Clause 5.4) | LG Electronics |
S2-2501886 | PCR to TS 23.xyz: Functional Entity description for AIoT | Spreadtrum, UNISOC |
S2-2501903 | PCR to TS 23.xyz_KI#1 Topic3 aggregation | Nokia |
S2-2501942 | PCR to TS 23.xyz: AIoT Reader Selection | HONOR |
S2-2501944 | PCR to TS 23.xyz: NEF Services | ZTE |
S2-2501945 | PCR to TS 23.xyz: Clause 4.1 General Concept Clarification | ZTE |
S2-2501946 | PCR to TS 23.xyz: Service Operation Result Aggregation | ZTE |
S2-2501947 | PCR to TS 23.xyz: Procedure for Inventory | ZTE |
S2-2501948 | PCR to TS 23.xyz: ADM Related Reference Point and Interface | ZTE |
S2-2501949 | PCR to TS 23.xyz: AIoT Reader Selection | ZTE |
S2-2501971 | PCR to TS 23.xyz: Profile Management for Ambient IoT Device | Huawei, HiSilicon |
S2-2501972 | PCR to TS 23.xyz: AF Authorization for Ambient IoT Services | Huawei, HiSilicon |
S2-2501973 | PCR to TS 23.xyz: Network Functions Services | Huawei, HiSilicon |
S2-2501974 | PCR for TS 23.xyz: Ambient IoT Device Identifier | Huawei, HiSilicon, Qualcomm? |
S2-2501975 | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service | Huawei, HiSilicon |
S2-2501976 | PCR to TS 23.xyz: Procedure for Ambient IoT Command Service | Huawei, HiSilicon |
S2-2501977 | PCR to TS 23.xyz: Procedures for AIOTF and AIoT Reader Communication | Huawei, HiSilicon |
S2-2501978 | PCR to TS 23.xyz: Updates to Architecture clause | Huawei, HiSilicon |
S2-2501999 | PCR to TS 23.xyz: AIoT Reader selection | Lenovo |
S2-2502080 | Discussion on globally unique Ambient IoT identifier | NTT DOCOMO, Nokia, Deutsche Telekom, Philips International B.V., Ericsson |
S2-2502082 | PCR to TS 23.xyz: Text on permanent Ambient IoT Identifiers | NTT DOCOMO, Nokia, Deutsche Telekom, Philips International B.V., Ericsson |
S2-2502083 | Discussion on assistance information to support command procedure | NTT DOCOMO, Deutsche Telekom, Philips International B.V., Ericsson, KPN N.V. |
S2-2502084 | PCR to TS 23.xyz: Text on assistance information to support command procedure | NTT DOCOMO, KPN N.V., Ericsson, Deutsche Telekom, Philips International B.V. |
S2-2502086 | PCR to TS 23.xyz: Inventory call flow | NTT DOCOMO, Deutsche Telekom, Philips International B.V., KPN N.V. |
S2-2502117 | PCR to TS 23.xyz: Assistance Information used by AIoT RAN | Ofinno |
S2-2502322 | NF description for AIoT. | OPPO |
S2-2502323 | Ambient IoT Services. | InterDigital Inc. |
S2-2502324 | PCR to 23.xyz: Reader selection for Ambient IoT service request. | China Mobile, Spreadtrum, ZTE, CATT |
S2-2502338 | PCR to TS 23.xyz: Profile Management for Ambient IoT Device. | Huawei, HiSilicon, NEC |
S2-2502339 | PCR to TS 23.xyz: AF authorization to the Ambient IoT Services. | Lenovo |
S2-2502340 | PCR to TS 23.xyz: AIoT device Identifiers | Vivo, NTT DOCOMO, Deutsche Telekom, T-Mobile USA |
S2-2502341 | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon |
S2-2502342 | Command procedure. | OPPO |
S2-2502343 | PCR to TS 23.xyz: NF Services | vivo |
S2-2502344 | PCR to TS 23.xyz: NEF Services. | ZTE, vivo |
S2-2502345 | PCR to TS 23.xyz: Updates to Architecture clause. | Huawei, HiSilicon |
S2-2502346 | PCR to TS 23.xyz: Protocol Stacks Update | vivo |
S2-2502347 | Resolving EN about assistance information (Clause 5.4). | LG Electronics |
S2-2502368 | NF description for AIoT. | OPPO, Lenovo, Spreadtrum, UNISOC, CATT, China Mobile |
S2-2502369 | Ambient IoT Services. | InterDigital Inc. |
S2-2502370 | PCR to 23.xyz: Reader selection for Ambient IoT service request. | China Mobile, Spreadtrum, ZTE, CATT, InterDigital |
S2-2502551 | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon |
S2-2502552 | PCR to TS 23.xyz: Updates to Architecture clause. | Huawei, HiSilicon |
S2-2502555 | PCR to TS 23.xyz: Profile Management for Ambient IoT Device. | Huawei, HiSilicon, NEC |
S2-2502556 | PCR to TS 23.xyz: AF authorization to the Ambient IoT Services. | Lenovo, Huawei, HiSilicon, CATT, Ericsson |
S2-2502557 | PCR to TS 23.xyz: AIoT device Identifiers | Vivo, NTT DOCOMO, Deutsche Telekom, T-Mobile USA |
S2-2502558 | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon, CATT, OPPO |
S2-2502559 | Command procedure. | OPPO, CATT |
S2-2502560 | PCR to TS 23.xyz: NF Services | vivo |
S2-2502561 | PCR to TS 23.xyz: NEF Services. | ZTE, vivo |
S2-2502562 | Resolving EN about assistance information (Clause 5.4). | LG Electronics |
S2-2502563 | PCR to TS 23.xyz: Protocol Stacks Update | vivo |
S2-2502564 | PCR to TS 23.xyz: Updates to Architecture clause. | Huawei, HiSilicon |
S2-2502565 | PCR on the aggregation aspects. | Nokia |
S2-2502578 | PCR to TS 23.xyz: AF authorization to the Ambient IoT Services. | Lenovo, Huawei, HiSilicon, CATT, Ericsson |
S2-2502579 | Ambient IoT Services. | InterDigital Inc., Oppo |
S2-2502580 | PCR to 23.xyz: Reader selection for Ambient IoT service request. | China Mobile, Spreadtrum, ZTE, CATT, InterDigital |
S2-2502581 | PCR to TS 23.xyz: AIoT device Identifiers | Vivo, NTT DOCOMO, Deutsche Telekom, T-Mobile USA |
S2-2502582 | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon, CATT, OPPO, Ofinno |
S2-2502583 | Command procedure. | OPPO, CATT |
S2-2502584 | PCR to TS 23.xyz: NF Services | vivo |
S2-2502585 | PCR to TS 23.xyz: NEF Services. | ZTE, vivo |
S2-2502586 | PCR to TS 23.xyz: Protocol Stacks Update | vivo |
S2-2502588 | Command procedure. | OPPO, CATT, Huawei, HiSilicon |
S2-2502589 | PCR to TS 23.xyz: NF Services | vivo |
S2-2502590 | PCR to 23.xyz: Reader selection for Ambient IoT service request. | China Mobile, Spreadtrum, ZTE, CATT, InterDigital |
TDoc | Title | Source |
---|---|---|
S2-2501357 | LS from RAN WG1: Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | RAN WG1 (R1-2405578) |
S2-2501364 | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 |
S2-2501372 | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN |
S2-2501387 | LS from RAN WG2: Reply LS to SA WG2 on LMF-based AI/ML Positioning for Case 2b | RAN WG2 |
S2-2501440 | Clarifications on intermediate training result and intermediate model training information | ZTE |
S2-2501441 | Clarifications on VFL inference | ZTE |
S2-2501442 | General maintenance of KI#1 | ZTE |
S2-2501443 | General maintenance of KI#4 | ZTE |
S2-2501447 | VFL high level description refinements | ZTE |
S2-2501449 | EN removal for clarification of VFL high level description | KDDI, LG Electronics |
S2-2501450 | KI#1 AMF exposing RAN overload to LMF | Nokia |
S2-2501451 | Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung [Nokia, Apple, ZTE, Lenovo, OPPO] |
S2-2501452 | Discussion on supporting VFL model training with client intermediate results sharing between VFL clients | Samsung |
S2-2501453 | KI#1: Resolving open issues for LMF data exposure | Nokia |
S2-2501454 | Updates to AI/ML-based positioning general descriptions | Apple, [CATT] |
S2-2501455 | Updates to AI/ML-based positioning procedures | Apple, [vivo] |
S2-2501456 | Updates to user consent description | Apple |
S2-2501460 | User consent purpose for AI/ML-based positioning | Apple |
S2-2501476 | KI#1: Considering RAN load when collecting data to train model for positioning | Nokia |
S2-2501477 | Triggering VFL model training | Nokia |
S2-2501478 | Updates to VFL Training – possible compromise | [Ericsson, Lenovo, InterDigital, OPPO,] Nokia |
S2-2501479 | Updates to VFL Training - no new training triggers | [Ericsson, Lenovo, InterDigital, OPPO], Nokia |
S2-2501480 | User consent for model training | Ericsson, AT&T |
S2-2501481 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor´s Note. | Ericsson, AT&T |
S2-2501482 | Updates to AI/ML-based positioning procedures | [Apple, vivo] Ericsson, AT&T |
S2-2501483 | Resolving ENs for VFL including triggering of Training | Ericsson |
S2-2501484 | Resolving ENs for VFL | Ericsson, OPPO, [Lenovo, InterDigital, Nokia, KDDI] |
S2-2501485 | KI#2: VFL services | [Nokia,] Ericsson |
S2-2501486 | Procedure to collect input data for ML Model training at NWDAF | Ericsson |
S2-2501487 | Parameters for VFL inference | Nokia |
S2-2501488 | Resolve some ENs in the vertical federated learning inference procedure | [OPPO,] Nokia [, Ericsson, Samsung] |
S2-2501489 | VFL services | Nokia |
S2-2501490 | KI#2: VFL services | Nokia[, Ericsson] |
S2-2501491 | KI#2: Model training service is not applicable for VFL | Nokia |
S2-2501492 | EN Resolution and Further Corrections on QoS and policy assistance analytics | Nokia, [Samsung, Ericsson, Verizon, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon, ETRI]? |
S2-2501493 | KI#4 Resolve open issues for mitigation actions | Nokia |
S2-2501494 | KI#4: Input data to be collected from PCF have been defined | Nokia |
S2-2501499 | KI#2: VFL services | Nokia |
S2-2501544 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | [Ericsson,] Apple |
S2-2501546 | Addressing EN in VFL training | Tejas Networks |
S2-2501547 | Triggering VFL training - Way Forwards | Lenovo |
S2-2501552 | Correction on usage of signalling storm analytics for reliability of NF services | Huawei, HiSilicon |
S2-2501553 | Clarifying Signalling Storm Analytics | Huawei, HiSilicon, [China Telecom], SK Telecom, [Verizon, NTT DOCOMO] |
S2-2501573 | Sample update during VFL training | Apple, [Ericsson,] Samsung, ETRI, Futurewei |
S2-2501630 | Sample ID intersection when untrusted AF acting as VFL server | Samsung [Nokia] |
S2-2501638 | Modifications on ML Model retrieval service | [ZTE], Intel |
S2-2501639 | Updates to AI/ML-based positioning general descriptions | [Apple], [CATT],Intel |
S2-2501640 | Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | [CATT], [ ZTE], Intel |
S2-2501646 | Resolve some ENs in the vertical federated learning inference procedure | OPPO, [Nokia, Ericsson, Samsung] |
S2-2501647 | KI#2: VFL services | [Nokia, Ericsson], OPPO |
S2-2501648 | Modifications on ML Model retrieval service | ZTE |
S2-2501669 | Clarification on number of UEs for data collection and data source type | vivo |
S2-2501670 | NWDAF registration and discovery for AI positioning | vivo |
S2-2501671 | Updates to AI/ML-based positioning general descriptions | [Apple, CATT], vivo |
S2-2501672 | Clarification on data collection by LMF for LMF-based AIML Positioning | [CATT], vivo |
S2-2501673 | Interaction between consumer and VFL server for VFL inference | vivo |
S2-2501674 | NEF work during VFL preparation procedure | vivo |
S2-2501675 | Enhancements for the accuracy monitoring of VFL training | vivo |
S2-2501676 | Adding VFL related services supported by NEF and AF | Vivo, [Nokia, KDDI] |
S2-2501677 | Update on the contents of VFL related services | vivo |
S2-2501678 | KI#2 - update to registration and discovery procedure | [InterDigital, Nokia, KDDI, OPPO, LGE, Ericsson, Samsung], vivo |
S2-2501679 | Resolving ENs for VFL | [Ericsson, Lenovo, InterDigital, OPPO, Nokia], vivo |
S2-2501699 | Clarify the output of QoS and Policy Assistance Analytics in 23.288 | China Mobile |
S2-2501700 | Adding new LMF Selection Factor | China Mobile |
S2-2501701 | Clarification on the description of VFL Server and VFL Client | China Mobile |
S2-2501702 | Clarification on LMF as service consumer for ML Model Training | China Mobile |
S2-2501703 | NF discovery for signaling data collection related to signaling storm analytics | China Mobile |
S2-2501709 | Editorial improvement on QoS and policy assistance analytics | [Samsung, Ericsson, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon, ETRI] Verizon |
S2-2501761 | CR for 23.501 AIML_CN SCP related alignment | Vivo |
S2-2501782 | KI#2: VFL services | [Nokia, Ericsson], LG Electronics |
S2-2501823 | Clarification on data collection by LMF from NG-RAN for LMF-based AIML Positioning | CATT |
S2-2501824 | Clarification on model performance monitoring for LMF-based AIML Positioning | CATT, vivo, Intel |
S2-2501829 | KI#4: Minor Clarifications and Corrections | ETRI |
S2-2501834 | Clarification on data collection from PRU | Xiaomi |
S2-2501835 | UE LCS privacy check for ground truth data collection | Qualcomm Incorporated |
S2-2501836 | UE LCS privacy check for ground truth data collection | Qualcomm Incorporated |
S2-2501837 | [DRAFT] Reply LS on Signalling feasibility of data set and parameter sharing | Qualcomm Germany |
S2-2501848 | Corrections on QoS and policy assistance analytics | [Samsung, Ericsson, Verizon, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon, ETRI,] CATT |
S2-2501855 | Updates of input data collection from LMF | Huawei, HiSilicon, ZTE, [Apple,] China Telecom |
S2-2501856 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | [Ericsson], Huawei, HiSilicon |
S2-2501857 | Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | [CATT, ZTE], Huawei, HiSilicon |
S2-2501858 | Updates of ML model provisioning services for LMF-based AI/ML Positioning | Huawei, HiSilicon |
S2-2501863 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | [Ericsson], Samsung |
S2-2501880 | Corrections on QoS and policy assistance analytics | [Samsung, Ericsson, Verizon, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon] ETRI |
S2-2501882 | User consent check during performance monitoring | Samsung |
S2-2501894 | User consent check during performance monitoring | Samsung |
S2-2501936 | Resolving ENs for VFL | [Ericsson], Lenovo, [InterDigital, OPPO, Nokia] |
S2-2501939 | Resolve some ENs in the vertical federated learning inference procedure | [OPPO], [Nokia], [Ericsson], [Samsung], Lenovo |
S2-2501943 | KI#1 - Further clarification on ML Model performance monitoring for AI/ML positioning | Lenovo, CATT |
S2-2501955 | KI#1 - Further clarification on input data for ML model training for AI/ML positioning | Lenovo |
S2-2501984 | Proposals of VFL training trigger with possible compromise | ZTE |
S2-2501993 | Discussion on SMF events of QoS Flow | NTT DOCOMO |
S2-2501994 | QFI Change event | NTT DOCOMO, CATT, Nokia, Samsung |
S2-2501995 | Exposure of control plane signalling information from NFs | NTT DOCOMO |
S2-2501996 | Correction of NF Signalling Information for Signalling Storm Analytics | NTT DOCOMO |
S2-2502007 | Update UDM to support user consent of data collection for performance monitoring | Xiaomi |
S2-2502008 | Clarification on privacy check for data collection | Xiaomi |
S2-2502017 | Updates on input data of AI/ML positioning model performance monitoring | China Telecom |
S2-2502019 | Resolve some ENs in the vertical federated learning inference procedure | [OPPO, Nokia, Ericsson, Samsung], China Telecom |
S2-2502020 | Remove misleading content and update consumers in Signalling Storm Analytics | China Telecom |
S2-2502021 | Update event exposure service of PCF | China Telecom |
S2-2502033 | VFL Accuracy Monitoring | Huawei, HiSilicon |
S2-2502034 | KI#2 - update to VFL preparation procedure | [InterDigital, Nokia, Ericsson, Futurewei, LGE], Huawei, HiSilicon, ZTE, OPPO |
S2-2502035 | Discussion on the update of S2-2501134 | Huawei, HiSilicon |
S2-2502036 | Resolve some ENs in the vertical federated learning inference procedure | [OPPO, Nokia, Ericsson, Samsung], Huawei, HiSilicon |
S2-2502041 | Adding VFL related services supported by NEF and AF | [Vivo, Nokia, KDDI], Huawei, HiSilicon |
S2-2502059 | Updates on VFL training and VFL inference to remove ENs | China Telecom, [ZTE, Lenovo, Nokia, ETRI] |
S2-2502098 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | [Ericsson], Xiaomi |
S2-2502104 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | [Ericsson,] Nokia |
S2-2502105 | KI#2 - update to registration and discovery procedure | [InterDigital, Nokia, KDDI, OPPO, LGE,] Ericsson [, Samsung] |
S2-2502106 | KI#2 - update to VFL preparation procedure | [InterDigital, Nokia,] Ericsson [, Futurewei, LGE] |
S2-2502132 | Updates to AI/ML-based positioning procedures | InterDigtial, [Apple, vivo] |
S2-2502133 | KI#2 update to VFL preparation procedure | InterDigital, [Nokia], [Ericsson], [Futurewei], [LGE] |
S2-2502141 | KI#2 - update to VFL inference procedure | InterDigital |
S2-2502142 | Resolving ENs for VFL | [Ericsson], [Lenovo], InterDigital, [OPPO], [Nokia] |
S2-2502174 | User consent for model training | Ericsson, AT&T |
S2-2502221 | Adding new LMF Selection Factor | China Mobile, ZTE, ETRI, Interdigital |
S2-2502222 | Clarification on model performance monitoring for LMF-based AIML Positioning | CATT, vivo, Intel |
S2-2502223 | Updates to AI/ML-based positioning general descriptions | Apple, [CATT] |
S2-2502224 | Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | CATT, ZTE, Intel, Huawei |
S2-2502225 | Modifications on ML Model retrieval service | ZTE |
S2-2502226 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | Ericsson, AT&T |
S2-2502227 | KI#1 - Further clarification on ML Model performance monitoring for AI/ML positioning | Lenovo, CATT |
S2-2502228 | KI#2 update to VFL preparation procedure | [InterDigital, Nokia, Ericsson, Futurewei, LGE], Huawei, HiSilicon, ZTE, OPPO |
S2-2502229 | KI#2: VFL services | [Nokia, Ericsson], LG Electronics, OPPO? |
S2-2502230 | Adding VFL related services supported by NEF and AF | Vivo, [Nokia, KDDI] |
S2-2502231 | QFI Change event | NTT DOCOMO, CATT, Nokia, Samsung, ETRI |
S2-2502232 | KI#4: Minor Clarifications and Corrections | ETRI |
S2-2502233 | Updates to AI/ML-based positioning general descriptions | Apple, CATT, Intel |
S2-2502234 | Clarification on data collection by LMF from NG-RAN for LMF-based AIML Positioning | CATT |
S2-2502235 | Clarification on LMF as service consumer for ML Model Training | China Mobile |
S2-2502250 | Resolving ENs for VFL | Ericsson, OPPO, [Lenovo, InterDigital, Nokia, KDDI] |
S2-2502251 | Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, OPPO, Nokia, KDDI, Vivo, Samsung |
S2-2502252 | Updates to VFL Training - no new training triggers | [Ericsson, Lenovo, InterDigital, OPPO], Nokia |
S2-2502253 | Resolve some ENs in the vertical federated learning inference procedure | OPPO, ZTE, [Nokia, Ericsson, Samsung] |
S2-2502254 | UE LCS privacy check for ground truth data collection | Qualcomm Incorporated |
S2-2502255 | Updates to AI/ML-based positioning procedures | Apple, [vivo], Interdigital |
S2-2502256 | User consent check during performance monitoring | Samsung |
S2-2502257 | UE LCS privacy check for ground truth data collection | Qualcomm Incorporated, Apple, xiaomi |
S2-2502258 | EN removal for clarification of VFL high level description | KDDI, LG Electronics, Huawei, ETRI, Samsung, China mobile |
S2-2502259 | Editorial improvement on QoS and policy assistance analytics | [Ericsson, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon] Verizon, ETRI, Samsung |
S2-2502260 | update UDM to support user consent of data collection for performance monitoring | Xiaomi |
S2-2502261 | Clarifications on intermediate training result and intermediate model training information | ZTE |
S2-2502262 | Sample update during VFL training | Apple, Ericsson, Samsung, ETRI, Futurewei, ZTE |
S2-2502263 | Enhancements for the accuracy monitoring of VFL training | vivo |
S2-2502264 | KI#2 update to VFL inference procedure | InterDigital |
S2-2502265 | Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, Lenovo, OPPO, ZTE [Nokia, Apple,] |
S2-2502478 | KI#1 - Further clarification on input data for ML model training for AI/ML positioning | Lenovo, Intel |
S2-2502479 | Updates to AI/ML-based positioning procedures | Apple, vivo, Interdigital |
S2-2502480 | Adding new LMF Selection Factor | China Mobile, ZTE, ETRI, Interdigital |
S2-2502481 | Updates to AI/ML-based positioning general descriptions | Apple, [CATT] |
S2-2502482 | Clarification on model performance monitoring for LMF-based AIML Positioning | CATT, vivo, Intel |
S2-2502483 | Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | CATT, ZTE, Intel, Huawei |
S2-2502484 | User consent check during performance monitoring | Samsung |
S2-2502485 | Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | Ericsson, AT&T |
S2-2502486 | KI#1 - Further clarification on ML Model performance monitoring for AI/ML positioning | Lenovo, CATT |
S2-2502487 | Update UDM to support user consent of data collection for performance monitoring | Xiaomi |
S2-2502488 | KI#2 update to VFL preparation procedure | InterDigital, Nokia, Ericsson, Futurewei, LGE, Huawei, HiSilicon, ZTE, OPPO, Samsung, Lenovo |
S2-2502489 | Summary of VFL training triggering scenarios | vivo |
S2-2502490 | Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, OPPO, Nokia, KDDI |
S2-2502491 | Resolve some ENs in the vertical federated learning inference procedure | OPPO, ZTE, [Nokia, Ericsson, Samsung], China Telecom |
S2-2502492 | Adding VFL related services supported by NEF and AF | Vivo, Nokia, KDDI |
S2-2502493 | QFI Change event | NTT DOCOMO, CATT, Nokia, Samsung, ETRI |
S2-2502494 | Editorial improvement on QoS and policy assistance analytics | [Ericsson, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon] Verizon, ETRI, Samsung |
S2-2502495 | Updates to AI/ML-based positioning general descriptions | Apple, CATT, Intel |
S2-2502496 | Clarification on data collection by LMF from NG-RAN for LMF-based AIML Positioning | CATT |
S2-2502497 | KI#1 - Further clarification on input data for ML model training for AI/ML positioning | Lenovo, Intel, Nokia |
S2-2502515 | Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, OPPO, Nokia, KDDI |
S2-2502516 | Clarification on LMF as service consumer for ML Model Training | China Mobile |
S2-2502517 | Enhancements for the accuracy monitoring of VFL training | vivo |
S2-2502518 | Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, Lenovo, OPPO, ZTE, Apple, Nokia |
S2-2502519 | EN removal for clarification of VFL high level description | KDDI, LG Electronics, Huawei, ETRI, Samsung, China mobile |
S2-2502520 | Editorial improvement on QoS and policy assistance analytics | Samsung, Ericsson, Verizon, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon, ETRI |
S2-2502527 | Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, OPPO, Nokia, ZTE, KDDI, Samsung, Vivo, CMCC, China Telecom, Huawei, HiSilicon |
S2-2502528 | Clarification on model performance monitoring for LMF-based AIML Positioning | CATT, vivo, Intel, Huawei, HiSilicon, ZTE, China Telecom |
S2-2502668 | Resolve some ENs in the vertical federated learning inference procedure | OPPO, ZTE, Nokia, Ericsson, Samsung, China Telecom, vivo, Huawei, Hisilicon |
S2-2502669 | KI#2: VFL services | Nokia, Ericsson, LG Electronics, OPPO |
S2-2502670 | KI#2 – update to VFL inference procedure | InterDigital, Samsung |
S2-2502679 | Enhancements for the accuracy monitoring of VFL training | vivo |
S2-2502680 | KI#2 update to VFL inference procedure | InterDigital, Samsung, Nokia, LG Electronics |
S2-2502681 | Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, Lenovo, OPPO, ZTE, Apple, Nokia, InterDigital |
S2-2502682 | EN removal for clarification of VFL high level description | KDDI, LG Electronics, Huawei, ETRI, Samsung, China mobile, ZTE |
S2-2502784 | Updates to AI/ML-based positioning procedures | Apple, vivo, Interdigital |
TDoc | Title | Source |
---|---|---|
S2-2501522 | Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | China Unicom, Ericsson, Nokia, NEC, Lenovo |
S2-2501831 | UCMF discovery in case of Indirect Network Service (INS) deployment deployment.-23.501 | NEC |
S2-2501832 | UCMF discovery in case of Indirect Network Service (INS) deployment deployment.-23.502 | NEC |
S2-2501845 | Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | [China Unicom, Ericsson, Nokia, NEC, Lenovo], Huawei, Hisilicon |
S2-2502168 | Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | [China Unicom, Ericsson], CableLabs, Charter |
S2-2502395 | Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | China Unicom, Ericsson, Nokia, NEC, Lenovo |
S2-2502396 | UCMF discovery in case of Indirect Network Service (INS) deployment deployment-23.501. | NEC |
S2-2502397 | UCMF discovery in case of Indirect Network Service (INS) deployment deployment.-23.502 | NEC |
S2-2502635 | Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | China Unicom, Ericsson, Nokia, NEC, Lenovo |
S2-2502637 | UCMF discovery in case of Indirect Network Service (INS) deployment deployment-23.501. | NEC |
S2-2502641 | UCMF discovery in case of Indirect Network Service (INS) deployment-23.501. | NEC |
TDoc | Title | Source |
---|---|---|
S2-2501743 | Adding the reference and correcting the format error | ZTE |
S2-2502029 | Add Positioning Deactivation step in Cancellation of Reporting of Periodic Events | Nokia, Nokia Shanghai Bell |
S2-2502388 | Adding the reference and correcting the format error | ZTE |
S2-2502390 | [DRAFT] LS on Positioning Deactivation | Nokia |
S2-2502643 | Add Positioning Deactivation step in Cancellation of Reporting of Periodic Events | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S2-2501472 | Clarification about VLAN handling in 5GS | Nokia |
S2-2502398 | Clarification about VLAN handling in 5GS | Nokia |
S2-2502636 | Clarification about VLAN handling in 5GS | Nokia |
TDoc | Title | Source |
---|---|---|
S2-2502128 | Avoiding potential Static IP assignment | [Samsung], China Mobile |
TDoc | Title | Source |
---|---|---|
S2-2501685 | Adjustments for clarity and consistency for PCF interaction with UDR and CHF in the UE Policy Association procedures | Amdocs, AT&T |
S2-2502389 | Adjustments for clarity and consistency for PCF interaction with UDR and CHF in the UE Policy Association procedures | Amdocs, AT&T, Ericsson, Oracle |
S2-2502654 | Adjustments for clarity and consistency for PCF interaction with UDR and CHF in the UE Policy Association procedures | Amdocs, AT&T, Ericsson, Oracle |
S2-2502655 | Adjustments for clarity and consistency for PCF interaction with UDR and CHF in the UE Policy Association procedures | Amdocs, AT&T, Ericsson, Oracle |
TDoc | Title | Source |
---|---|---|
S2-2501363 | LS from CT WG4: Reply LS on RAN support of QoS monitoring capability | CT WG4 (C4-245437) |
S2-2501474 | Providing to the PCF the initial value of the support for QoS monitoring | Nokia |
S2-2501539 | Fixing the QoS monitoring capability notification mechanism | China Telecom |
S2-2501922 | Clarification on the Qos monitoring capability | [ZTE,] Huawei, HiSilicon |
S2-2501923 | Update of notification functionality related to network support for QoS Monitoring | Huawei, HiSilicon |
S2-2502404 | Clarification on the Qos monitoring capability | ZTE, Huawei, HiSilicon |
S2-2502405 | Fixing the QoS monitoring capability notification mechanism | China Telecom, Nokia, Huawei, Ericsson |
S2-2502658 | Clarification on the Qos monitoring capability | ZTE, Huawei, HiSilicon |
S2-2502659 | Fixing the QoS monitoring capability notification mechanism | China Telecom, Nokia, Huawei, Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2501468 | Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE | [ZTE], Nokia,[ Ericsson] |
S2-2501469 | Update to Support of network slice replacement based on AF request | Nokia, ZTE |
S2-2501506 | Update to 23.503 Support of network slice replacement based on AF request | Ericsson |
S2-2501754 | Resolvement of EN in AF Requested modification of the Set of Network Slice(s) for a UE | LG Electronics, [ZTE, Nokia, Ericsson] |
S2-2501803 | Clarification on Configured NSSAI in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE |
S2-2501804 | Clarification on the AF requested network slice replacement | ZTE |
S2-2502097 | Resolvement of EN in AF Requested modification of the Set of Network Slice(s) for a UE | [ZTE, Nokia, Ericsson], Samsung |
S2-2502099 | Clarification for AF requested slice selection | Samsung, [Ericsson, NEC] |
S2-2502401 | Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE | [ZTE], Nokia,[ Ericsson] |
S2-2502402 | Clarification on Configured NSSAI in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE |
S2-2502403 | Update to 23.503 Support of network slice replacement based on AF request | Ericsson, ZTE , Nokia |
S2-2502650 | Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE | [ZTE], Nokia,[ Ericsson] |
S2-2502651 | Clarification on Configured NSSAI in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE |
S2-2502652 | Update to 23.503 Support of network slice replacement based on AF request | Ericsson, ZTE , Nokia, Samsung |
S2-2502653 | Clarification for AF requested slice selection | Samsung, [Ericsson, NEC] |
S2-2502656 | Clarification for AF requested slice selection | Samsung, Ericsson, NEC, ZTE, Huawei |
S2-2502657 | Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE, Nokia, Ericsson, Samsung |
TDoc | Title | Source |
---|---|---|
S2-2501524 | Updates to the ATSSS capability handling | China Telecom, Ericsson?, Apple?, Google?, AT&T?, Samsung? |
S2-2501555 | Clarification on UPF Selecion for ATSSS feature | Huawei, HiSilicon, China Telecom, Nokia, Apple, China Mobile |
S2-2501616 | Use of MPQUIC-UDP when MPQUIC-IP is supported | Ericsson, Apple, Google |
S2-2501619 | Correcting the USS changeover procedure | Ericsson |
S2-2501620 | Timestamping UAV's altitude information reports | Ericsson |
S2-2501628 | Corrections for Any_UE data collection targets | Ericsson, Nokia, Samsung, ZTE |
S2-2501846 | Clarification on IP version used for MPQUIC-E | LG Electronics, CableLabs, Nokia |
S2-2501847 | Clarification on IP version used for MPQUIC-E in procedure | LG Electronics, CableLabs, Nokia |
S2-2501958 | Correction of UE Altitude Reporting Bevahior | Huawei, HiSilicon |
S2-2502170 | Terminology alignment | Apple |
S2-2502385 | Timestamping UAV's altitude information reports | Ericsson, Huawei |
S2-2502386 | Correcting the USS changeover procedure | Ericsson |
S2-2502387 | Corrections for Any_UE data collection targets | Ericsson, Nokia, Samsung, ZTE |
S2-2502424 | Clarification on UPF Selection for ATSSS feature | Huawei, HiSilicon, China Telecom, Nokia, Apple, China Mobile, Samsung, ETRI |
S2-2502425 | Terminology alignment | Apple |
S2-2502426 | Use of MPQUIC-UDP when MPQUIC-IP is supported | Ericsson, Apple, Google, Samsung? |
S2-2502646 | Terminology alignment | Apple |
S2-2502647 | Use of MPQUIC-UDP when MPQUIC-IP is supported | Ericsson, Apple, Google, Samsung? |
TDoc | Title | Source |
---|---|---|
S2-2501386 | LS from RAN WG2: Reply LS on Time Synchronization for MBS | RAN WG2 |
TDoc | Title | Source |
---|---|---|
S2-2501367 | LS from RAN WG2: LS on emergency services and eDRX | RAN WG2 |
S2-2501375 | LS from SA WG5: LS on Usage of Charging Characteristics and CHF Group ID | SA WG5 |
S2-2501475 | Alignment of SA WG2 TNGF specifications to the output of SA WG3 WID NON3GPPMOB_SEC | Nokia |
S2-2501568 | Emergency PDU session and 'delayed' paging | Qualcomm Incorporated |
S2-2501569 | Removing unnecessary restrictions for emergency PDU sessions | Qualcomm |
S2-2501570 | Removing unnecessary restrictions for emergency PDN connection | Qualcomm |
S2-2501571 | Clarify text related to PSAP callback | Qualcomm |
S2-2501572 | [DRAFT] Reply LS on emergency service and eDRX | Qualcomm Technologies Ireland |
S2-2501587 | Clarification of eDRX application with emergency service | Ericsson, AT&T |
S2-2501588 | Clarification of eDRX application with emergency service | Ericsson, AT&T |
S2-2501589 | Clarification of eDRX application with emergency service | Ericsson, AT&T |
S2-2501590 | Clarification on emergency PDU session release | Ericsson, AT&T |
S2-2501591 | Clarification on emergency PDU session release | Ericsson, AT&T |
S2-2501592 | Clarification on emergency PDU session release | Ericsson, AT&T |
S2-2501593 | [DRAFT] Reply LS on emergency services and eDRX | Ericsson |
S2-2501625 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2501626 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2501627 | [DRAFT] LS Usage of Charging Characteristics and CHF Group ID | Ericsson |
S2-2501798 | [DRAFT] Reply LS on emergency call back and paging | ZTE |
S2-2501799 | Clarification on eDRX handling with emergency PDU Session | ZTE |
S2-2501800 | Clarification on eDRX handling with emergency PDU Session | ZTE |
S2-2501896 | EDRX for emergency PDU Sessions | Nokia |
S2-2501897 | EDRX for emergency PDU Sessions | Nokia |
S2-2501898 | EDRX for emergency PDU Sessions | Nokia |
S2-2501899 | [DRAFT] LS reply on emergency services and eDRX | Nokia |
S2-2501900 | DP on emergency services and eDRX | Nokia, ZTE |
S2-2501979 | Clarification on NAS LP-WUS Subgroup Support Indication meaning | Huawei, HiSilicon. Vodafone |
S2-2501980 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2501981 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2501982 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2501983 | [DRAFT] LS Reply on emergency services and eDRX | Huawei, HiSilicon |
S2-2502145 | Paging and UE power saving features related to PSAP call back | Vodafone |
S2-2502147 | PSAP emergency callback interaction with PSM | Vodafone |
S2-2502181 | Alignment of SA WG2 TNGF specifications to the output of SA WG3 WID NON3GPPMOB_SEC | Nokia |
S2-2502182 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2502183 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2502184 | [DRAFT] LS Usage of Charging Characteristics and CHF Group ID | Ericsson |
S2-2502423 | [DRAFT] Reply LS on emergency call back and paging | ZTE |
S2-2502427 | Reply LS on emergency call back and paging | SA WG2 |
S2-2502428 | Removing unnecessary restrictions for emergency PDU sessions | Qualcomm |
S2-2502638 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2502639 | Extending charging support in 5GC | Ericsson, Verizon |
S2-2502640 | Reply LS on Usage of Charging Characteristics and CHF Group ID | SA WG2 |
TDoc | Title | Source |
---|---|---|
S2-2501970 | New WID on Architecture support of Ambient power-enabled Internet of Things | Huawei, HiSilicon |
S2-2502032 | Revised WID on Energy Efficiency and Energy Saving. | Samsung, Lenovo (Rapporteurs) |
S2-2502553 | New WID on Architecture support of Ambient power-enabled Internet of Things. | Huawei, HiSilicon |
S2-2502566 | New WID on Architecture support of Ambient power-enabled Internet of Things. | Huawei, HiSilicon, OPPO |
S2-2502772 | New WID on Architecture support of Ambient power-enabled Internet of Things. | Huawei, HiSilicon, OPPO |
S2-2502773 | Revised WID on Energy Efficiency and Energy Saving. | Samsung, Lenovo (Rapporteurs) |
TDoc | Title | Source |
---|---|---|
S2-2501681 | Cover sheet for presentation of TR 23.700-13 to TSG SA for Approval | OPPO |
S2-2502774 | Cover sheet for presentation of TR 23.700-13 to TSG SA for Approval | OPPO |
TDoc | Title | Source |
---|---|---|
S2-2502591 | WI Status Report for Integration of satellite components in the 5G architecture Phase 3 (5GSAT_Ph3-ARC) | Rapporteur (CATT) |
S2-2502592 | WI Status Report for System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2) | Rapporteur (ZTE) |
S2-2502593 | WI Status Report for Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2) | Rapporteur (Nokia) |
S2-2502594 | WI Status Report for 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys) | Rapporteur (Samsung) |
S2-2502595 | WI Status Report for MPS for IMS Messaging and SMS services (MPS4msg) | Rapporteur (Peraton Labs) |
S2-2502596 | WI Status Report for Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2) | Rapporteur (Qualcomm) |
S2-2502597 | WI Status Report for System Enhancement for Proximity-based Services in 5GS - Phase 3 (5G_ProSe_Ph3) | Rapporteur (TNO) |
S2-2502598 | WI Status Report for Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC) | Rapporteur (Interdigital) |
S2-2502599 | WI Status Report for Enhancement of support for Edge Computing in 5G Core network - Phase 3 (eEDGE_5GC_Ph3) | Rapporteur (Intel) |
S2-2502600 | WI Status Report for Phase 3 for UAS, UAV and UAM (UAS_Ph3) | Rapporteur (Apple) |
S2-2502601 | WI Status Report for UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2) | Rapporteur (ZTE) |
S2-2502602 | WI Status Report for System aspects of 5G NR Femto (5G_Femto) | Rapporteur (DOCOMO) |
S2-2502603 | WI Status Report for Multi-Access (ATSSS_Ph4) (MASSS) | Rapporteur (Apple) |
S2-2502604 | WI Status Report for Architecture support of Ambient power-enabled Internet of Things (AmbientIoT) | Rapporteur (Huawei) |
S2-2502605 | WI Status Report for Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (AIML_CN) | Rapporteur (vivo) |
S2-2502606 | WI Status Report for Indirect Network Sharing (TEI19_NetShare) | Rapporteur (China Unicom) |
S2-2502607 | WI Status Report for Architecture support of roaming value-added services (TEI19_RVAS) | Rapporteur (Ericsson) |
S2-2502608 | WI Status Report for Minimize the Number of Policy Associations (TEI19_MINPA) | Rapporteur (Ericsson) |
S2-2502609 | WI Status Report for Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports (TEI19_DLPM) | Rapporteur (Ericsson) |
S2-2502610 | WI Status Report for Providing per-subscriber VLAN instructions from UDM (TEI19_VLANSUB) | Rapporteur (Ericsson) |
S2-2502611 | WI Status Report for Enhancing Parameter Provisioning with static UE IP address and UP security policy (TEI19_IP_SP_EXP) | Rapporteur (Ericsson) |
S2-2502612 | WI Status Report for Spending Limits for UE Policies in Roaming scenario (TEI19_SLUPiR) | Rapporteur (Oracle) |
S2-2502613 | WI Status Report for Subscription control for reference time distribution in EPS (TEI19_TIME_SUB_EPS) | Rapporteur (Qualcomm) |
S2-2502614 | WI Status Report for On-demand broadcast of GNSS assistance data (TEI19_OBGAD) | Rapporteur (China Mobile) |
S2-2502615 | WI Status Report for QoS monitoring (TEI19_QME) | Rapporteur (China Mobile) |
S2-2502616 | WI Status report for NF discovery and selection by target PLMN (TEI19_NFsel_by_tPLMN) | Rapporteur (Nokia) |
S2-2502617 | WI Status report for Roaming traffic offloading via session breakout in HPLMN (TEI19_HSBO) | Rapporteur (Samsung) |
S2-2502618 | WI Status report for Multiple Location Procedure for Emergency LCS Routing (TEI19_MLR4RTR) | Rapporteur (Nokia) |
S2-2502619 | WI Status report for Support for ProSe services in NPNs (TEI19_ProSe_NPN) | Rapporteur (Philips) |
S2-2502620 | WI Status report for MSISDN verification operation support to Nnef_UEId Service (TEI19_MVOSNS) | Rapporteur (AT&T) |
S2-2502621 | WI Status report for ATSSS Rule Provisioning via 3GPP access connected to EPC (TEI19_ARP3E) | Rapporteur (Xiaomi) |
S2-2502622 | WI Status report for Network Controlled Network Slice Selection (TEI19_SliceSel) | Rapporteur (KDDI) |
S2-2502623 | WI Status report for PRU Usage Extension supported by Core Network (TEI19_PRUE) | Rapporteur (CATT) |
TDoc | Title | Source |
---|---|---|
S2-2502009 | TU budget for Rel-20 | SA WG2 Chair |
S2-2502010 | Work Planning slides | SA WG2 Chair |
S2-2502011 | Work planning spreadsheet | SA WG2 Chair |
S2-2502012 | Report of way of working NWM discussions | SA WG2 Chair |
S2-2502014 | Way of working guidance proposal | SA WG2 Chair |
S2-2502102 | SA WG2 High Level TU planning for 2025 and 2026 | SA WG2 Chair |
S2-2502642 | Work Planning slides | SA WG2 Chair |
TDoc | Title | Source |
---|---|---|
S2-2501708 | The Discussion on ISAC | China Mobile Com. Corporation |
TDoc | Title | Source |
---|---|---|
S2-2501416 | WID: TEI20_DAMUP - Deferred AM and UE Policies in the 5GC | Oracle, Verizon UK Ltd |
S2-2501444 | Potential working tasks of AIML in R20 5G-A | ZTE |
S2-2501461 | Report of NWM discussion on Enhancements for ePDG based access to 5GC | Qualcomm France |
S2-2501462 | New SID on Enhancements for ePDG based access to 5GC | Qualcomm Incorporated as moderator |
S2-2501535 | Discussion on R20 AIML_CN ph2 AI/ML for User Plane | SK Telecom |
S2-2501545 | AI/ML SID: 5GC information exposure to the UE | Apple, OPPO |
S2-2501574 | Moderator report on: Moderated discussion for Industrial Network enhancements Features | Ericsson Canada Inc. |
S2-2501576 | Moderator report on: Moderated discussion for Industrial Network enhancements Features | Ericsson Canada Inc. |
S2-2501645 | The NWM and moderator report for satellite phase4 | CATT |
S2-2501722 | Discussion on SA WG2 Rel-20 5G-A ISAC/Sensing | NEC |
S2-2501723 | [DRAFT] LS on Sensing control and Data collection in Rel-20 5G-A ISAC/Sensing | NEC |
S2-2501725 | New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication | NEC |
S2-2501727 | Discussion on Probability Improvement of informing the MT call to the UE in very poor SNR conditions | NEC |
S2-2501728 | New SID on Probability Improvement of informing the MT call to the UE in very poor SNR conditions | NEC |
S2-2501772 | New SID on IMS resiliency | KDDI |
S2-2501773 | Discussion on IMS resiliency study | KDDI |
S2-2501779 | Moderator_Report_Rel-20 5GA ISAC | Xiaomi |
S2-2501796 | New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication | Xiaomi (Moderator of ISAC) |
S2-2501822 | NWM Discussion Report on R20 5GA AIML enhancement | Vivo (Moderator) |
S2-2501854 | New Study on eRG without USIM | China Unicom |
S2-2501935 | New SID on Study on Integration of satellite components in the 5G architecture Phase 4 | CATT |
S2-2501956 | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2 | vivo (Moderator) |
S2-2502015 | Considerations for Release 20 5GA AIML SID | Lenovo |
S2-2502037 | Report of moderated NWM discussion on Rel-20 Energy Efficiency and Energy Saving Phase 2 | Samsung Electronics France SA |
S2-2502040 | New SID for Energy Efficiency and Energy Saving Phase2 | Samsung (Moderator) |
S2-2502057 | Discussion on R20 AIML_CN ph2 AI/ML for User Plane | SK Telecom, China Mobile, ETRI, KPN N.V., LG Uplus, Oracle, Rakuten Mobile, Samsung, Verizon |
S2-2502081 | Discussion paper on Rel-20 5G-A ISAC SID | Xiaomi |
S2-2502116 | Discussion paper on the scope of GEO voice call | vivo |
S2-2502120 | Progressing moderated discussion for 'Industrial Network enhancements' features | Ericsson |
S2-2502121 | New SID on Study on Industrial Networks enhancements | Ericsson (moderator) |
S2-2502122 | Study of Industrial Networks enhancements- New WTs | Ericsson (moderator) |
S2-2502124 | Proposal on Rel-20 Energy WTs | Ofinno |
S2-2502134 | New SID on Industrial Network enhancements for 5G | Siemens |
S2-2502177 | Feedback on SID proposal for Enhancements for ePDG based access to 5GC | Charter Communications, ZTE Corporation, CableLabs, Nokia, Lenovo, CEWiT, Deutsche Telekom, Reliance Jio? |
S2-2502629 | New SID on Study on Integration of satellite components in the 5G architecture Phase 4 | CATT |
S2-2502630 | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2. | vivo (Moderator) |
S2-2502631 | New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication. | Xiaomi (Moderator of ISAC) |
S2-2502632 | New SID on Energy Efficiency and Energy Saving Phase2. | Samsung (Moderator) |
S2-2502768 | New SID on Study on Integration of satellite components in the 5G architecture Phase 4 | CATT |
S2-2502769 | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2. | vivo (Moderator) |
S2-2502770 | New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication. | Xiaomi (Moderator of ISAC) |
S2-2502771 | New SID on Energy Efficiency and Energy Saving Phase2. | Samsung (Moderator) |
S2-2502778 | New SID on Study on Integration of satellite components in the 5G architecture Phase 4. | CATT |
S2-2502779 | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2. | vivo (Moderator) |
S2-2502780 | New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication. | Xiaomi (Moderator of ISAC) |
S2-2502781 | New SID on Energy Efficiency and Energy Saving Phase2. | Samsung (Moderator) |
S2-2502788 | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2. | vivo (Moderator) |
TDoc | Title | Source |
---|---|---|
S2-2501355 | SA WG2#167 meeting schedule | SA WG2 Chair |
S2-2501388 | Reserved for incoming LS | MCC |
S2-2501389 | Reserved for incoming LS | MCC |
S2-2501390 | Reserved for incoming LS | MCC |
S2-2501391 | Reserved for incoming LS | MCC |
S2-2501392 | Reserved for incoming LS | MCC |
S2-2501393 | Reserved for incoming LS | MCC |
S2-2501394 | Reserved for incoming LS | MCC |
S2-2501395 | Reserved for incoming LS | MCC |
S2-2501396 | Reserved for incoming LS | MCC |
S2-2501397 | Reserved for incoming LS | MCC |
S2-2501398 | Reserved for incoming LS | MCC |
S2-2501399 | Reserved for incoming LS | MCC |
S2-2501400 | Reserved for incoming LS | MCC |
S2-2501401 | Reserved for incoming LS | MCC |
S2-2501402 | Reserved for incoming LS | MCC |
S2-2501403 | Reserved for incoming LS | MCC |
S2-2501404 | Reserved for incoming LS | MCC |
S2-2501405 | Reserved for incoming LS | MCC |
S2-2501406 | Reserved for incoming LS | MCC |
S2-2501407 | Reserved for incoming LS | MCC |
S2-2501408 | Reserved for incoming LS | MCC |
S2-2501459 | User consent purpose for AI/ML-based positioning | Apple |
S2-2501473 | Alignment of SA WG2 TNGF specifications to the output of SA WG3 WID NON3GPPMOB_SEC | Nokia |
S2-2501541 | Resolving EN on the use of Energy Saving indicator | Samsung |
S2-2501567 | Discussion on QoS Flow vs. Service Data Flow granularity | Huawei, HiSilicon |
S2-2501617 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2501618 | Handling of handover cancel during 5GS to EPS mobility | Ericsson, Verizon |
S2-2501635 | MPS Resume Cause alignment | Peraton Labs, CISA ECD, Nokia, AT&T, T-Mobile USA, Verizon |
S2-2501636 | MPS Resume Cause and Priority Handling alignment | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
S2-2501789 | Resolving ENs on Avatar ID List | Qualcomm Incorporated, ZTE |
S2-2501819 | SA WG2 6G Study - structure, process proposal | Nokia |
S2-2501820 | SA WG2 6G SID draft | Nokia |
S2-2501827 | Policy control with energy saving consideration. | [vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom,] CATT, [Samsung] |
S2-2501927 | Support of Attach with PDN connection for split MME architecture | [LG Electronics, NEC, Samsung],CATT |
S2-2501928 | Update for support of UE-Satellite-UE communication | Update for support of UE-Satellite-UE communication |
S2-2502018 | Updates on VFL training and VFL inference to remove ENs | China Telecom, [ZTE, Lenovo, Nokia, ETRI] |
S2-2502039 | Update for support of UE-Satellite-UE communication | CATT |
S2-2502087 | Adapting the data collection procedure for performance monitoring | Xiaomi |
S2-2502093 | Provisioning Multi-modal Service ID to NG-RAN | Qualcomm, Ericsson |
S2-2502301 | Reserved for Wanqiang's sessions | - |
S2-2502383 | Reserved for Wanqiang's sessions | - |
S2-2502384 | Reserved for Wanqiang's sessions | - |
S2-2502587 | Reserved for Wanqiang's sessions | - |
S2-2502624 | Reserved for Wanqiang's sessions | - |
S2-2502625 | Reserved for Wanqiang's sessions | - |
S2-2502626 | Reserved for Wanqiang's sessions | - |
S2-2502627 | Reserved for Wanqiang's sessions | - |
S2-2502628 | Reserved for Wanqiang's sessions | - |
S2-2502684 | Reserved for Dario's sessions | - |
S2-2502685 | Reserved for Dario's sessions | - |
S2-2502686 | Reserved for Dario's sessions | - |
S2-2502687 | Reserved for Dario's sessions | - |
S2-2502688 | Reserved for Dario's sessions | - |
S2-2502689 | Reserved for Dario's sessions | - |
S2-2502690 | Reserved for Dario's sessions | - |
S2-2502691 | Reserved for Dario's sessions | - |
S2-2502692 | Reserved for Dario's sessions | - |
S2-2502693 | Reserved for Dario's sessions | - |
S2-2502694 | Reserved for Dario's sessions | - |
S2-2502695 | Reserved for Dario's sessions | - |
S2-2502696 | Reserved for Dario's sessions | - |
S2-2502697 | Reserved for Dario's sessions | - |
S2-2502698 | Reserved for Dario's sessions | - |
S2-2502699 | Reserved for Dario's sessions | - |
S2-2502700 | Reserved for Dario's sessions | - |
S2-2502701 | Reserved for Dario's sessions | - |
S2-2502702 | Reserved for Dario's sessions | - |
S2-2502703 | Reserved for Dario's sessions | - |
S2-2502704 | Reserved for Dario's sessions | - |
S2-2502705 | Reserved for Dario's sessions | - |
S2-2502706 | Reserved for Dario's sessions | - |
S2-2502707 | Reserved for Dario's sessions | - |
S2-2502708 | Reserved for Dario's sessions | - |
S2-2502709 | Reserved for Dario's sessions | - |
S2-2502710 | Reserved for Dario's sessions | - |
S2-2502711 | Reserved for Dario's sessions | - |
S2-2502712 | Reserved for Dario's sessions | - |
S2-2502713 | Reserved for Dario's sessions | - |
S2-2502714 | Reserved for Dario's sessions | - |
S2-2502715 | Reserved for Dario's sessions | - |
S2-2502716 | Reserved for Dario's sessions | - |
S2-2502717 | Reserved for Dario's sessions | - |
S2-2502718 | Reserved for Dario's sessions | - |
S2-2502719 | Reserved for Dario's sessions | - |
S2-2502720 | Reserved for Dario's sessions | - |
S2-2502721 | Reserved for Dario's sessions | - |
S2-2502722 | Reserved for Dario's sessions | - |
S2-2502723 | Reserved for Dario's sessions | - |
S2-2502724 | Reserved for Dario's sessions | - |
S2-2502725 | Reserved for Dario's sessions | - |
S2-2502726 | Reserved for Dario's sessions | - |
S2-2502727 | Reserved for Dario's sessions | - |
S2-2502728 | Reserved for Dario's sessions | - |
S2-2502729 | Reserved for Dario's sessions | - |
S2-2502730 | Reserved for Dario's sessions | - |
S2-2502731 | Reserved for Dario's sessions | - |
S2-2502732 | Reserved for Dario's sessions | - |
S2-2502733 | Reserved for Dario's sessions | - |
S2-2502734 | Reserved for Dario's sessions | - |
S2-2502735 | Reserved for Dario's sessions | - |
S2-2502736 | Reserved for Dario's sessions | - |
S2-2502737 | Reserved for Dario's sessions | - |
S2-2502738 | Reserved for Dario's sessions | - |
S2-2502739 | Reserved for Dario's sessions | - |
S2-2502740 | Reserved for Dario's sessions | - |
S2-2502741 | Reserved for Dario's sessions | - |
S2-2502742 | Reserved for Dario's sessions | - |
S2-2502743 | Reserved for Dario's sessions | - |
S2-2502744 | Reserved for Dario's sessions | - |
S2-2502745 | Reserved for Dario's sessions | - |
S2-2502746 | Reserved for Dario's sessions | - |
S2-2502747 | Reserved for Dario's sessions | - |
S2-2502748 | Reserved for Dario's sessions | - |
S2-2502749 | Reserved for Dario's sessions | - |
S2-2502750 | Reserved for Dario's sessions | - |
S2-2502751 | Reserved for Dario's sessions | - |
S2-2502752 | Reserved for Dario's sessions | - |
S2-2502753 | Reserved for Dario's sessions | - |
S2-2502754 | Reserved for Dario's sessions | - |
S2-2502755 | Reserved for Dario's sessions | - |
S2-2502756 | Reserved for Dario's sessions | - |
S2-2502757 | Reserved for Dario's sessions | - |
S2-2502758 | Reserved for Dario's sessions | - |
S2-2502759 | Reserved for Dario's sessions | - |
S2-2502760 | Reserved for Dario's sessions | - |
S2-2502761 | Reserved for Dario's sessions | - |
S2-2502762 | Reserved for Dario's sessions | - |
S2-2502763 | Reserved for Dario's sessions | - |
S2-2502764 | Reserved for Dario's sessions | - |
S2-2502765 | Reserved for Dario's sessions | - |
S2-2502766 | Reserved for Dario's sessions | - |
S2-2502767 | Reserved for Dario's sessions | - |