|
|
| 29.576 | 0076 | 1 | B | 19.0.0 | Rel-19 | MFAF 3daDataManagement updates to support MFAF transfer |
C3-246400
| | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0076 | - | B | 19.0.0 | Rel-19 | MFAF 3daDataManagement updates to support MFAF transfer |
C3-246205
| revised | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0075 | 1 | B | 19.0.0 | Rel-19 | MFAF ContextManagement API OpenAPI |
C3-246399
| | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0075 | - | B | 19.0.0 | Rel-19 | MFAF ContextManagement API OpenAPI |
C3-246204
| revised | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0074 | 1 | B | 19.0.0 | Rel-19 | MFAF ContextManagement API data model |
C3-246398
| | CT3#138 | Nokia, Huawei |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0074 | - | B | 19.0.0 | Rel-19 | MFAF ContextManagement API data model |
C3-246203
| revised | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0073 | 1 | B | 19.0.0 | Rel-19 | MFAF ContextManagement API service descripiton |
C3-246397
| | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0073 | - | B | 19.0.0 | Rel-19 | MFAF ContextManagement API service descripiton |
C3-246202
| revised | CT3#138 | Nokia |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0072 | - | B | 19.0.0 | Rel-19 | Adding LMF as a consumer of Nmfaf_3caDataManagement Service |
C3-246129
| | CT3#138 | ZTE |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0071 | 1 | B | 19.0.0 | Rel-19 | Support event notification processing based on the processing and formatting instructions |
C3-245381
| agreed | CT3#137 | Huawei |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0071 | - | B | 19.0.0 | Rel-19 | Support event notification processing based on the processing and formatting instructions |
C3-245271
| revised | CT3#137 | Huawei |
| | | | | eNetAE19 |
|
|
|
| 29.576 | 0070 | - | F | 18.4.0 | Rel-19 | MFAF API corrections |
C3-244233
| agreed | CT3#136 | Nokia |
CP-242124
| approved | CT#105 | CT3 | 19.0.0 | eNetAE19 |
|
|
|
| 29.576 | 0069 | - | F | 18.4.0 | Rel-18 | MFAF ContextManagement API OpenAPI |
C3-244228
| postponed | CT3#136 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0068 | - | F | 18.4.0 | Rel-18 | MFAF ContextManagement API data model |
C3-244227
| postponed | CT3#136 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0067 | - | F | 18.4.0 | Rel-18 | MFAF ContextManagement API service descripiton |
C3-244226
| postponed | CT3#136 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0066 | - | F | 18.4.0 | Rel-18 | MFAF Context Transfer initiation service operation |
C3-244225
| postponed | CT3#136 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0065 | 1 | A | 18.4.0 | Rel-18 | Adding ADRF as a consumer of Nmfaf_3caDataManagement |
C3-244549
| agreed | CT3#136 | ZTE |
CP-242128
| approved | CT#105 | CT3 | 18.5.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0065 | - | A | 18.4.0 | Rel-18 | Adding ADRF as a consumer of Nmfaf_3caDataManagement_Fetch |
C3-244147
| revised | CT3#136 | ZTE |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0064 | 1 | F | 17.4.0 | Rel-17 | Adding ADRF as a consumer of Nmfaf_3caDataManagement |
C3-244548
| agreed | CT3#136 | ZTE |
CP-242128
| approved | CT#105 | CT3 | 17.5.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0064 | - | F | 17.4.0 | Rel-17 | Adding ADRF as a consumer of Nmfaf_3caDataManagement_Fetch |
C3-244146
| revised | CT3#136 | ZTE |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0063 | - | F | 18.4.0 | Rel-19 | Correction to API Descriptions table |
C3-244143
| agreed | CT3#136 | ZTE |
CP-242124
| approved | CT#105 | CT3 | 19.0.0 | eNetAE19 |
|
|
|
| 29.576 | 0062 | - | F | 18.4.0 | Rel-18 | Adding LMF as a consumer of Nmfaf_3caDataManagement Service |
C3-244134
| postponed | CT3#136 | ZTE |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0061 | - | F | 18.3.0 | Rel-18 | Update of info and externalDocs fields |
C3-243655
| agreed | CT3#135 | China Mobile |
CP-241086
| approved | CT#104 | CT3 | 18.4.0 | TEI18 |
|
|
|
| 29.576 | 0060 | 1 | A | 18.3.0 | Rel-18 | Corrections on attribute name |
C3-243570
| agreed | CT3#135 | Huawei, Nokia |
CP-241105
| approved | CT#104 | CT3 | 18.4.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0060 | - | A | 18.3.0 | Rel-18 | Corrections on attribute name |
C3-243322
| revised | CT3#135 | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0059 | 1 | F | 17.3.0 | Rel-17 | Corrections on attribute name |
C3-243569
| agreed | CT3#135 | Huawei, Nokia |
CP-241105
| approved | CT#104 | CT3 | 17.4.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0059 | - | F | 17.3.0 | Rel-17 | Corrections on attribute name |
C3-243321
| revised | CT3#135 | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0058 | - | F | 18.3.0 | Rel-18 | MFAF 3caDataManagement API corrections |
C3-243202
| agreed | CT3#135 | Nokia |
CP-241101
| approved | CT#104 | CT3 | 18.4.0 | eNetAE |
|
|
|
| 29.576 | 0057 | - | F | 18.3.0 | Rel-18 | MFAF 3daDataManagement API corrections |
C3-243201
| agreed | CT3#135 | Nokia |
CP-241101
| approved | CT#104 | CT3 | 18.4.0 | eNetAE |
|
|
|
| 29.576 | 0056 | - | B | 18.3.0 | Rel-18 | MFAF ContextManagement API OpenAPI |
C3-243197
| postponed | CT3#135 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0055 | - | B | 18.3.0 | Rel-18 | MFAF ContextManagement API data model |
C3-243196
| postponed | CT3#135 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0054 | 1 | F | 18.3.0 | Rel-18 | MFAF API names corrections |
C3-243550
| agreed | CT3#135 | Nokia |
CP-241101
| approved | CT#104 | CT3 | 18.4.0 | eNetAE |
|
|
|
| 29.576 | 0054 | - | B | 18.3.0 | Rel-18 | MFAF ContextManagement API service descripiton |
C3-243195
| revised | CT3#135 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0053 | 1 | F | 18.3.0 | Rel-18 | MFAF service consumers |
C3-243549
| agreed | CT3#135 | Nokia |
CP-241101
| approved | CT#104 | CT3 | 18.4.0 | eNetAE |
|
|
|
| 29.576 | 0053 | - | B | 18.3.0 | Rel-18 | MFAF Context Transfer initiation service operation |
C3-243194
| revised | CT3#135 | Nokia |
| | | | | eNA_Ph3 |
|
|
|
| 29.576 | 0052 | - | A | 18.3.0 | Rel-18 | Corrections on the attribute names in the service description |
C3-242215
| agreed | CT3#134 | Huawei |
CP-241105
| approved | CT#104 | CT3 | 18.4.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0051 | - | F | 17.3.0 | Rel-17 | Corrections on the attribute names in the service description |
C3-242214
| agreed | CT3#134 | Huawei |
CP-241105
| approved | CT#104 | CT3 | 17.4.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0050 | - | F | 18.3.0 | Rel-18 | Callback correction |
C3-242149
| agreed | CT3#134 | Nokia |
CP-241101
| approved | CT#104 | CT3 | 18.4.0 | eNetAE |
|
|
|
| 29.576 | 0049 | 1 | F | 18.2.0 | Rel-18 | IETF RFC 7540, RFC 7807 obsoleted by RFC 9113 and RFC 9457 respectively |
C3-235572
| agreed | CT3#131 | China Mobile |
CP-233229
| approved | CT#102 | CT3 | 18.3.0 | SBIProtoc18 |
|
|
|
| 29.576 | 0049 | - | F | 18.2.0 | Rel-18 | IETF HTTP RFC 7540 obsoleted by RFC 9113 |
C3-235426
| revised | CT3#131 | China Mobile |
| | | | | SBIProtoc18 |
|
|
|
| 29.576 | 0048 | - | F | 18.1.0 | Rel-18 | Update of info and externalDocs fields |
C3-232703
| agreed | CT3#128 | China Mobile Co... |
CP-231142
| approved | CT#100 | CT3 | 18.2.0 | TEI18 |
|
|
|
| 29.576 | 0047 | 1 | F | 18.1.0 | Rel-18 | Corrections to the redirection mechanism description |
C3-232542
| agreed | CT3#128 | China Mobile Co... |
CP-231132
| approved | CT#100 | CT3 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.576 | 0047 | - | F | 18.1.0 | Rel-18 | Corrections to the redirection mechanism description |
C3-232419
| revised | CT3#128 | China Mobile Co... |
| | | | | SBIProtoc18 |
|
|
|
| 29.576 | 0046 | 1 | F | 18.1.0 | Rel-18 | Corrections to the dummy POST based operation of the Nmfaf_3caDataManagement API |
C3-231564
| agreed | CT3#127-e | Huawei |
CP-231131
| approved | CT#100 | CT3 | 18.2.0 | SBIProtoc18 |
|
|
|
| 29.576 | 0046 | - | F | 18.1.0 | Rel-18 | Corrections to the dummy POST based operation of the Nmfaf_3caDataManagement API |
C3-231206
| revised | CT3#127-e | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.576 | 0045 | - | F | 18.0.0 | Rel-18 | Update of info and externalDocs fields |
C3-230953
| agreed | CT3#126 | China Mobile |
CP-230162
| approved | CT#99 | CT3 | 18.1.0 | TEI18 |
|
|
|
| 29.576 | 0044 | - | B | 18.0.0 | Rel-18 | Support of multiple notification endpoints |
C3-230539
| agreed | CT3#126 | Huawei |
CP-230148
| approved | CT#99 | CT3 | 18.1.0 | eNetAE |
|
|
|
| 29.576 | 0043 | - | F | 18.0.0 | Rel-18 | Corrections to the redirection mechanism description |
C3-230471
| postponed | CT3#126 | Huawei |
| | | | | SBIProtoc18 |
|
|
|
| 29.576 | 0042 | 1 | F | 18.0.0 | Rel-18 | Handling of fetch Instruction |
C3-230715
| agreed | CT3#126 | ZTE |
CP-230149
| approved | CT#99 | CT3 | 18.1.0 | eNetAE |
|
|
|
| 29.576 | 0042 | - | F | 18.0.0 | Rel-18 | Handling of fetch Instruction |
C3-230287
| revised | CT3#126 | ZTE |
| | | | | eNetAE |
|
|
|
| 29.576 | 0041 | - | F | 17.2.0 | Rel-17 | Update of info and externalDocs fields |
C3-225782
| agreed | CT3#125 | China Mobile |
CP-223188
| approved | CT#98-e | CT3 | 17.3.0 | TEI17 |
|
|
|
| 29.576 | 0040 | - | F | 17.2.0 | Rel-18 | Update of info and externalDocs fields |
C3-225766
| agreed | CT3#125 | China Mobile |
CP-223190
| approved | CT#98-e | CT3 | 18.0.0 | TEI18 |
|
|
|
| 29.576 | 0039 | - | F | 17.2.0 | Rel-17 | The time stamp of data and analytics notification |
C3-225710
| withdrawn | CT3#125 | Huawei, Nokia, ... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0038 | - | F | 17.2.0 | Rel-17 | The time stamp of data and analytics notification |
C3-225465
| withdrawn | CT3#125 | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0037 | 2 | F | 17.2.0 | Rel-17 | The time stamp of data and analytics notification |
| | | |
CP-223237
| approved | CT#98-e | Huawei, Nokia, ... | 17.3.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0037 | 1 | F | 17.2.0 | Rel-17 | The time stamp of data and analytics notification |
C3-225772
| revised | CT3#125 | Huawei, Nokia, ... |
CP-223173
| revised | CT#98-e | CT3 | | eNA_Ph2 |
|
|
|
| 29.576 | 0037 | - | F | 17.2.0 | Rel-17 | The time stamp of data and analytics notification |
C3-225446
| revised | CT3#125 | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0036 | - | F | 17.2.0 | Rel-17 | Corrections to data type in POST header |
C3-225339
| agreed | CT3#125 | Ericsson |
CP-223172
| approved | CT#98-e | CT3 | 17.3.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0035 | 1 | F | 17.2.0 | Rel-18 | Correction of data type of procInstruct |
C3-225707
| agreed | CT3#125 | ZTE |
CP-223176
| approved | CT#98-e | CT3 | 18.0.0 | eNetAE |
|
|
|
| 29.576 | 0035 | - | F | 17.2.0 | Rel-17 | Correction of data type of procInstruct |
C3-225222
| revised | CT3#125 | ZTE |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0034 | - | F | 17.2.0 | Rel-17 | Correcting procedure description for dataNotif attribute |
C3-225219
| agreed | CT3#125 | ZTE |
CP-223172
| approved | CT#98-e | CT3 | 17.3.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0033 | - | F | 17.2.0 | Rel-17 | Corrections on Nmfaf_3caDataManagement service |
C3-225173
| merged | CT3#125 | China Telecom |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0032 | 1 | F | 17.2.0 | Rel-17 | Corrections for time stamp in Nmfaf_3caDataManagement_Notify service operation |
C3-225493
| merged | CT3#125 | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0032 | - | F | 17.2.0 | Rel-18 | Corrections for time stamp in Nmfaf_3caDataManagement_Notify service operation |
C3-225133
| revised | CT3#125 | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0031 | - | F | 17.2.0 | Rel-18 | Adding the mandatory error code 502 Bad Gateway |
C3-225121
| agreed | CT3#125 | Nokia, Nokia Sh... |
CP-223191
| approved | CT#98-e | CT3 | 18.0.0 | SBIProtoc18 |
|
|
|
| 29.576 | 0030 | - | F | 17.1.0 | Rel-17 | Update of info and externalDocs fields |
C3-224754
| agreed | CT3#123-e | China Mobile |
CP-222121
| approved | CT#97-e | CT3 | 17.2.0 | TEI17 |
|
|
|
| 29.576 | 0029 | - | F | 17.1.0 | Rel-17 | Corrections to NF service consumer |
C3-224400
| agreed | CT3#123-e | Ericsson |
CP-222101
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0028 | 1 | F | 17.1.0 | Rel-17 | Miscellaneous corrections |
C3-224522
| agreed | CT3#123-e | Huawei |
CP-222102
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0028 | - | F | 17.1.0 | Rel-17 | Miscellaneous corrections |
C3-224350
| revised | CT3#123-e | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0027 | - | F | 17.1.0 | Rel-17 | Nmfaf_3daDataManagement Application specific error code enhancement |
C3-224342
| withdrawn | CT3#123-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0026 | - | F | 17.1.0 | Rel-17 | Corrections to Fetch Notification |
C3-224291
| agreed | CT3#123-e | ZTE |
CP-222101
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0025 | - | F | 17.1.0 | Rel-17 | Corrections related to NmfafDataRetrievalNotification data type |
C3-224290
| agreed | CT3#123-e | ZTE |
CP-222101
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0024 | - | F | 17.1.0 | Rel-17 | Clean up References |
C3-224289
| agreed | CT3#123-e | ZTE |
CP-222101
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0023 | 1 | F | 17.1.0 | Rel-17 | Add NWDAF hosting DCCF as consumer of the Nmfaf_3daDataManagement service |
C3-224667
| agreed | CT3#123-e | Nokia, Nokia Sh... |
CP-222104
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0023 | - | F | 17.1.0 | Rel-17 | Add NWDAF hosting DCCF as consumer of the Nmfaf_3daDataManagement service |
C3-224247
| revised | CT3#123-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0022 | 1 | F | 17.1.0 | Rel-17 | Corrections related to callback functions in MFAF |
C3-224666
| agreed | CT3#123-e | Nokia, Nokia Sh... |
CP-222104
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0022 | - | F | 17.1.0 | Rel-17 | Corrections related to callback functions in MFAF |
C3-224246
| revised | CT3#123-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0021 | 2 | F | 17.1.0 | Rel-17 | Add expiry attribute to the fetch instructions |
C3-224762
| agreed | CT3#123-e | Nokia, Nokia Sh... |
CP-222104
| approved | CT#97-e | CT3 | 17.2.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0021 | 1 | F | 17.1.0 | Rel-17 | Add expiry attribute to the fetch instructions |
C3-224665
| revised | CT3#123-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0021 | - | F | 17.1.0 | Rel-17 | Add expiry attribute to the fetch instructions |
C3-224245
| revised | CT3#123-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0020 | - | F | 17.1.0 | Rel-17 | Update inputs of Nmfaf_3caDataManagement_Notify service |
C3-224224
| merged | CT3#123-e | China Telecom |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0019 | - | F | 17.0.0 | Rel-17 | Update of info and externalDocs fields |
C3-223731
| agreed | CT3#122-e | China Mobile |
CP-221152
| approved | CT#96 | CT3 | 17.1.0 | TEI17 |
|
|
|
| 29.576 | 0018 | 1 | F | 17.0.0 | Rel-17 | Update the apiVersion placeholder 29.576 Rel-17 |
C3-223616
| agreed | CT3#122-e | China Mobile Co... |
CP-221155
| approved | CT#96 | CT3 | 17.1.0 | SBIProtoc17 |
|
|
|
| 29.576 | 0018 | - | F | 17.0.0 | Rel-17 | Update the apiVersion placeholder 29.576 Rel-17 |
C3-223449
| revised | CT3#122-e | China Mobile Co... |
| | | | | SBIProtoc17 |
|
|
|
| 29.576 | 0017 | - | F | 17.0.0 | Rel-17 | Correction on DataNotification type 29.576 |
C3-223445
| withdrawn | CT3#122-e | China Mobile Co... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0016 | - | F | 17.0.0 | Rel-17 | update of Abbreviations |
C3-223346
| agreed | CT3#122-e | ZTE |
CP-221134
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0015 | - | F | 17.0.0 | Rel-17 | add CEF and OAM as consumers of Nmfaf_3daDataManagement Service |
C3-223343
| agreed | CT3#122-e | ZTE |
CP-221134
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0014 | - | F | 17.0.0 | Rel-17 | Correction to MFAF notification information |
C3-223342
| agreed | CT3#122-e | ZTE |
CP-221134
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0013 | - | F | 17.0.0 | Rel-17 | Incorrect referred data type |
C3-223341
| merged | CT3#122-e | ZTE |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0012 | 1 | F | 17.0.0 | Rel-17 | Update inputs of Nmfaf_3caDataManagement_Notify service |
C3-223552
| agreed | CT3#122-e | China Telecom, ZTE |
CP-221135
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0012 | - | F | 17.0.0 | Rel-17 | Update inputs of Nmfaf_3caDataManagement_Notify service |
C3-223179
| revised | CT3#122-e | China Telecom |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0011 | - | F | 17.0.0 | Rel-17 | Removing UDM from the list of MFAF service consumers |
C3-223062
| agreed | CT3#122-e | Nokia, Nokia Sh... |
CP-221133
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0010 | - | F | 17.0.0 | Rel-17 | Adding 3XX and error response handling support for MFAF services |
C3-222568
| withdrawn | CT3#121-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0009 | 2 | F | 17.0.0 | Rel-17 | Correction on DataNotification type |
C3-223463
| agreed | CT3#122-e | China Mobile Co... |
CP-221134
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0009 | 1 | F | 17.0.0 | Rel-17 | Correction on DataNotification type |
C3-222591
| revised | CT3#121-e | China Mobile Co... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0009 | - | F | 17.0.0 | Rel-17 | Correction on DataNotification type |
C3-222369
| revised | CT3#121-e | China Mobile Co... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0008 | - | F | 17.0.0 | Rel-17 | Correction on Nadrf_DataManagement_StorageRequest service operation |
C3-222368
| withdrawn | CT3#121-e | China Mobile Co... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0007 | - | F | 17.0.0 | Rel-17 | Handling of the redirection responses |
C3-222289
| agreed | CT3#121-e | Ericsson |
CP-221130
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0006 | 1 | F | 17.0.0 | Rel-17 | Nmfaf_3caDataManagement API corrections |
C3-222514
| agreed | CT3#121-e | Ericsson |
CP-221131
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0006 | - | F | 17.0.0 | Rel-17 | Nmfaf_3caDataManagement API corrections |
C3-222288
| revised | CT3#121-e | Ericsson |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0005 | - | F | 17.0.0 | Rel-17 | Nmfaf_3daDataManagement API corrections |
C3-222287
| agreed | CT3#121-e | Ericsson |
CP-221129
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0004 | 1 | B | 17.0.0 | Rel-17 | Support carrying ADRF ID in Nmfaf_3daDataManagement_Configure service operation |
C3-222562
| agreed | CT3#121-e | Huawei |
CP-221132
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0004 | - | B | 17.0.0 | Rel-17 | Support carrying ADRF ID in Nmfaf_3daDataManagement_Configure service operation |
C3-222216
| revised | CT3#121-e | Huawei |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0003 | - | F | 17.0.0 | Rel-17 | Correct the Cardinality and Presence of some attributes |
C3-222206
| agreed | CT3#121-e | Huawei |
CP-221129
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0002 | 1 | F | 17.0.0 | Rel-17 | Corrections in the MFAF 3caDataManagement API |
C3-222546
| agreed | CT3#121-e | Nokia, Nokia Sh... |
CP-221132
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0002 | - | F | 17.0.0 | Rel-17 | Corrections in the MFAF 3caDataManagement API |
C3-222103
| revised | CT3#121-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|
|
|
| 29.576 | 0001 | 1 | F | 17.0.0 | Rel-17 | Adding 3XX and error response handling support for MFAF services |
C3-222572
| agreed | CT3#121-e | Nokia, Nokia Sh... |
CP-221132
| approved | CT#96 | CT3 | 17.1.0 | eNA_Ph2 |
|
|
|
| 29.576 | 0001 | - | F | 17.0.0 | Rel-17 | Adding 3XX and error response handling support for MFAF services |
C3-222042
| revised | CT3#121-e | Nokia, Nokia Sh... |
| | | | | eNA_Ph2 |
|