|
| 23.228 | 1525 | 1 | B | 19.0.0 | Rel-19 | Supporting Avatar Communication |
S2-2412397
| | SA2#166 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1525 | - | B | 19.0.0 | Rel-19 | Supporting Avatar Communication |
S2-2412170
| | SA2#166 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1524 | 1 | B | 19.0.0 | Rel-19 | Procedure for supporting of third party user identity information in IMS |
S2-2412401
| | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1524 | - | B | 19.0.0 | Rel-19 | Procedure for supporting of third party user identity information in IMS |
S2-2412096
| | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1519 | - | B | 19.0.0 | Rel-19 | KI#8: Procedures of avatar communications |
S2-2411948
| | SA2#166 | vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1518 | 1 | F | 19.0.0 | Rel-19 | KI#6: Modification on standalone IMS DC session |
S2-2412468
| | SA2#166 | vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1518 | - | F | 19.0.0 | Rel-19 | KI#6: Modification on standalone IMS DC session |
S2-2411946
| | SA2#166 | vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1517 | - | B | 19.0.0 | Rel-19 | Function Description for Interworking with MTSI UE |
S2-2411897
| | SA2#166 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1516 | 1 | B | 19.0.0 | Rel-19 | Transition Between IMS Avatar and Audio/video Communication |
S2-2412398
| | SA2#166 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1516 | - | B | 19.0.0 | Rel-19 | Transition Between IMS Avatar and Audio/video Communication |
S2-2411896
| | SA2#166 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1515 | - | B | 19.0.0 | Rel-19 | Add DC Application Server Description |
S2-2411894
| | SA2#166 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1512 | 1 | B | 19.0.0 | Rel-19 | Service updates to support multiplexing multiple DC applications over single SCTP connection |
S2-2412395
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1512 | - | B | 19.0.0 | Rel-19 | Service updates to support multiplexing multiple DC applications over single SCTP connection |
S2-2411609
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1511 | 1 | B | 19.0.0 | Rel-19 | Support of multiplexing multiple DC applications over single SCTP connection |
S2-2412394
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1511 | - | B | 19.0.0 | Rel-19 | Support of multiplexing multiple DC applications over single SCTP connection |
S2-2411608
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1510 | - | B | 19.0.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2411607
| | SA2#166 | [Ericsson], Chi... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1509 | 1 | B | 19.0.0 | Rel-19 | Alignment of DC exposure and standalone DC with IMS DC architecture |
S2-2412405
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1509 | - | B | 19.0.0 | Rel-19 | Alignment of DC exposure and standalone DC with IMS DC architecture |
S2-2411606
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1508 | - | F | 19.0.0 | Rel-19 | Update to Bootstrap and Application Data Channel Setup Signalling Procedure for data channel interworking |
S2-2411602
| | SA2#166 | SA WG2 |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1506 | - | B | 19.0.0 | Rel-19 | Procedures of IMS Avatar communication |
S2-2411519
| | SA2#166 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1505 | - | B | 19.0.0 | Rel-19 | KI#7: DC Multiplexing |
S2-2411331
| withdrawn | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1504 | - | B | 19.0.0 | Rel-19 | KI#8: Procedures for avatar communications |
S2-2411330
| withdrawn | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1503 | - | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411329
| withdrawn | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1502 | - | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2411328
| withdrawn | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1500 | - | B | 19.0.0 | Rel-19 | PS Data Off Exemption configuration for IMS Data Channel |
S2-2410525
| not treated | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1499 | 1 | B | 19.0.0 | Rel-19 | Supporting of IMS Avatar communication |
S2-2410621
| withdrawn | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1499 | - | B | 19.0.0 | Rel-19 | Supporting of IMS Avatar communication |
S2-2410524
| postponed | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1498 | 2 | B | 19.0.0 | Rel-19 | DCSF instructing the IMS AS to terminate the session at the IMS AS |
S2-2410969
| agreed | SA2#165 | NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1498 | 1 | B | 19.0.0 | Rel-19 | DCSF instructing the IMS AS to terminate the session at the IMS AS |
S2-2410697
| revised | SA2#165 | NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1498 | - | B | 19.0.0 | Rel-19 | DCSF instructing the IMS AS to terminate the session at the IMS AS |
S2-2410455
| revised | SA2#165 | NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1497 | 1 | B | 19.0.0 | Rel-19 | Corrections to the IMS standalone sessions |
S2-2412073
| | SA2#166 | NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1497 | - | B | 19.0.0 | Rel-19 | Corrections to the IMS standalone sessions |
S2-2410447
| revised | SA2#165 | NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1491 | - | C | 19.0.0 | Rel-19 | Update IMS AS Service to align with the service of NEF |
S2-2410358
| not treated | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1490 | - | C | 19.0.0 | Rel-19 | KI#6: Support of Standalone IMS Data Channel feature |
S2-2410356
| not treated | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 8 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2412466
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 7 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2412166
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 6 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2412111
| | SA2#166 | Nokia [, Huawei... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 5 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2411898
| | SA2#166 | [Huawei, HiSili... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 4 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2411589
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 3 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2411011
| revised | SA2#165 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 2 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2410968
| revised | SA2#165 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | 1 | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2410693
| revised | SA2#165 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1489 | - | B | 19.0.0 | Rel-19 | Network Capability Exposure Procedure |
S2-2410355
| revised | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1488 | 2 | B | 19.0.0 | Rel-19 | Supporting Avatar Communication |
S2-2410916
| merged | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1488 | 1 | B | 19.0.0 | Rel-19 | Supporting Avatar Communication |
S2-2410620
| revised | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1488 | - | B | 19.0.0 | Rel-19 | Supporting Avatar Communication |
S2-2410354
| revised | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1487 | - | D | 19.0.0 | Rel-19 | Removing MRF Usage for Data Channel |
S2-2410340
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1486 | - | B | 19.0.0 | Rel-19 | Base Avatar Repository in IMS DC Architecture |
S2-2410339
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1485 | - | B | 19.0.0 | Rel-19 | Clarification on DC Application Server |
S2-2410338
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1484 | - | B | 19.0.0 | Rel-19 | Clarification on Functional Support for Interworking with MTSI UE |
S2-2410337
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 6 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2412465
| | SA2#166 | [ZTE, Qualcomm,... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 5 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2412164
| | SA2#166 | Huawei, HiSilli... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 4 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2411605
| | SA2#166 | [ZTE, Qualcomm,... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 3 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2411469
| | SA2#166 | [ZTE, Qualcomm,... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 2 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2410967
| revised | SA2#165 | ZTE, Qualcomm, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | 1 | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2410692
| revised | SA2#165 | ZTE, Qualcomm, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1483 | - | B | 19.0.0 | Rel-19 | Address ENs in IMS AS Session Management Service |
S2-2410336
| revised | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1482 | - | B | 19.0.0 | Rel-19 | PS Data Off Exemption for Services over IMS DC |
S2-2410335
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1481 | - | B | 19.0.0 | Rel-19 | Transition Between IMS Avatar and Audio/video Communication |
S2-2410334
| not treated | SA2#165 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 8 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2412396
| | SA2#166 | Samsung, [ZTE, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 7 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411947
| | SA2#166 | [Samsung, ZTE, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 6 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411899
| | SA2#166 | [Samsung,] ZTE,... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 5 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411473
| | SA2#166 | Ericsson, [Sams... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 4 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411332
| | SA2#166 | Samsung, [ZTE, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 3 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2411010
| revised | SA2#165 | Samsung, ZTE, v... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 2 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2410966
| revised | SA2#165 | Samsung, ZTE, v... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | 1 | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2410619
| revised | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1480 | - | B | 19.0.0 | Rel-19 | KI#8: Architecture for avatar communications |
S2-2410217
| revised | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 6 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2412636
| | SA2#166 | Samsung, [Ericsson] |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 5 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2411944
| | SA2#166 | [Samsung, Erics... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 4 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2411333
| | SA2#166 | Samsung, [Ericsson] |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 3 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2410973
| revised | SA2#165 | Samsung, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 2 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2410970
| revised | SA2#165 | Samsung, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | 1 | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2410696
| revised | SA2#165 | Samsung, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1479 | - | B | 19.0.0 | Rel-19 | KI#3: DC interworking with MTSI UE |
S2-2410216
| revised | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 9 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2412637
| | SA2#166 | [Nokia, Ericsso... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 8 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2412400
| | SA2#166 | Nokia[, Ericsso... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 7 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2412399
| | SA2#166 | [Nokia, Ericsso... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 6 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2412132
| | SA2#166 | Nokia[, Ericsso... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 5 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2412085
| | SA2#166 | [Nokia, Ericsso... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 4 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2411009
| revised | SA2#165 | Nokia, Ericsson... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 3 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2410972
| revised | SA2#165 | Nokia, Ericsson... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 2 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2410915
| revised | SA2#165 | Nokia, Ericsson... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | 1 | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2410617
| revised | SA2#165 | Nokia, Ericsson... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1478 | - | B | 19.0.0 | Rel-19 | Support of third party user identity information in IMS |
S2-2410189
| revised | SA2#165 | Nokia, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1474 | - | F | 19.0.0 | Rel-19 | KI#6: Update to Support for Standalone IMS Data Channel feature |
S2-2409985
| not treated | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1473 | - | F | 19.0.0 | Rel-19 | Update to interworking between DCMTSI UE and MTSI UE |
S2-2409984
| merged | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1472 | - | C | 19.0.0 | Rel-19 | Update of Nimsas_ImsSessionManagement Service to resolve ENs |
S2-2409964
| merged | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1471 | - | B | 19.0.0 | Rel-19 | PS Data Off Exemption configuration for IMS Data Channel |
S2-2409963
| not treated | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1468 | - | C | 19.0.0 | Rel-19 | Update of Nimsas_ImsSessionManagement Service to resolve ENs |
S2-2409909
| withdrawn | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1467 | - | B | 19.0.0 | Rel-19 | PS Data Off Exemption configuration for IMS Data Channel |
S2-2409908
| withdrawn | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1466 | - | B | 19.0.0 | Rel-19 | Supporting of IMS Avatar communication |
S2-2409907
| withdrawn | SA2#165 | Qualcomm Incorp... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1465 | 1 | B | 19.0.0 | Rel-19 | Update on support of DC interworking |
S2-2411943
| | SA2#166 | vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1465 | - | F | 19.0.0 | Rel-19 | Update on support of DC interworking |
S2-2409906
| revised | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1463 | - | F | 19.0.0 | Rel-19 | Update on support of DC interworking |
S2-2409731
| withdrawn | SA2#165 | vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1462 | 1 | F | 19.0.0 | Rel-19 | Resolve configuration EN for Standalone IMS DC feature |
S2-2410695
| agreed | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1462 | - | F | 19.0.0 | Rel-19 | Resolve configuration EN for Standalone IMS DC feature |
S2-2409728
| revised | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1461 | - | F | 19.0.0 | Rel-19 | Update on combined BDC and ADC setup procedure |
S2-2409727
| not treated | SA2#165 | Vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1460 | - | F | 19.0.0 | Rel-19 | Update on adding ADC to standalone IMS DC with BDC procedure |
S2-2409726
| postponed | SA2#165 | Vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1459 | - | F | 19.0.0 | Rel-19 | Update on originating standalone BDC procedure |
S2-2409725
| not treated | SA2#165 | Vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1458 | - | D | 19.0.0 | Rel-19 | Editorial modification on general description for standalone IMS DC session |
S2-2409724
| not treated | SA2#165 | Vivo, Qualcomm |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1457 | - | D | 19.0.0 | Rel-19 | Editorial modification on change between IMS DC and standalone IMS DC |
S2-2409723
| not treated | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1452 | 2 | B | 19.0.0 | Rel-19 | Authenitcation and Authorization of third party identities during IMS Session |
S2-2410618
| postponed | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1452 | 1 | B | 19.0.0 | Rel-19 | Authenitcation and Authorization of third party identities during IMS Session |
S2-2410511
| revised | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1451 | 1 | B | 19.0.0 | Rel-19 | PS data off exemption for services over IMS DC |
S2-2410504
| not treated | SA2#165 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1429 | 4 | B | 19.0.0 | Rel-19 | IMS AS Service Enhancement to Support IMS Event Exposure |
S2-2410614
| withdrawn | SA2#165 | ZTE, NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1429 | 3 | B | 19.0.0 | Rel-19 | IMS AS Service Enhancement to Support IMS Event Exposure |
S2-2410446
| noted | SA2#165 | ZTE, NTT DOCOMO |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1423 | 1 | B | 19.0.0 | Rel-19 | Support of avatar communication in bootstrap data channel |
S2-2409729
| postponed | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 6 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2412169
| | SA2#166 | vivo?, Huawei, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 5 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2411895
| | SA2#166 | [vivo, Huawei, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 4 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2411604
| | SA2#166 | [vivo, Huawei, ... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 3 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2410914
| revised | SA2#165 | Vivo, Huawei, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 2 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2410616
| revised | SA2#165 | Vivo, Huawei, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1421 | 1 | B | 19.0.0 | Rel-19 | KI#5: Support of Data off feature for data channel |
S2-2409730
| revised | SA2#165 | Vivo |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1416 | 3 | B | 19.0.0 | Rel-19 | Terminating local BDC establishment without BDC media component in SDP of incoming INVITE request |
S2-2412462
| | SA2#166 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 13 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2412403
| | SA2#166 | Ericsson, [Noki... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 12 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2412167
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 11 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2411949
| | SA2#166 | [Ericsson, Noki... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 10 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2411603
| | SA2#166 | [Ericsson, Noki... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 9 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2411471
| | SA2#166 | Ericsson, [Noki... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 8 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2410974
| revised | SA2#165 | Ericsson, Nokia... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 7 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2410971
| revised | SA2#165 | Ericsson, Nokia... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 6 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2410913
| revised | SA2#165 | Ericsson, Nokia... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 5 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2410613
| revised | SA2#165 | Ericsson, Nokia... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.228 | 1409 | 4 | B | 19.0.0 | Rel-19 | KI#1: IMS Subscribe/Notify Framework Architecture |
S2-2409982
| revised | SA2#165 | Ericsson, Nokia... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5177 | 2 | B | 19.1.0 | Rel-19 | KI#4: Enhancements to NEF Services for provisioning of RCD information |
S2-2412638
| | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5177 | 1 | B | 19.1.0 | Rel-19 | KI#4: Enhancements to NEF Services for provisioning of RCD information |
S2-2412402
| | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5177 | - | B | 19.1.0 | Rel-19 | KI#4: Enhancements to NEF Services for provisioning of RCD information |
S2-2412092
| | SA2#166 | Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | 5 | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2412467
| | SA2#166 | [Huawei, HiSili... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | 4 | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2412165
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | 3 | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2411562
| | SA2#166 | [Huawei, HiSili... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | 2 | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2411012
| revised | SA2#165 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | 1 | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2410694
| revised | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 5087 | - | B | 19.1.0 | Rel-19 | Update NEF services to support the conclusion of KI#1 and KI#2 |
S2-2410357
| revised | SA2#165 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 11 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2412404
| | SA2#166 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 10 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2412168
| | SA2#166 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 9 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2412091
| | SA2#166 | [Ericsson], Samsung |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 8 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2411472
| | SA2#166 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 7 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2411188
| revised | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 6 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2411181
| revised | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 5 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2410615
| revised | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 23.502 | 4872 | 4 | B | 19.1.0 | Rel-19 | KI#1: Enhancements to NEF Services |
S2-2409983
| revised | SA2#165 | Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0054 | - | B | 19.0.0 | Rel-19 | Procedure of avatar communication |
C1-246448
| | CT1#152 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0053 | - | B | 19.0.0 | Rel-19 | Procedure of network-initiated DC estabilishement |
C1-246447
| | CT1#152 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0052 | - | B | 19.0.0 | Rel-19 | Procedure of Standalone data channel |
C1-246446
| | CT1#152 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0051 | - | B | 19.0.0 | Rel-19 | AS handling of IMS data channel in PS Data off feature |
C1-246311
| | CT1#152 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0050 | - | B | 19.0.0 | Rel-19 | UE handling of IMS data channel in PS Data off feature |
C1-246310
| | CT1#152 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0042 | 1 | B | 19.0.0 | Rel-19 | Support of interworking with MTSI client |
C1-245856
| agreed | CT1#151 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0042 | - | B | 19.0.0 | Rel-19 | Support of interworking with MTSI client |
C1-245208
| revised | CT1#151 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0041 | 1 | B | 19.0.0 | Rel-19 | Support of Standalone DC |
C1-245860
| agreed | CT1#151 | Huawei, HiSilic... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0041 | - | B | 19.0.0 | Rel-19 | Support of Standalone DC |
C1-245207
| revised | CT1#151 | Huawei, HiSilicon |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0040 | - | B | 19.0.0 | Rel-19 | KI#6-The procedure on the UE for standalone DC |
C1-245180
| merged | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0039 | 2 | B | 19.0.0 | Rel-19 | Update session control and DC application related requirement to support the standalone DC |
C1-245941
| agreed | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0039 | 1 | B | 19.0.0 | Rel-19 | Update session control and DC application related requirement to support the standalone DC |
C1-245859
| revised | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0039 | - | B | 19.0.0 | Rel-19 | Update session control and DC application related requirement to support the standalone DC |
C1-245178
| revised | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0038 | 1 | B | 19.0.0 | Rel-19 | The procedure on the IMS AS for DC interworking |
C1-245857
| merged | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.186 | 0038 | - | B | 19.0.0 | Rel-19 | The procedure on the IMS AS for DC interworking |
C1-245176
| revised | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.229 | 6691 | - | B | 19.0.0 | Rel-19 | Update the description of PS Data off feature |
C1-246312
| | CT1#152 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.229 | 6675 | 1 | B | 19.0.0 | Rel-19 | The standalone DC in R19 TS |
C1-245858
| agreed | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.229 | 6675 | - | B | 19.0.0 | Rel-19 | The standalone DC in R19 TS |
C1-245177
| revised | CT1#151 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 24.275 | 0008 | 4 | B | 18.2.0 | Rel-19 | Support DC in 3GPP PS Data Off exempt services |
C1-245918
| agreed | CT1#151 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.275 | 0008 | 3 | B | 18.2.0 | Rel-19 | Support DC in 3GPP PS Data Off exempt services |
C1-245855
| revised | CT1#151 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 24.275 | 0008 | 2 | B | 18.2.0 | Rel-19 | Support DC in 3GPP PS Data Off exempt services |
C1-245175
| revised | CT1#151 | China Mobile, H... |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0030 | 1 | B | 18.2.0 | Rel-19 | Definition of Nimsas_ImsEE Service |
C4-245352
| agreed | CT4#126 | Huawei, Ericsson |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0030 | - | B | 18.2.0 | Rel-19 | Definition of Nimsas_ImsEE Service |
C4-245158
| revised | CT4#126 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0029 | - | B | 18.2.0 | Rel-19 | Report the PS Data Off Status to DCSF |
C4-245154
| merged | CT4#126 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0028 | 2 | B | 18.2.0 | Rel-19 | Support of IMS AS Event Exposure Service |
C4-245397
| agreed | CT4#126 | China Mobile, H... |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0028 | 1 | B | 18.2.0 | Rel-19 | Support of IMS AS Event Exposure Service |
C4-245346
| revised | CT4#126 | China Mobile, Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0028 | - | B | 18.2.0 | Rel-19 | Support of IMS AS Event Exposure Service |
C4-245134
| revised | CT4#126 | China Mobile, Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0027 | - | B | 18.2.0 | Rel-19 | Support of the specific PSI within Called ID for standalone DC |
C4-245129
| agreed | CT4#126 | China Mobile |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0026 | - | B | 18.2.0 | Rel-19 | Support of PS Data off feature for data channel |
C4-245127
| merged | CT4#126 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0025 | - | D | 18.2.0 | Rel-19 | Update the description of EventInitiator data type |
C4-245124
| agreed | CT4#126 | China Mobile |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0024 | 2 | F | 18.2.0 | Rel-19 | Event Notification for PS Data Off Status |
C4-245396
| agreed | CT4#126 | ZTE, Huawei, Ch... |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0024 | 1 | F | 18.2.0 | Rel-19 | Event Notification for PS Data Off Status |
C4-245345
| revised | CT4#126 | ZTE, Huawei, Ch... |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0024 | - | F | 18.2.0 | Rel-19 | Event Notification for PS Data Off Status |
C4-245052
| revised | CT4#126 | ZTE |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0022 | 1 | B | 18.2.0 | Rel-19 | Support of interworking with MTSI client |
C4-244385
| agreed | CT4#125 | Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0022 | - | B | 18.2.0 | Rel-19 | Support of interworking with MTSI client |
C4-244234
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0021 | 2 | B | 18.2.0 | Rel-19 | Definition of Nimsas_ImsSessionManagement Service |
C4-245159
| agreed | CT4#126 | Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0021 | 1 | B | 18.2.0 | Rel-19 | Definition of Nimsas_ImsSessionManagement Service |
C4-244384
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0021 | - | B | 18.2.0 | Rel-19 | Definition of Nimsas_ImsSessionManagement Service |
C4-244233
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.175 | 0019 | 1 | B | 18.2.0 | Rel-19 | Supporting of network initiated IMS Data Channel |
C4-244383
| agreed | CT4#125 | China Mobile, Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.175 | 0019 | - | B | 18.2.0 | Rel-19 | Supporting of network initiated IMS Data Channel |
C4-244108
| revised | CT4#125 | China Mobile |
| | | | | NG_RTC_Ph2 |
|
|
| 29.176 | 0021 | 1 | B | 18.3.0 | Rel-19 | Support of interworking with MTSI client |
C4-244386
| agreed | CT4#125 | Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.176 | 0021 | - | B | 18.3.0 | Rel-19 | Support of interworking with MTSI client |
C4-244235
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.364 | 0054 | 3 | B | 18.1.0 | Rel-19 | Support of Standalone DC |
C4-244527
| agreed | CT4#125 | Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.364 | 0054 | 2 | B | 18.1.0 | Rel-19 | Support of Standalone DC |
C4-244482
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.364 | 0054 | 1 | B | 18.1.0 | Rel-19 | Support of Standalone DC |
C4-244387
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.364 | 0054 | - | B | 18.1.0 | Rel-19 | Support of Standalone DC |
C4-244236
| revised | CT4#125 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.510 | 1103 | 2 | B | 19.0.0 | Rel-19 | Support of IMS AS registration to NRF |
C4-245479
| agreed | CT4#126 | Huawei |
CP-243045
| | CT#106 | CT4 | | NG_RTC_Ph2 |
|
|
| 29.510 | 1103 | 1 | B | 19.0.0 | Rel-19 | Support of IMS AS registration to NRF |
C4-245351
| revised | CT4#126 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.510 | 1103 | - | B | 19.0.0 | Rel-19 | Support of IMS AS registration to NRF |
C4-245157
| revised | CT4#126 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1429 | 1 | B | 19.0.0 | Rel-19 | IMS Event Exposure Services OpenAPI file definition |
C3-246434
| agreed | CT3#138 | Nokia, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1429 | - | B | 19.0.0 | Rel-19 | IMS Event Exposure (EE) Services OpenAPI |
C3-246116
| revised | CT3#138 | Nokia |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1428 | 1 | B | 19.0.0 | Rel-19 | IMS Event Exposure API definitions and data model |
C3-246462
| agreed | CT3#138 | Nokia, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1428 | - | B | 19.0.0 | Rel-19 | IMS Event Exposure (EE) Services operations and data model |
C3-246115
| revised | CT3#138 | Nokia |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1427 | 1 | B | 19.0.0 | Rel-19 | IMS Event Exposure Service descriptions and procedures |
C3-246461
| agreed | CT3#138 | Nokia, Ericsson |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1427 | - | B | 19.0.0 | Rel-19 | IMS Event Exposure(EE) Services description |
C3-246114
| revised | CT3#138 | Nokia |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1426 | 2 | B | 19.0.0 | Rel-19 | Definition of Nnef_ImsSessionManagement Service |
C3-246510
| agreed | CT3#138 | Huawei, Nokia |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1426 | 1 | B | 19.0.0 | Rel-19 | Definition of Nnef_ImsSessionManagement Service |
C3-246460
| revised | CT3#138 | Huawei |
| | | | | NG_RTC_Ph2 |
|
|
| 29.522 | 1426 | - | B | 19.0.0 | Rel-19 | Definition of Nnef_ImsSessionManagement Service |
C3-246109
| revised | CT3#138 | Huawei |
| | | | | NG_RTC_Ph2 |
|