|
|
| 23.003 | 0697 | - | F | 18.5.0 | Rel-18 | SUCI format |
C4-241077
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 23.003 | 0692 | 1 | F | 18.4.0 | Rel-18 | Structure of APN |
C4-240616
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 23.003 | 0692 | - | F | 18.4.0 | Rel-18 | Structure of APN |
C4-240093
| revised | CT4#121 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 23.527 | 0065 | 1 | B | 18.0.0 | Rel-18 | Prefix in Callback URIs |
C4-233520
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 23.527 | 0065 | - | B | 18.0.0 | Rel-18 | API prefix in Callback URIs |
C4-233149
| revised | CT4#117 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 23.632 | 0042 | 1 | F | 18.1.0 | Rel-18 | UE Memory Available |
C4-231433
| agreed | CT4#115-e | Hewlett-Packard... |
CP-231027
| approved | CT#100 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 23.632 | 0042 | - | B | 18.1.0 | Rel-18 | UE Memory Available |
C4-231203
| revised | CT4#115-e | Hewlett-Packard... |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0022 | 1 | F | 18.3.0 | Rel-18 | Callbacks |
C4-241321
| agreed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0022 | - | F | 18.3.0 | Rel-18 | Callbacks |
C4-241072
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0021 | - | F | 18.2.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-235305
| agreed | CT4#119 | Huawei |
CP-233030
| approved | CT#102 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.256 | 0020 | - | F | 18.2.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9113 |
C4-234212
| agreed | CT4#118 | Huawei |
CP-233027
| approved | CT#102 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | 5 | F | 18.0.0 | Rel-18 | Location header and missing Redirection clause |
C4-231414
| agreed | CT4#115-e | Huawei |
CP-231027
| approved | CT#100 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | 4 | F | 18.0.0 | Rel-18 | Location header and missing Redirection clause |
C4-231380
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | 3 | F | 18.0.0 | Rel-18 | Location header and missing Redirection clause |
C4-231039
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | 2 | F | 17.3.0 | Rel-18 | Adding missing HTTP redirection clause |
C4-230785
| postponed | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | 1 | F | 17.3.0 | Rel-18 | Adding missing HTTP redirection clause |
C4-230699
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.256 | 0013 | - | F | 17.3.0 | Rel-18 | Location header in a redirect response |
C4-230384
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.272 | 0851 | 2 | F | 18.2.0 | Rel-18 | NR as Secondary RAT feature over S6a interface |
C4-240793
| postponed | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.272 | 0851 | 1 | F | 18.2.0 | Rel-18 | NR as Secondary RAT feature over S6a interface |
C4-240766
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.272 | 0851 | - | F | 18.2.0 | Rel-18 | NR as Secondary RAT feature over S6a interface |
C4-240523
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.272 | 0845 | 1 | F | 18.1.0 | Rel-18 | Update on Group-Service-Id |
C4-233729
| withdrawn | CT4#117 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.272 | 0845 | - | F | 18.1.0 | Rel-18 | Update on Group-Service-Id |
C4-233414
| revised | CT4#117 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.273 | 0545 | - | F | 18.2.0 | Rel-18 | Update on AAA Command for Core-Network Restriction |
C4-233415
| agreed | CT4#117 | Huawei |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0011 | - | F | 18.0.0 | Rel-18 | Editorial and Style Corrections |
C4-235273
| agreed | CT4#119 | Ericsson |
CP-233030
| approved | CT#102 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0010 | 2 | F | 18.0.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-234509
| agreed | CT4#118 | Ericsson |
CP-233029
| approved | CT#102 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0010 | 1 | F | 18.0.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-234429
| withdrawn | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.309 | 0010 | - | B | 18.0.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-234153
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.309 | 0009 | 1 | B | 18.0.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |
C4-234506
| agreed | CT4#118 | Ericsson |
CP-233028
| approved | CT#102 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0009 | - | B | 18.0.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |
C4-234146
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.309 | 0008 | - | F | 18.0.0 | Rel-18 | Location header description |
C4-234022
| agreed | CT4#118 | Huawei |
CP-233027
| approved | CT#102 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0007 | 1 | F | 18.0.0 | Rel-18 | Default values of privateIdRequest and gbaUAware |
C4-234500
| agreed | CT4#118 | Huawei |
CP-233028
| approved | CT#102 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.309 | 0007 | - | F | 18.0.0 | Rel-18 | Default values of privateIdRequest and gbaUAware |
C4-234021
| revised | CT4#118 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.309 | 0005 | - | B | 17.1.0 | Rel-18 | OAuth2 scopes in the Nbsp_GBA API |
C4-233030
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.486 | 0092 | 1 | F | 18.0.0 | Rel-18 | Adding missing presence conditions |
C3-231502
| postponed | CT3#127-e | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.486 | 0092 | - | F | 18.0.0 | Rel-18 | Adding missing presence conditions |
C3-231127
| revised | CT3#127-e | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0430 | - | B | 18.5.0 | Rel-18 | Support of UNSUPPORTED_MONITORING_EVENT_TYPE error |
C4-241266
| not pursued | CT4#122 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0429 | 1 | F | 18.5.0 | Rel-18 | SBI Message Priority in a Response message |
C4-241326
| withdrawn | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0429 | - | F | 18.5.0 | Rel-18 | SBI Message Priority in a Response message |
C4-241229
| revised | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0428 | 1 | F | 18.5.0 | Rel-18 | Indication of Intermediate NF |
C4-242048
| | CT4#123 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0428 | - | F | 18.5.0 | Rel-18 | Indication of Intermediate NF |
C4-241156
| revised | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0427 | - | F | 18.5.0 | Rel-18 | Expected Message Priority for Resource or Context |
C4-241155
| postponed | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0426 | 1 | F | 18.5.0 | Rel-18 | Header case |
C4-242012
| | CT4#123 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0426 | - | F | 18.5.0 | Rel-18 | Header case |
C4-241078
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0425 | - | F | 18.4.0 | Rel-18 | NoProfileMatchInfo caching in SCPs |
C4-240546
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0424 | 1 | F | 18.4.0 | Rel-18 | Redundant clause removal |
C4-240572
| agreed | CT4#121 | Huawei, Nokia, ... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0424 | - | F | 18.4.0 | Rel-18 | Redundant clause removal |
C4-240322
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0421 | 3 | F | 18.4.0 | Rel-18 | Error description in 401 Unauthorized response |
C4-240848
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0421 | 2 | F | 18.4.0 | Rel-18 | Error description in 401 Unauthorized response |
C4-240794
| revised | CT4#121 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0421 | 1 | F | 18.4.0 | Rel-18 | Error description in 401 Unauthorized response |
C4-240571
| revised | CT4#121 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0421 | - | F | 18.4.0 | Rel-18 | Error description in 401 Unauthorized response |
C4-240268
| revised | CT4#121 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0420 | 2 | B | 18.4.0 | Rel-18 | New application error for the HTTP status code 403 |
C4-240798
| agreed | CT4#121 | Huawei |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0420 | 1 | B | 18.4.0 | Rel-18 | New application error for the HTTP status code 403 |
C4-240570
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0420 | - | B | 18.4.0 | Rel-18 | New application error for the HTTP status code 403 |
C4-240238
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0419 | - | B | 18.4.0 | Rel-18 | Add an application Error due to the NF is not reachable via the selected SEPP |
C4-240230
| postponed | CT4#121 | NTT DOCOMO |
| | | | | TEI18, SBIProto... |
|
|
|
| 29.500 | 0418 | - | F | 18.4.0 | Rel-18 | 3GPP SBI callback type values |
C4-240221
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0417 | - | F | 18.4.0 | Rel-18 | Extensions to the 3gpp-Sbi-Request-Info header |
C4-240158
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0416 | - | F | 18.4.0 | Rel-18 | SCP handling of 3xx redirect messages |
C4-240157
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0415 | 1 | F | 18.4.0 | Rel-18 | Note referring to an incorrect header name |
C4-240567
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0415 | - | F | 18.4.0 | Rel-18 | Note referring to an incorrect header name |
C4-240156
| revised | CT4#121 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0412 | - | F | 18.3.0 | Rel-18 | Encoding for String Type JSON Attributes |
C4-235411
| agreed | CT4#119 | ZTE |
CP-233031
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0409 | - | F | 18.3.0 | Rel-18 | Correction on the general description for overload |
C4-235185
| agreed | CT4#119 | Ericsson |
CP-233030
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0408 | 1 | F | 18.3.0 | Rel-18 | Reserved characters in JSON attributes defined as URI and in HTTP header parameters defined as URI or path-absolute |
C4-235412
| agreed | CT4#119 | Nokia, Nokia Sh... |
CP-233031
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0408 | - | F | 18.3.0 | Rel-18 | Reserved characters in JSON attributes defined as URI and in HTTP header parameters defined as URI or path-absolute |
C4-235097
| revised | CT4#119 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0407 | 1 | F | 18.3.0 | Rel-18 | ABNF Corrections |
C4-234438
| agreed | CT4#118 | Ericsson |
CP-233028
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0407 | - | F | 18.3.0 | Rel-18 | ABNF Corrections |
C4-234412
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0404 | - | F | 18.3.0 | Rel-18 | HTTP requests redirected by SEPP |
C4-234099
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233027
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0403 | - | B | 18.3.0 | Rel-18 | ABNF definition and example of callback-uri-prefix in 3gpp-Sbi-Request-Info header |
C4-234097
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233027
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0402 | 1 | F | 18.3.0 | Rel-18 | Incorrect references to HTTP RFC 7230 obsoleted by IETF RFC 9110 |
C4-234424
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233028
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0402 | - | B | 18.3.0 | Rel-18 | Incorrect references to HTTP RFC 7230 obsoleted by IETF RFC 9110 |
C4-234094
| revised | CT4#118 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0400 | 2 | F | 18.2.0 | Rel-18 | 504 Gateway Timeout response including the "problemDetails" |
C4-233792
| agreed | CT4#117 | Huawei |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0400 | 1 | F | 18.2.0 | Rel-18 | 504 Gateway Timeout response including the "problemDetails" |
C4-233593
| revised | CT4#117 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0398 | - | F | 18.2.0 | Rel-18 | Correction on NRF API URI |
C4-233433
| agreed | CT4#117 | Huawei |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0387 | 1 | B | 18.2.0 | Rel-18 | Prefix in Callback URIs |
C4-233517
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0387 | - | B | 18.2.0 | Rel-18 | API prefix in Callback URIs |
C4-233146
| revised | CT4#117 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0386 | 1 | B | 18.2.0 | Rel-18 | Access token with additional scopes for indirect com. with delegated discovery |
C4-233514
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0386 | - | B | 18.2.0 | Rel-18 | Access token with additional scopes for indirect com. with delegated discovery |
C4-233143
| revised | CT4#117 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0385 | - | B | 18.2.0 | Rel-18 | Binding indication with "other-service" scope from AMF to SMSF and PCF |
C4-233142
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0384 | - | B | 18.2.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |
C4-233141
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0382 | 4 | F | 18.1.0 | Rel-18 | Correction of ABNF rules |
C4-232344
| agreed | CT4#116 | Ericsson, Nokia... |
CP-231029
| approved | CT#100 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0382 | 3 | F | 18.1.0 | Rel-18 | Correction of ABNF rules |
C4-232336
| revised | CT4#116 | Ericsson, Nokia... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0382 | 2 | F | 18.1.0 | Rel-18 | Correction of ABNF rules |
C4-232180
| revised | CT4#116 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0382 | 1 | F | 18.1.0 | Rel-18 | Correction of ABNF rules |
C4-231486
| revised | CT4#115-e | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0382 | - | F | 18.1.0 | Rel-18 | Correction of ABNF rules |
C4-231307
| revised | CT4#115-e | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0379 | - | B | 18.1.0 | Rel-18 | Max Processing Time Informaiton by NF as HTTP server |
C4-231282
| postponed | CT4#115-e | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0375 | - | F | 18.0.0 | Rel-18 | Binding created as part of a service request |
C4-230406
| agreed | CT4#114 | Huawei |
CP-230029
| approved | CT#99 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0374 | - | F | 18.0.0 | Rel-18 | Location header in a redirect response |
C4-230369
| postponed | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0373 | - | F | 18.0.0 | Rel-18 | New application error to indicate next hop not reachable |
C4-230245
| postponed | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0369 | - | D | 18.0.0 | Rel-18 | Add recommendation to define Operation/Resource level scopes |
C4-230114
| withdrawn | CT4#114 | Samsung |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0365 | 3 | F | 17.8.0 | Rel-18 | Clarification on error handling at SEPP |
C4-225647
| agreed | CT4#113 | NTT DOCOMO INC. |
CP-223029
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0365 | 2 | F | 17.8.0 | Rel-18 | Clarification on error handling at SEPP |
C4-225547
| revised | CT4#113 | NTT DOCOMO INC. |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0365 | 1 | F | 17.8.0 | Rel-18 | Clarification on error handling at SEPP |
C4-225407
| revised | CT4#113 | NTT DOCOMO INC. |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0362 | - | F | 17.8.0 | Rel-18 | Standalone Notifications |
C4-225305
| agreed | CT4#113 | Ericsson |
CP-223027
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0361 | - | B | 17.8.0 | Rel-18 | Optional support of 100 Continue response |
C4-225177
| postponed | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0360 | 2 | F | 17.8.0 | Rel-18 | Extending the 3gpp-Sbi-Nrf-Callback URI with the NRF NFManagement API URI |
C4-225570
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223029
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0360 | 1 | F | 17.8.0 | Rel-18 | Extending the 3gpp-Sbi-Nrf-Callback URI with the NRF NFManagement API URI |
C4-225404
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0360 | - | F | 17.8.0 | Rel-18 | Extending the 3gpp-Sbi-Nrf-Callback URI with the NRF NFManagement API URI |
C4-225176
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0359 | 1 | F | 17.8.0 | Rel-18 | Extending the problem details with supported API versions |
C4-225402
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223027
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0359 | - | F | 17.8.0 | Rel-18 | Extending the problem details with supported API versions |
C4-225173
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0357 | 1 | F | 17.8.0 | Rel-18 | Feature negotiation for subscriptions to notifications occuring via an indirect path |
C4-225481
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223028
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0357 | - | F | 17.8.0 | Rel-18 | Feature negotiation for subscriptions to notifications occuring via an indirect path |
C4-225139
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0356 | 2 | F | 17.8.0 | Rel-18 | Restricting SCP to perform retries |
C4-225650
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223029
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0356 | 1 | F | 17.8.0 | Rel-18 | Restricting SCP to perform retries |
C4-225485
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0356 | - | F | 17.8.0 | Rel-18 | Restricting SCP to perform retries |
C4-225137
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.500 | 0355 | 1 | F | 17.8.0 | Rel-18 | Notification error handling |
C4-225386
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223027
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.500 | 0355 | - | F | 17.8.0 | Rel-18 | Notification error handling |
C4-225136
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0155 | 1 | F | 18.4.0 | Rel-18 | HTTP Multipart message support in PATCH Request |
C4-241329
| agreed | CT4#122 | Microsoft EUROP... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0155 | - | D | 18.4.0 | Rel-18 | HTTP Multipart message support in PATCH Request |
C4-241298
| revised | CT4#122 | Microsoft EUROP... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0154 | 1 | F | 18.4.0 | Rel-18 | Query Parameter clarification |
C4-241324
| agreed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0154 | - | F | 18.4.0 | Rel-18 | Query Parameter clarification |
C4-241079
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0153 | - | F | 18.4.0 | Rel-18 | OAuth Scope for Subscription and Notification |
C4-240049
| withdrawn | CT4#121 | ZTE |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0152 | - | F | 18.4.0 | Rel-18 | Handling of absent boolean attribute in CREATE operation |
C4-240048
| not pursued | CT4#121 | ZTE |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0151 | - | F | 18.3.0 | Rel-18 | Case-insensitive hexadecimal encoding |
C4-235252
| agreed | CT4#119 | Ericsson |
CP-233030
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0149 | 1 | B | 18.3.0 | Rel-18 | Update of SBI TS skeleton template |
C4-234430
| agreed | CT4#118 | Ericsson |
CP-233028
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0149 | - | B | 18.3.0 | Rel-18 | Update of SBI TS skeleton template |
C4-234157
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0148 | 1 | F | 18.3.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-234428
| agreed | CT4#118 | Ericsson |
CP-233028
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0148 | - | B | 18.3.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-234152
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0145 | - | B | 18.2.0 | Rel-18 | Uptade of the template to add ABNF |
C4-233624
| agreed | CT4#117 | Ericsson |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0144 | 1 | F | 18.2.0 | Rel-18 | Correct SBI stage 3 template for custom operations without resources |
C4-233623
| agreed | CT4#117 | CATT |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0144 | - | F | 18.2.0 | Rel-18 | Correct SBI stage 3 template for custom operations without resources |
C4-233296
| revised | CT4#117 | CATT |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0143 | - | B | 18.2.0 | Rel-18 | Documentation of 3GPP Custom HTTP Headers |
C4-233266
| agreed | CT4#117 | Ericsson |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0142 | 2 | B | 18.2.0 | Rel-18 | Prefix in Callback URIs |
C4-233798
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0142 | 1 | B | 18.2.0 | Rel-18 | Prefix in Callback URIs |
C4-233518
| revised | CT4#117 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0142 | - | B | 18.2.0 | Rel-18 | API prefix in Callback URIs |
C4-233147
| revised | CT4#117 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0141 | - | B | 18.1.0 | Rel-18 | OAuth2 scopes in the Nmbsmf_TMGI API |
C4-231298
| withdrawn | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0140 | 1 | B | 18.1.0 | Rel-18 | Adding Redirection clause to SBI template |
C4-231413
| agreed | CT4#115-e | Huawei |
CP-231026
| approved | CT#100 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0140 | - | B | 18.1.0 | Rel-18 | Adding Redirection clause to SBI template |
C4-231066
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0139 | - | F | 18.0.0 | Rel-18 | Correction of the NO-$REF SIBLINGS error for nullable attributes within PATCH method |
C4-230381
| agreed | CT4#114 | Ericsson |
CP-230029
| approved | CT#99 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0138 | 1 | F | 18.0.0 | Rel-18 | Guidelines for OAuth2 scopes definition |
C4-230507
| agreed | CT4#114 | Nokia, Nokia Sh... |
CP-230029
| approved | CT#99 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0138 | - | F | 18.0.0 | Rel-18 | Guidelines for OAuth2 scopes definition |
C4-230170
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0137 | 2 | F | 18.0.0 | Rel-18 | Maximum number of leaves |
C4-230786
| agreed | CT4#114 | Nokia, Nokia Sh... |
CP-230090
| approved | CT#99 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0134 | 1 | D | 18.0.0 | Rel-18 | Editorial modifications to the rules for incrementing API version |
C4-230504
| agreed | CT4#114 | Huawei |
CP-230029
| approved | CT#99 | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0134 | - | D | 18.0.0 | Rel-18 | Rules for incrementing API version field values |
C4-230059
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0133 | 2 | F | 18.1.0 | Rel-18 | Rules for incrementing API version field values |
C4-231482
| agreed | CT4#115-e | Huawei |
CP-231027
| approved | CT#100 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0133 | 1 | F | 18.1.0 | Rel-18 | Rules for incrementing API version field values |
C4-231185
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0133 | - | F | 18.0.0 | Rel-18 | Rules for incrementing API version field values |
C4-230029
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.501 | 0132 | - | F | 17.7.0 | Rel-18 | Standalone Notifications |
C4-225307
| agreed | CT4#113 | Ericsson |
CP-223027
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0131 | 1 | F | 17.7.0 | Rel-18 | Description fields in enumerations |
C4-225540
| agreed | CT4#113 | Ericsson |
CP-223029
| approved | CT#98-e | CT4 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.501 | 0131 | - | F | 17.7.0 | Rel-18 | Description fields in enumerations |
C4-225303
| revised | CT4#113 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0779 | - | F | 18.6.0 | Rel-18 | 504 Gateway Timeout in Update SM Context procedure |
C4-242116
| | CT4#123 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0765 | - | F | 18.6.0 | Rel-18 | Features supported by the Anchor SMF |
C4-241106
| agreed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0728 | - | D | 18.4.0 | Rel-18 | Editorial correction on the name of Remote UE Report Response |
C4-235277
| agreed | CT4#119 | CATT |
CP-233030
| approved | CT#102 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0726 | - | D | 18.4.0 | Rel-18 | Editorial correction on the name of Remote UE Report Response |
C4-235241
| withdrawn | CT4#119 | CATT |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0725 | - | B | 18.4.0 | Rel-18 | VPLLMN QoS Constraints supporting Multiple 5QIs |
C4-235215
| postponed | CT4#119 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0724 | 1 | B | 18.4.0 | Rel-18 | Roaming UE Indication for Emergency Session |
C4-235512
| agreed | CT4#119 | Ericsson |
CP-233031
| approved | CT#102 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0724 | - | B | 18.4.0 | Rel-18 | Roaming UE Indication for Emergency Session |
C4-235214
| revised | CT4#119 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0719 | - | F | 18.4.0 | Rel-18 | ProblemDetails RFC 7807 obsoleted by 9457 |
C4-235096
| agreed | CT4#119 | Nokia, Nokia Sh... |
CP-233030
| approved | CT#102 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0712 | 2 | B | 18.4.0 | Rel-18 | Indication of PDU Session Establishment Rejection |
C4-234634
| agreed | CT4#118 | Ericsson |
CP-233029
| approved | CT#102 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0712 | 1 | B | 18.4.0 | Rel-18 | Indication of PDU Session Establishment Rejection |
C4-234453
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0712 | - | B | 18.4.0 | Rel-18 | Indication of PDU Session Establishment Rejection |
C4-234292
| revised | CT4#118 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0696 | 1 | F | 18.4.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |
C4-234451
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233028
| approved | CT#102 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0696 | - | B | 18.4.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |
C4-234092
| revised | CT4#118 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0677 | - | B | 18.3.0 | Rel-18 | Time Critical Service Handling during Signling Conflicting via N16/N16a |
C4-233325
| not pursued | CT4#117 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0676 | 4 | B | 18.3.0 | Rel-18 | Avoidance of unnecessary interworking on N16 and N16a |
| | | |
CP-232150
| approved | CT#101 | Ericsson | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0676 | 3 | B | 18.3.0 | Rel-18 | Avoidance of unnecessary interworking on N16 and N16a |
C4-233875
| revised | CT4#117 | Ericsson |
CP-232033
| revised | CT#101 | CT4 | | SBIProtoc18 |
|
|
|
| 29.502 | 0676 | 2 | B | 18.3.0 | Rel-18 | Avoidance of unnecessary interworking on N16 and N16a |
C4-233801
| revised | CT4#117 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0676 | 1 | B | 18.3.0 | Rel-18 | Avoidance of unnecessary interworking on N16 and N16a |
C4-233548
| revised | CT4#117 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0676 | - | B | 18.3.0 | Rel-18 | Avoidance of unnecessary interworking on N16 and N16a |
C4-233324
| revised | CT4#117 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0673 | - | F | 18.3.0 | Rel-18 | Correction of ABNF rule of 3gpp-Sbi-Origination-Timestamp header |
C4-233145
| agreed | CT4#117 | Nokia, Nokia Sh... |
CP-232033
| approved | CT#101 | CT4 | 18.4.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0653 | - | F | 18.2.0 | Rel-18 | Clarification on the release of duplicated PDU Session |
C4-232122
| agreed | CT4#116 | CATT, Ericsson |
CP-231028
| approved | CT#100 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0649 | - | F | 18.2.0 | Rel-18 | Clarification on DNN inclusion during EPS to 5GS mobility for roaming subscriber. |
C4-231369
| withdrawn | CT4#115-e | Microsoft EUROP... |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | 5 | F | 18.2.0 | Rel-18 | Location header description |
C4-231587
| agreed | CT4#115-e | Huawei |
CP-231028
| approved | CT#100 | CT4 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | 4 | F | 18.2.0 | Rel-18 | Location header description |
C4-231576
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | 3 | F | 18.2.0 | Rel-18 | Location header description |
C4-231403
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | 2 | F | 18.2.0 | Rel-18 | Location header description |
C4-231056
| revised | CT4#115-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | 1 | F | 18.1.0 | Rel-18 | Adding SEPP to RedirectResponse |
C4-230569
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0629 | - | F | 18.1.0 | Rel-18 | Location header in a redirect response |
C4-230371
| revised | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0624 | 1 | B | 18.1.0 | Rel-18 | Vplmn QoS Flow Rejection |
C4-230519
| agreed | CT4#114 | Ericsson |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0624 | - | B | 18.1.0 | Rel-18 | Vplmn QoS Flow Rejection |
C4-230315
| revised | CT4#114 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0623 | 1 | B | 18.1.0 | Rel-18 | Retry Timer via N16/N16a |
C4-230517
| agreed | CT4#114 | Ericsson |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0623 | - | B | 18.1.0 | Rel-18 | Retry Timer via N16/N16a |
C4-230314
| revised | CT4#114 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0619 | 1 | B | 18.1.0 | Rel-18 | Populating Group ID during 4G to 5G mobility |
C4-230516
| agreed | CT4#114 | Ericsson |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0619 | - | B | 18.1.0 | Rel-18 | Populating Group ID during 4G to 5G mobility |
C4-230252
| revised | CT4#114 | Ericsson LM |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0618 | 1 | F | 18.1.0 | Rel-18 | SM context / PDU session release cause for Mobility or Access Restrictions |
C4-230515
| agreed | CT4#114 | Nokia, Nokia Sh... |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0618 | - | F | 18.1.0 | Rel-18 | SM context / PDU session release cause for Mobility or Access Restrictions |
C4-230251
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0612 | - | F | 18.1.0 | Rel-18 | Strings with Base64-encoded characters |
C4-230173
| agreed | CT4#114 | Nokia, Nokia Sh... |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0610 | 1 | F | 18.1.0 | Rel-18 | Status code 504 in Create Response |
C4-230523
| agreed | CT4#114 | Huawei |
CP-230029
| approved | CT#99 | CT4 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0608 | - | F | 18.1.0 | Rel-18 | Missing Mandatory Status Codes in OpenAPI |
C4-230024
| withdrawn | CT4#114 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.502 | 0589 | 1 | F | 18.0.0 | Rel-18 | Missing mandatory status codes in OpenAPI |
C4-225488
| agreed | CT4#113 | Nokia, Nokia Sh... |
CP-223029
| approved | CT#98-e | CT4 | 18.1.0 | SBIProtoc18 |
|
|
|
| 29.502 | 0589 | - | F | 18.0.0 | Rel-18 | Missing mandatory status codes in OpenAPI |
C4-225142
| revised | CT4#113 | Nokia, Nokia Sh... |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1264 | - | F | 18.5.0 | Rel-18 | Remove additional application error |
C4-242208
| | CT4#123 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1255 | 2 | F | 18.5.0 | Rel-18 | Missing Description fields in Nudm_UECM API definition |
C4-242242
| | CT4#123 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1255 | 1 | F | 18.5.0 | Rel-18 | Missing Description fields in Nudm_UECM API definition |
C4-241412
| revised | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1255 | - | F | 18.5.0 | Rel-18 | Missing Description fields in Nudm_UECM API definition |
C4-241296
| revised | CT4#122 | Ericsson |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1240 | 3 | F | 18.5.0 | Rel-18 | Subscribe failure clarification |
C4-241476
| agreed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1240 | 2 | F | 18.5.0 | Rel-18 | Subscribe failure clarification |
C4-241466
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1240 | 1 | F | 18.5.0 | Rel-18 | Subscribe failure clarification |
C4-241406
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1240 | - | F | 18.5.0 | Rel-18 | Subscribe failure clarification |
C4-241087
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1238 | 2 | F | 18.5.0 | Rel-18 | Presence condition for PGW FQDN and IP address in SMF registration |
C4-241465
| postponed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1238 | 1 | F | 18.5.0 | Rel-18 | Presence condition for PGW FQDN and IP address in SMF registration |
C4-241405
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1238 | - | F | 18.5.0 | Rel-18 | Presence condition for PGW FQDN and IP address in SMF registration |
C4-241080
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1237 | 1 | F | 18.5.0 | Rel-18 | Callbacks |
C4-241322
| agreed | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1237 | - | F | 18.5.0 | Rel-18 | Callbacks |
C4-241073
| revised | CT4#122 | Nokia |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1230 | 2 | F | 18.4.0 | Rel-18 | Clarification on maxNumOfReports and expiry |
C4-240783
| agreed | CT4#121 | Huawei |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.503 | 1230 | 1 | F | 18.4.0 | Rel-18 | Clarification on maxNumOfReports and expiry |
C4-240728
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1230 | - | F | 18.4.0 | Rel-18 | Clarification on maxNumOfReports and expiry |
C4-240524
| revised | CT4#121 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1218 | - | F | 18.4.0 | Rel-18 | MDT User Consent for PLMNs adjacent to the serving PLMN |
C4-240234
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.503 | 1217 | - | F | 18.4.0 | Rel-18 | Shared Trace Data |
C4-240226
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.503 | 1216 | - | F | 18.4.0 | Rel-18 | Registration Time Stamp |
C4-240225
| agreed | CT4#121 | Nokia, Nokia Sh... |
CP-240028
| approved | CT#103 | CT4 | 18.5.0 | SBIProtoc18 |
|
|
|
| 29.503 | 1196 | 1 | F | 18.3.0 | Rel-18 | Updates on the description of default value |
C4-235451
| not pursued | CT4#119 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.503 | 1196 | - | F | 18.3.0 | Rel-18 | Updates on the description of default value |
C4-235306
| revised | CT4#119 | Huawei |
| | | | | SBIProtoc18 |
|