Luis Farias | 9d66fca | 2020-05-28 19:01:58 -0700 | [diff] [blame^] | 1 | .. Copyright (c) 2019-2020 Intel |
| 2 | .. |
| 3 | .. Licensed under the Apache License, Version 2.0 (the "License"); |
| 4 | .. you may not use this file except in compliance with the License. |
| 5 | .. You may obtain a copy of the License at |
| 6 | .. |
| 7 | .. http://www.apache.org/licenses/LICENSE-2.0 |
| 8 | .. |
| 9 | .. Unless required by applicable law or agreed to in writing, software |
| 10 | .. distributed under the License is distributed on an "AS IS" BASIS, |
| 11 | .. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 12 | .. See the License for the specific language governing permissions and |
| 13 | .. limitations under the License. |
| 14 | |
| 15 | |
| 16 | .. |br| raw:: html |
| 17 | |
| 18 | <br /> |
| 19 | |
| 20 | ORAN 5G FAPI TM Release Notes |
| 21 | ============================= |
| 22 | |
| 23 | Version oran_release_bronze_v1.0, May 2020 |
| 24 | ------------------------------------------ |
| 25 | * First release of the 5G FAPI TM to ORAN in support of the Bronze Release |
| 26 | * This version supports 5G only |
| 27 | * PARAM.config and PARAM.resp are not supported |
| 28 | * ERROR.ind relies on the L1 support for error detection as the 5G FAPI TM \ |
| 29 | only enforces security checks and |br| |
| 30 | integrity checks to avoid DOS attacks but \ |
| 31 | it doesn't perform full validation of the input parameters for compliance to |
| 32 | the standard |
| 33 | * Deviations from the March version of the SCF 5G FAPI document have been \ |
| 34 | implemented in order to deal with |br| |
| 35 | limitations and ommisions found in the |
| 36 | current SCF document, these differences are being provided to the SCF for |
| 37 | the next document update. The 5G FAPI implementation is defined in the file |
| 38 | fapi_interface.h |
| 39 | * Multi-user MIMO, Beamforming, Precoding and URLLC are not supported in the |
| 40 | current implementation as they |br| |
| 41 | require additional alignment between the SCF |
| 42 | P19 and the ORAN |
| 43 | * The option for the MAC layer doing the full generation of the PBCH payload is not supported in this release and it will be added in the maintainance release cycle. |