|
| 29.501 | 0175 | - | A | 18.6.0 | Rel-18 | Query parameter clarification |
C4-245309
| agreed | CT4#126 | Nokia |
CP-243050
| | CT#106 | CT4 | | 5GS_Ph1-CT |
|
|
| 29.501 | 0174 | - | A | 17.8.0 | Rel-17 | Query parameter clarification |
C4-245308
| agreed | CT4#126 | Nokia |
CP-243050
| | CT#106 | CT4 | | 5GS_Ph1-CT |
|
|
| 29.501 | 0173 | - | A | 16.7.0 | Rel-16 | Query parameter clarification |
C4-245307
| agreed | CT4#126 | Nokia |
CP-243050
| | CT#106 | CT4 | | 5GS_Ph1-CT |
|
|
| 29.501 | 0172 | - | F | 15.8.0 | Rel-15 | Query parameter clarification |
C4-245306
| agreed | CT4#126 | Nokia |
CP-243050
| | CT#106 | CT4 | | 5GS_Ph1-CT |
|
|
| 29.501 | 0171 | 1 | F | 19.0.0 | Rel-19 | Presence condition in an Information Element |
C4-245318
| agreed | CT4#126 | Ericsson |
CP-243035
| | CT#106 | CT4 | | SBIProtoc19 |
|
|
| 29.501 | 0171 | - | F | 19.0.0 | Rel-19 | Presence condition in an Information Element |
C4-245225
| revised | CT4#126 | Ericsson |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0170 | 1 | A | 19.0.0 | Rel-19 | Query parameter clarification |
C4-245310
| agreed | CT4#126 | Nokia |
CP-243050
| | CT#106 | CT4 | | 5GS_Ph1-CT |
|
|
| 29.501 | 0170 | - | F | 19.0.0 | Rel-19 | Query parameter clarification |
C4-245104
| revised | CT4#126 | Nokia |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0169 | - | A | 19.0.0 | Rel-19 | Missing clause |
C4-244282
| merged | CT4#125 | Ericsson, MCC |
| | | | | SBIProtoc18 |
|
|
| 29.501 | 0168 | - | F | 18.6.0 | Rel-18 | Missing clause |
C4-244281
| merged | CT4#125 | Ericsson, MCC |
| | | | | SBIProtoc18 |
|
|
| 29.501 | 0167 | 1 | D | 19.0.0 | Rel-19 | Editorial Corrections |
C4-244345
| agreed | CT4#125 | Ericsson |
CP-243032
| | CT#106 | CT4 | | TEI19 |
|
|
| 29.501 | 0167 | - | F | 19.0.0 | Rel-19 | Editorial Corrections |
C4-244280
| revised | CT4#125 | Ericsson |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0166 | 1 | F | 19.0.0 | Rel-19 | Clarification on missing abbreviations |
C4-244463
| agreed | CT4#125 | Huawei |
CP-243032
| | CT#106 | CT4 | | TEI19 |
|
|
| 29.501 | 0166 | - | F | 19.0.0 | Rel-19 | Clarification on missing abbreviations |
C4-244277
| revised | CT4#125 | Huawei |
| | | | | TEI19 |
|
|
| 29.501 | 0165 | 1 | A | 19.0.0 | Rel-19 | Restore deleted clause |
C4-244333
| agreed | CT4#125 | Nokia, MCC, Ericsson |
CP-243022
| | CT#106 | CT4 | | TEI18 |
|
|
| 29.501 | 0165 | - | A | 19.0.0 | Rel-19 | Restore deleted clause |
C4-244202
| revised | CT4#125 | Nokia, MCC |
| | | | | TEI18 |
|
|
| 29.501 | 0164 | 1 | F | 18.6.0 | Rel-18 | Restore deleted clause |
C4-244332
| agreed | CT4#125 | Nokia, MCC, Ericsson |
CP-243022
| | CT#106 | CT4 | | TEI18 |
|
|
| 29.501 | 0164 | - | F | 18.6.0 | Rel-18 | Restore deleted clause |
C4-244201
| revised | CT4#125 | Nokia, MCC |
| | | | | TEI18 |
|
|
| 29.501 | 0163 | 1 | F | 19.0.0 | Rel-19 | OpenAPI definition of boolean with false value prohibited |
C4-244250
| agreed | CT4#125 | Huawei, China Mobile |
CP-243035
| | CT#106 | CT4 | | SBIProtoc19 |
|
|
| 29.501 | 0163 | - | F | 19.0.0 | Rel-19 | OpenAPI definition of boolean with false value prohibited |
C4-244080
| revised | CT4#125 | Huawei, China Mobile |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0162 | - | F | 18.5.0 | Rel-18 | HTTP RFCs obsoleted by IETF RFC 9110 and 9113 |
C4-243275
| agreed | CT4#124 | Huawei |
CP-242039
| approved | CT#105 | CT4 | 18.6.0 | SBIProtoc18 |
|
|
| 29.501 | 0161 | 2 | F | 18.5.0 | Rel-19 | Update of the template for the HTTP RFC obsoleted by IETF RFC 9113 |
C4-243415
| agreed | CT4#124 | Huawei |
CP-242030
| approved | CT#105 | CT4 | 19.0.0 | SBIProtoc19 |
|
|
| 29.501 | 0161 | 1 | F | 18.5.0 | Rel-18 | Update of the template for the HTTP RFC obsoleted by IETF RFC 9113 |
C4-243382
| revised | CT4#124 | Huawei |
| | | | | SBIProtoc18 |
|
|
| 29.501 | 0161 | - | F | 18.5.0 | Rel-18 | Update of the template for the HTTP RFC obsoleted by IETF RFC 9113 |
C4-243274
| revised | CT4#124 | Ericsson |
| | | | | SBIProtoc18 |
|
|
| 29.501 | 0160 | 1 | F | 18.5.0 | Rel-19 | Correction of reference to an IETF Internet-Draft |
C4-243578
| agreed | CT4#124 | Huawei |
CP-242033
| approved | CT#105 | CT4 | 19.0.0 | TEI19 |
|
|
| 29.501 | 0160 | - | F | 18.5.0 | Rel-19 | Correction of reference to an IETF Internet-Draft |
C4-243150
| revised | CT4#124 | Huawei |
| | | | | TEI19 |
|
|
| 29.501 | 0159 | - | F | 18.5.0 | Rel-19 | Reject Message Reaching Maximum JSON Payload Size |
C4-243063
| withdrawn | CT4#124 | ZTE |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0158 | 1 | F | 18.5.0 | Rel-19 | Subscription expiry |
C4-243526
| agreed | CT4#124 | Nokia |
CP-242030
| approved | CT#105 | CT4 | 19.0.0 | SBIProtoc19 |
|
|
| 29.501 | 0158 | - | F | 18.5.0 | Rel-19 | Subscription expiry |
C4-243050
| revised | CT4#124 | Nokia |
| | | | | SBIProtoc19 |
|
|
| 29.501 | 0157 | - | F | 18.5.0 | Rel-19 | Example correction |
C4-243032
| agreed | CT4#124 | Nokia |
CP-242030
| approved | CT#105 | CT4 | 19.0.0 | SBIProtoc19 |
|
|
| 29.501 | 0156 | 2 | B | 18.5.0 | Rel-19 | Usage of GitLab Repository |
C4-243106
| agreed | CT4#124 | Ericsson |
CP-242033
| approved | CT#105 | CT4 | 19.0.0 | TEI19 |
|
|
| 29.501 | 0156 | 1 | B | 18.4.0 | Rel-19 | Usage of GitLab Repository |
C4-242475
| revised | CT4#123 | Ericsson |
| | | | | TEI19 |
|
|
| 29.501 | 0156 | - | B | 18.4.0 | Rel-19 | Usage of GitLab Repository |
C4-242241
| revised | CT4#123 | Ericsson |
| | | | | TEI19 |
|
|
| 29.501 | 0155 | 1 | F | 18.4.0 | Rel-18 | HTTP Multipart message support in PATCH Request |
C4-241329
| agreed | CT4#122 | Microsoft EUROP... |
CP-241028
| approved | CT#104 | CT4 | 18.5.0 | 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 |
CP-241028
| approved | CT#104 | CT4 | 18.5.0 | 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 | 0150 | 1 | B | 18.3.0 | Rel-18 | Optional usage of 3GPP Forge as normative storage of OpenAPI files |
C4-235279
| agreed | CT4#119 | Ericsson |
CP-233056
| approved | CT#102 | CT4 | 18.4.0 | TEI18 |
|
|
| 29.501 | 0150 | - | F | 18.3.0 | Rel-18 | Optional usage of 3GPP Forge as normative storage of OpenAPI files |
C4-234667
| postponed | CT4#118 | Ericsson |
| | | | | TEI18 |
|
|
| 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 | 0147 | - | A | 18.3.0 | Rel-18 | wrong CR implementation |
C4-234054
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233062
| approved | CT#102 | CT4 | 18.4.0 | SBIProtoc17 |
|
|
| 29.501 | 0146 | - | F | 17.7.0 | Rel-17 | wrong CR implementation |
C4-234053
| agreed | CT4#118 | Nokia, Nokia Sh... |
CP-233062
| approved | CT#102 | CT4 | 17.8.0 | SBIProtoc17 |
|
|
| 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 | 0137 | 1 | A | 18.0.0 | Rel-18 | Maximum number of leaves |
C4-230401
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0137 | - | A | 18.0.0 | Rel-18 | Maximum number of leaves |
C4-230097
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0136 | 2 | A | 17.7.0 | Rel-17 | Maximum number of leaves |
C4-232054
| not pursued | CT4#116 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0136 | 1 | A | 17.7.0 | Rel-17 | Maximum number of leaves |
C4-231102
| postponed | CT4#115-e | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0136 | - | A | 17.7.0 | Rel-17 | Maximum number of leaves |
C4-230096
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0135 | 2 | F | 16.7.0 | Rel-16 | Maximum number of leaves |
C4-232053
| not pursued | CT4#116 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0135 | 1 | F | 16.7.0 | Rel-16 | Maximum number of leaves |
C4-231101
| postponed | CT4#115-e | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0135 | - | F | 16.7.0 | Rel-16 | Maximum number of leaves |
C4-230095
| revised | CT4#114 | Nokia, Nokia Sh... |
| | | | | SBIProtoc16 |
|
|
| 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.501 | 0130 | 1 | F | 17.6.0 | Rel-17 | Limits for number and length of query parameters |
C4-224421
| agreed | CT4#111-e | Huawei |
CP-222026
| approved | CT#97-e | CT4 | 17.7.0 | SBIProtoc17 |
|
|
| 29.501 | 0130 | - | F | 17.6.0 | Rel-17 | Limits for number and length of query parameters |
C4-224321
| revised | CT4#111-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0129 | 1 | A | 17.6.0 | Rel-17 | Essential for Location Header in 201 Response |
C4-224496
| agreed | CT4#111-e | Ericsson |
CP-222070
| approved | CT#97-e | CT4 | 17.7.0 | 5GS_Ph1-CT, TEI16 |
|
|
| 29.501 | 0129 | - | A | 17.6.0 | Rel-17 | Essential for Location Header in 201 Response |
C4-224277
| revised | CT4#111-e | Ericsson |
| | | | | TEI16, 5GS_Ph1-CT |
|
|
| 29.501 | 0128 | 1 | F | 16.6.0 | Rel-16 | Essential for Location Header in 201 Response |
C4-224495
| agreed | CT4#111-e | Ericsson |
CP-222070
| approved | CT#97-e | CT4 | 16.7.0 | 5GS_Ph1-CT, TEI16 |
|
|
| 29.501 | 0128 | - | F | 16.6.0 | Rel-16 | Essential for Location Header in 201 Response |
C4-224276
| revised | CT4#111-e | Ericsson |
| | | | | TEI16, 5GS_Ph1-CT |
|
|
| 29.501 | 0127 | - | F | 17.5.0 | Rel-17 | oAuth2 clarification |
C4-223091
| agreed | CT4#110-e | Nokia, Nokia Sh... |
CP-221028
| approved | CT#96 | CT4 | 17.6.0 | SBIProtoc17 |
|
|
| 29.501 | 0126 | 1 | F | 17.5.0 | Rel-17 | Default logical relationship between query parameters |
C4-223339
| agreed | CT4#110-e | Huawei |
CP-221029
| approved | CT#96 | CT4 | 17.6.0 | SBIProtoc17 |
|
|
| 29.501 | 0126 | - | F | 17.5.0 | Rel-17 | Default logical relationship between query parameters |
C4-223045
| revised | CT4#110-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0125 | - | F | 17.5.0 | Rel-17 | Remove the apiVersion placeholder from the resource URI variables table |
C4-222295
| agreed | CT4#109-e | Huawei |
CP-221027
| approved | CT#96 | CT4 | 17.6.0 | SBIProtoc17 |
|
|
| 29.501 | 0124 | 1 | F | 17.5.0 | Rel-17 | SBI stage 3 template update - Data models |
C4-222310
| agreed | CT4#109-e | Huawei |
CP-221027
| approved | CT#96 | CT4 | 17.6.0 | SBIProtoc17 |
|
|
| 29.501 | 0124 | - | F | 17.5.0 | Rel-17 | SBI stage 3 template update - Data models |
C4-222080
| revised | CT4#109-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0123 | 1 | F | 17.5.0 | Rel-17 | SBI stage 3 template update - OpenAPI |
C4-222307
| agreed | CT4#109-e | Huawei |
CP-221027
| approved | CT#96 | CT4 | 17.6.0 | SBIProtoc17 |
|
|
| 29.501 | 0123 | - | F | 17.5.0 | Rel-17 | SBI stage 3 template update - OpenAPI |
C4-222074
| revised | CT4#109-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0122 | - | F | 17.4.1 | Rel-17 | URL Encoding |
C4-221204
| agreed | CT4#108-e | Ericsson |
CP-220024
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0121 | 1 | F | 17.4.1 | Rel-17 | Notification Clarification |
C4-221569
| agreed | CT4#108-e | Hewlett-Packard... |
CP-220025
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0121 | - | F | 17.4.1 | Rel-17 | Notification Clarification |
C4-221198
| revised | CT4#108-e | Hewlett-Packard... |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0120 | 1 | D | 17.4.1 | Rel-17 | Miscellaneous corrections to the 5GC SBI TS Skeleton |
C4-220447
| agreed | CT4#107-bis-e | Huawei |
CP-220024
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0120 | - | F | 17.4.1 | Rel-17 | Miscellaneous corrections to the 5GC SBI TS Skeleton |
C4-220300
| revised | CT4#107-bis-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0119 | 1 | F | 17.4.1 | Rel-17 | Formatting of Description Fields |
C4-221566
| agreed | CT4#108-e | Ericsson |
CP-220025
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0119 | - | F | 17.4.1 | Rel-17 | Formatting of Description Fields |
C4-220197
| revised | CT4#107-bis-e | Ericsson |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0118 | - | F | 17.4.1 | Rel-17 | JSON schema example with a combination of restrictions |
C4-220104
| agreed | CT4#107-bis-e | Nokia, Nokia Sh... |
CP-220023
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0117 | 1 | F | 17.4.1 | Rel-17 | Aligning SBI-Stage3-Template with TS 29.501 |
C4-220325
| agreed | CT4#107-bis-e | Huawei |
CP-220023
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0117 | - | F | 17.4.1 | Rel-17 | Aligning SBI-Stage3-Template with TS 29.501 |
C4-220036
| revised | CT4#107-bis-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0116 | 1 | F | 17.4.1 | Rel-17 | Handling Description field along with the '$ref' keyword |
C4-220324
| agreed | CT4#107-bis-e | Huawei |
CP-220023
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0116 | - | F | 17.4.1 | Rel-17 | Handling Description field along with the '$ref' keyword |
C4-220035
| revised | CT4#107-bis-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0115 | 1 | F | 17.4.1 | Rel-17 | Adding examples to the Resource URI structure clause |
C4-220323
| agreed | CT4#107-bis-e | Huawei |
CP-220023
| approved | CT#95-e | CT4 | 17.5.0 | SBIProtoc17 |
|
|
| 29.501 | 0115 | - | F | 17.4.1 | Rel-17 | Adding examples to the Resource URI structure clause |
C4-220034
| revised | CT4#107-bis-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0114 | - | F | 17.3.1 | Rel-17 | Subscription update with PUT request |
C4-216187
| agreed | CT4#107-e | Ericsson |
CP-213086
| approved | CT#94-e | CT4 | 17.4.0 | SBIProtoc17 |
|
|
| 29.501 | 0113 | 1 | F | 17.3.1 | Rel-17 | Extending the SBI skeleton Table 6.1.3.1-1 |
C4-215358
| withdrawn | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0113 | - | F | 17.3.1 | Rel-17 | Extending the SBI skeleton Table 6.1.3.1-1 |
C4-215224
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0112 | 2 | F | 17.3.1 | Rel-17 | Resource URI structure in the SBI skeleton |
C4-215501
| agreed | CT4#106-e | Huawei |
CP-213086
| approved | CT#94-e | CT4 | 17.4.0 | SBIProtoc17 |
|
|
| 29.501 | 0112 | 1 | F | 17.3.1 | Rel-17 | Resource URI structure in the SBI skeleton |
C4-215350
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0112 | - | F | 17.3.1 | Rel-17 | Resource URI structure in the SBI skeleton |
C4-215030
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0111 | 5 | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-216618
| agreed | CT4#107-e | Huawei |
CP-213087
| approved | CT#94-e | CT4 | 17.4.0 | SBIProtoc17 |
|
|
| 29.501 | 0111 | 4 | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-216614
| revised | CT4#107-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0111 | 3 | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-216439
| revised | CT4#107-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0111 | 2 | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-216016
| revised | CT4#107-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0111 | 1 | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-215349
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0111 | - | F | 17.3.1 | Rel-17 | Resource URI structure in the Guidelines for Services Definition |
C4-215029
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0110 | 1 | F | 17.3.1 | Rel-17 | Miscellaneous clarifications |
C4-215348
| agreed | CT4#106-e | Huawei |
CP-213085
| approved | CT#94-e | CT4 | 17.4.0 | SBIProtoc17 |
|
|
| 29.501 | 0110 | - | F | 17.3.1 | Rel-17 | Miscellaneous clarifications |
C4-215028
| revised | CT4#106-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0109 | 2 | F | 17.2.0 | Rel-17 | Corrections to the API URI and relative URI below root concepts |
C4-214690
| agreed | CT4#105-e | Huawei |
CP-212026
| approved | CT#93-e | CT4 | 17.3.0 | SBIProtoc17 |
|
|
| 29.501 | 0109 | 1 | F | 17.2.0 | Rel-17 | Corrections to the API URI and relative URI below root concepts |
C4-214527
| revised | CT4#105-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0109 | - | F | 17.2.0 | Rel-17 | Corrections to the API URI and relative URI below root concepts |
C4-214515
| revised | CT4#105-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0108 | 2 | F | 17.2.0 | Rel-17 | Clarification to API name guidance in the SBI template |
C4-214545
| agreed | CT4#105-e | Huawei |
CP-212026
| approved | CT#93-e | CT4 | 17.3.0 | SBIProtoc17 |
|
|
| 29.501 | 0108 | 1 | F | 17.2.0 | Rel-17 | Clarification to API name guidance in the SBI template |
C4-214524
| revised | CT4#105-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0108 | - | F | 17.2.0 | Rel-17 | Clarification to API name guidance in the SBI template |
C4-214494
| revised | CT4#105-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0107 | 1 | F | 17.2.0 | Rel-17 | Compatibility Clarification |
C4-214583
| agreed | CT4#105-e | Nokia, Nokia Sh... |
CP-212026
| approved | CT#93-e | CT4 | 17.3.0 | SBIProtoc17 |
|
|
| 29.501 | 0107 | - | F | 17.2.0 | Rel-17 | Compatibility Clarification |
C4-214166
| revised | CT4#105-e | Nokia, Nokia Sh... |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0106 | 1 | B | 17.1.0 | Rel-17 | Additional guidelines for OpenAPI specification files |
C4-213515
| agreed | CT4#104-e | Huawei, Ericsson |
CP-211028
| approved | CT#92-e | CT4 | 17.2.0 | SBIProtoc17 |
|
|
| 29.501 | 0106 | - | B | 17.1.0 | Rel-17 | Respecting 3GPP Forge executing rules |
C4-213357
| revised | CT4#104-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0105 | - | A | 17.1.0 | Rel-17 | Nested cardinality R17 |
C4-213030
| agreed | CT4#104-e | China Mobile Co... |
CP-211065
| approved | CT#92-e | CT4 | 17.2.0 | SBIProtoc16 |
|
|
| 29.501 | 0104 | - | F | 16.5.0 | Rel-16 | Nested cardinality R16 |
C4-213029
| agreed | CT4#104-e | China Mobile Co... |
CP-211065
| approved | CT#92-e | CT4 | 16.6.0 | SBIProtoc16 |
|
|
| 29.501 | 0103 | 1 | F | 17.1.0 | Rel-17 | Change Notification of Array to Stateless NF Consumer |
C4-212545
| agreed | CT4#103-e | Hewlett-Packard... |
CP-211028
| approved | CT#92-e | CT4 | 17.2.0 | SBIProtoc17 |
|
|
| 29.501 | 0103 | - | F | 17.1.0 | Rel-17 | Change Notification of Array to Stateless NF Consumer |
C4-212064
| revised | CT4#103-e | Hewlett-Packard... |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0102 | - | F | 17.0.0 | Rel-17 | Withdrawing API versions |
C4-211500
| agreed | CT4#102-e | HuaWei, MCC |
CP-210021
| approved | CT#91-e | CT4 | 17.1.0 | 5GS_Ph1-CT, SBI... |
|
|
| 29.501 | 0101 | - | D | 17.0.0 | Rel-17 | Editorial Corrections |
C4-211483
| agreed | CT4#102-e | Ericsson |
CP-210021
| approved | CT#91-e | CT4 | 17.1.0 | SBIProtoc17 |
|
|
| 29.501 | 0100 | - | F | 17.0.0 | Rel-17 | Referencing of 3GPP custom headers |
C4-211371
| merged | CT4#102-e | Huawei |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0099 | 1 | B | 17.0.0 | Rel-17 | SBI TS Template Update |
C4-211590
| agreed | CT4#102-e | Ericsson, Huawei |
CP-210021
| approved | CT#91-e | CT4 | 17.1.0 | SBIProtoc17 |
|
|
| 29.501 | 0099 | - | B | 17.0.0 | Rel-17 | SBI TS Template Update |
C4-211292
| revised | CT4#102-e | Ericsson |
| | | | | SBIProtoc17 |
|
|
| 29.501 | 0098 | - | F | 17.0.0 | Rel-17 | Guidance on Error Response design for Indirect Communication |
C4-211082
| agreed | CT4#102-e | Nokia, Nokia Sh... |
CP-210021
| approved | CT#91-e | CT4 | 17.1.0 | SBIProtoc17 |
|
|
| 29.501 | 0097 | - | D | 17.0.0 | Rel-17 | Use of inclusive terminology |
C4-210107
| agreed | CT4#101-bis-e | Huawei |
CP-210027
| approved | CT#91-e | CT4 | 17.1.0 | TEI17 |
|
|
| 29.501 | 0096 | - | F | 16.5.0 | Rel-17 | OpenAPI "description" fields in data type definitions |
C4-205266
| agreed | CT4#101-e | Ericsson |
CP-203064
| approved | CT#90-e | CT4 | 17.0.0 | SBIProtoc17 |
|
|
| 29.501 | 0095 | - | F | 16.5.0 | Rel-17 | OpenAPI Reference |
C4-205258
| agreed | CT4#101-e | Ericsson, Orange |
CP-203064
| approved | CT#90-e | CT4 | 17.0.0 | SBIProtoc17 |
|
|
| 29.501 | 0094 | - | F | 16.5.0 | Rel-17 | API Versioning System based on Semantic Versioning |
C4-205249
| agreed | CT4#101-e | Ericsson, Orang... |
CP-203064
| approved | CT#90-e | CT4 | 17.0.0 | SBIProtoc17 |
|
|
| 29.501 | 0093 | - | A | 16.4.0 | Rel-16 | Storage of YAML files in 3GPP Forge |
C4-204381
| agreed | CT4#99-e | Huawei |
CP-202043
| approved | CT#89-e | CT4 | 16.5.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0092 | - | F | 15.7.0 | Rel-15 | Storage of YAML files in 3GPP Forge |
C4-204380
| agreed | CT4#99-e | Huawei |
CP-202043
| approved | CT#89-e | CT4 | 15.8.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0091 | 1 | F | 16.4.0 | Rel-16 | API URI correction and template udpate |
C4-204384
| agreed | CT4#99-e | Huawei |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0091 | - | F | 16.4.0 | Rel-16 | API URI correction and template udpate |
C4-204335
| revised | CT4#99-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0090 | 1 | F | 16.4.0 | Rel-16 | Miscellaneous corrections |
C4-204422
| agreed | CT4#99-e | Huawei |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0090 | - | F | 16.4.0 | Rel-16 | Miscellaneous corrections |
C4-204307
| revised | CT4#99-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0089 | - | F | 16.4.0 | Rel-16 | Content of Location header when TLS is used |
C4-204286
| agreed | CT4#99-e | Ericsson |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0088 | 1 | F | 16.4.0 | Rel-16 | Data types with string type |
C4-204389
| agreed | CT4#99-e | Huawei |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0088 | - | F | 16.4.0 | Rel-16 | Data types with string type |
C4-204145
| revised | CT4#99-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0087 | - | F | 16.4.0 | Rel-16 | Naming requirements for resource/operation-level scopes |
C4-204122
| agreed | CT4#99-e | Nokia, Nokia Sh... |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0086 | 2 | F | 16.4.0 | Rel-16 | Handling of JSON Arrays |
C4-204523
| agreed | CT4#99-e | Ericsson, China... |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0086 | 1 | F | 16.4.0 | Rel-16 | Handling of JSON Arrays |
C4-204492
| revised | CT4#99-e | Ericsson, China... |
CP-202110
| approved | CT#89-e | CT4 | 16.5.0 | SBIProtoc16 |
|
|
| 29.501 | 0086 | - | F | 16.4.0 | Rel-16 | Handling of JSON Arrays |
C4-204083
| revised | CT4#99-e | Ericsson |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0085 | 2 | D | 16.4.0 | Rel-16 | Editorial fixes |
C4-204579
| agreed | CT4#99-e | Huawei |
CP-202109
| approved | CT#89-e | CT4 | 16.5.0 | TEI16 |
|
|
| 29.501 | 0085 | 1 | D | 16.4.0 | Rel-17 | Editorial fixes |
C4-204021
| revised | CT4#99-e | Huawei |
| | | | | TEI17 |
|
|
| 29.501 | 0085 | - | D | 16.4.0 | Rel-17 | Editorial fixes |
C4-204016
| revised | CT4#99-e | Huawei |
| | | | | TEI17 |
|
|
| 29.501 | 0084 | - | B | 16.3.0 | Rel-16 | Example on 5G SoR implicit subscribe/notify mechanism |
C4-203352
| not pursued | CT4#98-e | Orange |
| | | | | NSORAF |
|
|
| 29.501 | 0083 | 1 | F | 16.3.0 | Rel-16 | Missing abbreviations |
C4-203472
| agreed | CT4#98-e | Huawei |
CP-201071
| approved | CT#88-e | CT4 | 16.4.0 | TEI16 |
|
|
| 29.501 | 0083 | - | F | 16.3.0 | Rel-16 | Missing abbreviations |
C4-203319
| revised | CT4#98-e | Huawei |
| | | | | TEI16 |
|
|
| 29.501 | 0082 | 1 | F | 16.3.0 | Rel-16 | Maximum JSON payload size |
C4-203446
| agreed | CT4#98-e | China Mobile |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0082 | - | F | 16.3.0 | Rel-16 | Maximum JSON payload size |
C4-203227
| revised | CT4#98-e | China Mobile |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0081 | 2 | F | 16.3.0 | Rel-16 | Requirements for secure API design |
C4-203470
| withdrawn | CT4#98-e | Huawei |
| | | | | 5G_eSBA |
|
|
| 29.501 | 0081 | 1 | F | 16.3.0 | Rel-16 | Requirements for secure API design |
C4-203463
| agreed | CT4#98-e | Huawei |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0081 | - | F | 16.3.0 | Rel-16 | Requirements for secure API design |
C4-203167
| revised | CT4#98-e | Huawei |
| | | | | 5G_eSBA |
|
|
| 29.501 | 0080 | - | F | 16.3.0 | Rel-16 | Correct the Resource Tree Example |
C4-203101
| agreed | CT4#98-e | ZTE, AT&T |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0079 | 1 | F | 16.3.0 | Rel-16 | API URI correction and template udpate |
C4-203451
| agreed | CT4#98-e | China Mobile |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0079 | - | F | 16.3.0 | Rel-16 | API URI correction and template udpate |
C4-203023
| revised | CT4#98-e | China Mobile |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0078 | 2 | F | 16.3.0 | Rel-16 | URI types |
C4-203673
| agreed | CT4#98-e | Huawei |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0078 | 1 | F | 16.3.0 | Rel-16 | URI types |
C4-203462
| revised | CT4#98-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0078 | - | F | 16.3.0 | Rel-16 | URI types |
C4-203008
| revised | CT4#98-e | Huawei |
| | | | | 5G_eSBA |
|
|
| 29.501 | 0077 | 2 | F | 16.3.0 | Rel-16 | Delimiters - URI and SBI specific |
C4-203511
| agreed | CT4#98-e | Huawei |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0077 | 1 | F | 16.3.0 | Rel-16 | Delimiters - URI and SBI specific |
C4-203115
| revised | CT4#98-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0077 | - | F | 16.3.0 | Rel-16 | Delimiters - URI and SBI specifics |
C4-203007
| revised | CT4#98-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0076 | - | F | 16.3.0 | Rel-16 | Correction of the method used for Notifications |
C4-202127
| agreed | CT4#97-e | Ericsson |
CP-201071
| approved | CT#88-e | CT4 | 16.4.0 | TEI16 |
|
|
| 29.501 | 0075 | 1 | B | 16.3.0 | Rel-16 | Resource-Level Authorization |
C4-202511
| agreed | CT4#97-e | Ericsson, Nokia... |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0075 | - | B | 16.3.0 | Rel-16 | Resource-Level Authorization |
C4-202106
| revised | CT4#97-e | Ericsson, Nokia... |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0074 | 2 | F | 16.3.0 | Rel-16 | Clarifications to callback URI |
C4-202476
| agreed | CT4#97-e | Huawei |
CP-201034
| approved | CT#88-e | CT4 | 16.4.0 | SBIProtoc16 |
|
|
| 29.501 | 0074 | 1 | F | 16.3.0 | Rel-16 | Clarifications to callback URI |
C4-202396
| revised | CT4#97-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0074 | - | F | 16.3.0 | Rel-16 | Clarifications to callback URI |
C4-202013
| revised | CT4#97-e | Huawei |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0073 | 1 | F | 16.2.0 | Rel-16 | New tables in 29.501 template |
C4-201144
| agreed | CT4#96-e | SPRINT Corporation |
CP-200039
| approved | CT#87-e | CT4 | 16.3.0 | TEI16 |
|
|
| 29.501 | 0073 | - | F | 16.2.0 | Rel-16 | New tables in 29.501 template |
C4-200738
| revised | CT4#96-e | SPRINT Corporation |
| | | | | TEI16 |
|
|
| 29.501 | 0072 | 1 | A | 16.2.0 | Rel-16 | Storage of YAML files in ETSI Forge |
C4-200406
| agreed | CT4#96-e | Ericsson |
CP-200054
| approved | CT#87-e | CT4 | 16.3.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0072 | - | A | 16.2.0 | Rel-16 | Storage of YAML files in ETSI Forge |
C4-200106
| withdrawn | CT4#96 | Ericsson |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0071 | 1 | F | 15.6.0 | Rel-15 | Storage of YAML files in ETSI Forge |
C4-200405
| agreed | CT4#96-e | Ericsson |
CP-200054
| approved | CT#87-e | CT4 | 15.7.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0071 | - | F | 15.6.0 | Rel-15 | Storage of YAML files in ETSI Forge |
C4-200105
| withdrawn | CT4#96 | Ericsson |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0070 | 1 | F | 16.1.0 | Rel-16 | Add Corresponding OpenAPI descriptions in clause 5.1 |
C4-195562
| agreed | CT4#95 | Sprint |
CP-193036
| approved | CT#86 | CT4 | 16.2.0 | TEI16 |
|
|
| 29.501 | 0070 | - | F | 16.1.0 | Rel-16 | Add Corresponding OpenAPI descriptions in clause 5.1 |
C4-195456
| revised | CT4#95 | Sprint |
| | | | | TEI16 |
|
|
| 29.501 | 0069 | 2 | A | 16.1.0 | Rel-16 | Fourth Field of API Versions |
C4-195606
| agreed | CT4#95 | Ericsson, Veriz... |
CP-193025
| approved | CT#86 | CT4 | 16.2.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0069 | 1 | A | 16.1.0 | Rel-16 | Fourth Field of API Versions |
C4-195396
| revised | CT4#95 | Ericsson, Veriz... |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0069 | - | A | 16.1.0 | Rel-16 | Fourth Field of API Versions |
C4-195067
| revised | CT4#95 | Ericsson, Veriz... |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0068 | 2 | F | 15.5.0 | Rel-15 | Fourth Field of API Versions |
C4-195605
| agreed | CT4#95 | Ericsson, Veriz... |
CP-193025
| approved | CT#86 | CT4 | 15.6.0 | 5GS_Ph1-CT |
|
|
| 29.501 | 0068 | 1 | F | 15.5.0 | Rel-15 | Fourth Field of API Versions |
C4-195395
| revised | CT4#95 | Ericsson, Veriz... |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0068 | - | F | 15.5.0 | Rel-15 | Fourth Field of API Versions |
C4-195066
| revised | CT4#95 | Ericsson, Veriz... |
| | | | | 5GS_Ph1-CT |
|
|
| 29.501 | 0067 | 1 | F | 16.1.0 | Rel-16 | Extending ProblemDetails for Backward Compatibility |
C4-194337
| agreed | CT4#94 | Ericsson |
CP-193063
| approved | CT#86 | CT4 | 16.2.0 | SBIProtoc16 |
|
|
| 29.501 | 0067 | - | F | 16.1.0 | Rel-16 | Extending ProblemDetails for Backward Compatibility |
C4-194194
| revised | CT4#94 | Ericsson |
| | | | | SBIProtoc16 |
|
|
| 29.501 | 0066 | 2 | B | 16.1.0 | Rel-16 | 3gppHalForms media type |
C4-194512
| agreed | CT4#94 | China Mobile |
CP-193063
| approved | CT#86 | CT4 | 16.2.0 | SBIProtoc16 |
|