Uploaded O-RAN SC Ver A SW Requirements 20190610b.docx to reflect the latest list of epics; Please take a look at all epics for each category.

Radisys (Ganesh?) please provide your epics for O-DU and Open front haul when you get a chance. Thx,

Rittwik

still four minor comments for version O-RAN SC Ver A SW Requirements 20190619a.docx

(1)
[RIC-A-F02]
Acceptance criteria: A1 message sent to RIC is transformed into E2 Control message(s).
->
Acceptance criteria: A1 message sent to RIC is relayed to one or more xApps and the xApp(s) change their behavior accordingly.

(2)
[RIC-A-F30]
Possibly further steps needed after data is in Redis (e.g. ConfigMap creation)
->
Possibly further steps needed on top of R1's ConfigMap solution.

(3)
[RICAPP-A-F100] and the subsequent [RICAPP-A-F03]
The two EPICs are merged into one table block in the document. Pls. split.
Actually now looking more thoroughly it seems as if [RICAPP-A-F04] and [RICAPP-A-F03] on page 18 are duplicates of the same EPICs on
page 15/16. The correct action seems to delete the two

(4)
[RICAPP-A-F100] is missing the "source" row.

Thanks Thoralf and Tong Li for your inputs.

Uploaded O-RAN SC Ver A SW Requirements 20190627a.docx; Added Lenovo, Windriver, Radisys/Intel contributions.

Uploaded O-RAN SC Ver A SW Requirements 20190701.docx With Radisys/Intel O-DU epic updates

Uploaded O-RAN SC Ver A SW Requirements 20190702b.docx with Samsung Epic and Integration and Test Epic changes to support "one-click" test setup and deferal of OTF integration.

Uploaded O-RAN SC Ver A SW Requirements 20190709a.docx with a Repo name suggestion for Samsung Contribution, Placeholder for UE Simulator from Altran. Still pending is O-CU contribution from China Mobile, which Jinri thinks we can get added, and work out the user stories and legal aspects of the contribution post EPICs. Worst case is EPIC would become backlogged to "B" release. Still need O-RAN Alliance WG reviews with approve, abstain, or comments. WG6 review will be on 7/16.

Uploaded O-RAN SC Ver A SW Requirements 20190709a.docx with changes to several epics related to logging as provided by Eliza Celenti. Updated epics are: 

• [RIC-A-F06] Provide Standardized logging library
• [RIC-A-F07] Support event trace reporting
• [RIC-A-F39] RIC must support transactional logging
• [INT-A-F03] Share Network Data with RGPF

Uploaded O-RAN SC Ver A SW Requirements 20190719a. This version reflects entry into Jira of all the Near-RT RIC epics RIC-A-Fxx. Jira links added to the document for each epic posted to Jira.

Uploaded O-RAN SC Ver A SW Requirements 20190719b. This version reflects entry into Jira of all the Integration Project epics INT-A-Fxx. Jira links added to the document for each epic posted to Jira. Note that [INT-A-F212] Provide Test for the 5G use case "PNF Plug and Play” was not added to JIRA as it is expected to move to the OAM project.

Uploaded O-RAN SC Ver A SW Requirements 20190719c. This version adds O-CU epics and annex descriptions from CMCC. 

Uploaded O-RAN SC Ver A SW Requirements 20190724a. This version adds the JIRA links for RICAPP Epics. Also the Inspur Epic is reworded as a draft while we are confirming with them that the description now matches the contribution.

Updated document with Jira links for OAM and Non-RT RIC Epics

updated document with clarification on fig-4 which come from O-RAN WG8.

Uploaded v10 of the requirements (OSC_Bronze_release_planning_v10_2019_11_19.xlsx). This contains three new dashboard epics.

Uploaded v11 of the requirements (OSC_Bronze_release_planning_v11_2019_11_20.xlsx)

This version adds no new epics but group the epics by (a) element (e.g. RIC, RICAPP, ...) and (b) type of work needed (e.g. A1 Alignment). We can refine these categories and specific classifications further if need be.

Uploaded v12 of the requirements (OSC_Bronze_release_planning_v12_2019_11_21.xlsx)

No new epics this time. Fixes to a couple of lookup tables & adding counts to number of hits for each item in each lookup table.

Uploaded v13 of the requirements (OSC_Bronze_release_planning_v13_2019_11_26.xlsx)

Removed 'dynamic' from all the telemetry epics, as the intended functionality is general configurability of the telemetry options.

Uploaded a contribution on SMO application package schema definition for discussion. Would welcome other proposals so we can agree on the schema definition that we can then use for package definition in Cherry release.

user-59b16, can we use the next RSAC Cherry meeting on Thursday to discuss this.