Add 89 missing ORAN specs (R003/R004) parsed via Datalab Marker (accurate); update manifest + STATUS

.gitattributes

@@ -271,3 +271,91 @@ original/WG8/O-RAN.WG8.TS.AAD.0-R005-v17.00.docx filter=lfs diff=lfs merge=lfs -
 original/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN[[:space:]].X-R005-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
 original/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00.pdf filter=lfs diff=lfs merge=lfs -text
 original/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/SFG/O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/SuFG/O-RAN.SuFG.CE-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/TIFG/O-RAN.TIFG.CGofOTIC.0-v06.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/TIFG/O-RAN.TIFG.E2ETSTFWK.0-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN-WG1-CCIN-TR-R004-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.Information[[:space:]]Model[[:space:]]and[[:space:]]Data[[:space:]]Models-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.Network-Energy-Savings-Technical-Report-R003-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.O1-Interface.0-v04.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.OAM-Architecture-v04.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.Study-on-O-RAN-Slicing-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.TR.Decoupled-SMO-Architecture-R004-v03.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.TR.SA-MVD-R004-v03.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.TR.SMO-INT-R004-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.TS.Slicing-Architecture-R004-v14.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG1/O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG10/O-RAN.WG10.TE&IV-UCR.0-R004-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG10/O-RAN.WG10.TS.O1NRM.0-R004-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG10/O-RAN.WG10.TS.OAM-Architecture-R004-v14.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG10/O-RAN.WG10.TS.OnboardingSMOSGAP.0-R004-v01.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.AppLCM-Security-TR.0-R003-v03.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.Certficate-Management-Framework-TR.0-R004-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.O-CLOUD-Security-Analysis-TR.O-R004-v07.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.OAuth2.0-Security-TR.0-R004-v03.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.Security-Log-Management-TR.O-R004-v05.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.Security-Near-RT-RIC-xApps-TR.0-R003-v05.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TR.Fronthaul-CUSPlane-Security.0-R004-v03.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TR.O-RUCUM-R004-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TR.OAuth2.0-Security.O-R004-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TR.Threat-Modeling.O-R004-v05.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TS.Security-Protocols-Specification.0-R004-v11.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TS.Security-Requirements-Specification.0-R004-v11.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/O-RAN.WG11.TS.Security-Test-Specifications-R004-v09.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG11/ORAN-WG11-SharedORU-Security-Analysis-TR.0-R004-v06.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG2/O-RAN.WG2.AIML-v01.03.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-R004-v06.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-TR-v01.01.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG2/O-RAN.WG2.R1TP-v04.02.docx filter=lfs diff=lfs merge=lfs -text
+original/WG2/O-RAN.WG2.TS.A1TP-R004-v03.04.docx filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.E2TS-R003-v02.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.O1-Interface-for-Near-RT-RIC-R003-v01.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TR.ConMit-R004-v01.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2AP-R004-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2GAP-R004-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2SM-CCC-R004-v05.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2SM-KPM-R004-v06.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2SM-LLC-R004-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2SM-R004-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/O-RAN.WG3.TS.E2SM-RC-R004-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG3/ORAN-WG3.E2SM-NI-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG4/O-RAN.WG4.CTI-TCP.0-R003-v04.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG4/O-RAN.WG4.CTI-TMP.0-R003-v04.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG5/O-RAN.WG5.O-CU-O1.0-R003-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG5/O-RAN.WG5.O-DU-O1.0-R003-v09.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG5/O-RAN.WG5.Transport.0-v01.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG5/O-RAN.WG5.U.0-R003-v07.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN-WG6.AppLCM-Deployment-R003-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL[[:space:]]FEC.R004-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL-Common-API-R003-v08.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL-GAnP-R004-v10.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL-GAnP-R004-v11.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL-HI_PHY-R004-v07.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.AAL-MUMIMO-BF-Calc-Profile-R004-v01.01.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.ASD-R003-v01.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.CADS-v08.01.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.CLOUD-REF-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.O-Cloud[[:space:]]Notification[[:space:]]API-v04.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.O-Cloud-ES-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.O2-GAnP-v01.02.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.TS.O-CLOUD-IM.0-R004-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG6/O-RAN.WG6.TS.O-CLOUD-INTF-CONF-R004-v04.01.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.DSC.0-v04.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.EMC-HAR-HRD.0-R003-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.FHGW-HRD.0-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.IPC-HAR.0-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.IPC-HRD-Opt6-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.IPC-HRD-Opt7-2.0-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.IPC-HRD-Opt8.0-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.IPC-TEST.0-v01.docx filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.NES.0-R003-v02.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.OMAC-HAR.0-v05.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.OMAC-HRD.0-R003-v03.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG7/O-RAN.WG7.OMC-HAR.0-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG8/O-RAN.WG8.IOT.0-R004-v12.00.docx filter=lfs diff=lfs merge=lfs -text
+original/WG9/O-RAN.WG9.XTRP-MGT.0-R004-v09.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG9/O-RAN.WG9.XTRP-REQ-v01.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG9/O-RAN.WG9.XTRP-SYN.0-R004-v06.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG9/O-RAN.WG9.XTRP-TST.0-R004-v05.00.pdf filter=lfs diff=lfs merge=lfs -text
+original/WG9/ORAN-WG9.WDM.0-R004-v05.00.pdf filter=lfs diff=lfs merge=lfs -text

STATUS.md

@@ -2,6 +2,6 @@
 
 State: complete mirror
 
-- Original files: 140
-- Marked documents: 80
+- Original files: 229
+- Marked documents: 170
 - Missing marked documents: 0

manifest.jsonl

@@ -138,3 +138,92 @@
 {"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00.pdf", "original_path": "WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "cdcd99b19b331d2f8c0bbfcd98adf3b33859b27f6ca055ad86631c22131e5151"}
 {"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00.pdf", "original_path": "WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "17fe9e76fcee8460784e7347334b2430574a55d2f64c1ecca838c4200dd9bf45"}
 {"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00.pdf", "original_path": "WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "3752eef2abd845a6be763a218b69162a524d257ca0ccf76fe9e3ac543ae67f2e"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.Information Model and Data Models-v01.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.Information Model and Data Models-v01.00.pdf", "original_path": "WG1/O-RAN.WG1.Information Model and Data Models-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "eca6a3ecf1f34501b1ffa6feb1c7f02db03982c3b0d343c0a758911cb0c42b93"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/TIFG/O-RAN.TIFG.CGofOTIC.0-v06.00/raw.md", "normalized_path": "original/TIFG/O-RAN.TIFG.CGofOTIC.0-v06.00.pdf", "original_path": "TIFG/O-RAN.TIFG.CGofOTIC.0-v06.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "d605211c8ee1f345db812d3e052ec53b0e137d7c8b8c8f9c37c1d4d2a6c2e592"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/SuFG/O-RAN.SuFG.CE-v01.00/raw.md", "normalized_path": "original/SuFG/O-RAN.SuFG.CE-v01.00.pdf", "original_path": "SuFG/O-RAN.SuFG.CE-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b7528ac4539bd4beeef359e60ee97aef9366afaad16c769984565510569e80ce"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN-WG6.AppLCM-Deployment-R003-v02.00/raw.md", "normalized_path": "original/WG6/O-RAN-WG6.AppLCM-Deployment-R003-v02.00.pdf", "original_path": "WG6/O-RAN-WG6.AppLCM-Deployment-R003-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "dd74c19a3a8c9eea64500682af7a572da31fd5c51830bdcf5e356fee5665c7fe"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/SFG/O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00/raw.md", "normalized_path": "original/SFG/O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00.pdf", "original_path": "SFG/O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "41b4e4d600c88bb2e662eb8daf4cbd6a1e2942b5e26b9aaaeeeca55dcc228202"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN-WG1-CCIN-TR-R004-v01.00/raw.md", "normalized_path": "original/WG1/O-RAN-WG1-CCIN-TR-R004-v01.00.pdf", "original_path": "WG1/O-RAN-WG1-CCIN-TR-R004-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "e1310961f80c5d21ef4a2e4a0acac2c9e63ac630172ec0eff0b05e66e00bc1f0"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.OAM-Architecture-v04.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.OAM-Architecture-v04.00.pdf", "original_path": "WG1/O-RAN.WG1.OAM-Architecture-v04.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "355d24fa8c105ad1950ba3f457db646e02028305f8ff05b8e716db2ec4cefa7e"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG1/O-RAN.WG1.TR.SMO-INT-R004-v04.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.TR.SMO-INT-R004-v04.00.docx", "original_path": "WG1/O-RAN.WG1.TR.SMO-INT-R004-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "3af0d214ff8dd6ab599c1791098ea97af47c1e5d04f8ef6564f6b04596996fda"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.O1-Interface.0-v04.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.O1-Interface.0-v04.00.pdf", "original_path": "WG1/O-RAN.WG1.O1-Interface.0-v04.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "e56216c86b396d4c44c3a600f2facf0862b7c706a6b0464824d95f092197a7c2"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.Study-on-O-RAN-Slicing-v02.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.Study-on-O-RAN-Slicing-v02.00.pdf", "original_path": "WG1/O-RAN.WG1.Study-on-O-RAN-Slicing-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "c5ba3f9b6b6714e1a11fe43331d5e2a79dc235fb56ef6c294d0139606cc8f206"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG1/O-RAN.WG1.TR.Decoupled-SMO-Architecture-R004-v03.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.TR.Decoupled-SMO-Architecture-R004-v03.00.docx", "original_path": "WG1/O-RAN.WG1.TR.Decoupled-SMO-Architecture-R004-v03.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "bdfaffe1d62d639bfd999a8793d5e50dce6822aa5e2cf62cf6e9753e1327d08c"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG1/O-RAN.WG1.TR.SA-MVD-R004-v03.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.TR.SA-MVD-R004-v03.00.docx", "original_path": "WG1/O-RAN.WG1.TR.SA-MVD-R004-v03.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b0285e65fad88e4311bf186247b757ef314884583cb6dd3f721298534a9c92b0"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/TIFG/O-RAN.TIFG.E2ETSTFWK.0-v01.00/raw.md", "normalized_path": "original/TIFG/O-RAN.TIFG.E2ETSTFWK.0-v01.00.pdf", "original_path": "TIFG/O-RAN.TIFG.E2ETSTFWK.0-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "bffc70106a976b4a09d432772a122b18362f2a03cf0c50ef8f4cae5acfae7bbf"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG10/O-RAN.WG10.TS.O1NRM.0-R004-v02.00/raw.md", "normalized_path": "original/WG10/O-RAN.WG10.TS.O1NRM.0-R004-v02.00.pdf", "original_path": "WG10/O-RAN.WG10.TS.O1NRM.0-R004-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "accc7c58fa5070d2f7326ef9b0ed71a8e4bf80f97c9867a92bc88b59cdbc58cf"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.Network-Energy-Savings-Technical-Report-R003-v02.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.Network-Energy-Savings-Technical-Report-R003-v02.00.pdf", "original_path": "WG1/O-RAN.WG1.Network-Energy-Savings-Technical-Report-R003-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "821cf468aa81aa0a3170db6003127a148767793e65dd8fa7b10a6b4ad81bf00c"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG10/O-RAN.WG10.TE&IV-UCR.0-R004-v03.00/raw.md", "normalized_path": "original/WG10/O-RAN.WG10.TE&IV-UCR.0-R004-v03.00.pdf", "original_path": "WG10/O-RAN.WG10.TE&IV-UCR.0-R004-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "a062d4ce0974781a819be6bf347762fa3d1ee368c50ce2d492065e7bf0515da9"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG10/O-RAN.WG10.TS.OnboardingSMOSGAP.0-R004-v01.00/raw.md", "normalized_path": "original/WG10/O-RAN.WG10.TS.OnboardingSMOSGAP.0-R004-v01.00.docx", "original_path": "WG10/O-RAN.WG10.TS.OnboardingSMOSGAP.0-R004-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5609c8a40f0d12bf6c554a5fea49f0159c7d3560c6d55678474b71731773585d"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.AppLCM-Security-TR.0-R003-v03.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.AppLCM-Security-TR.0-R003-v03.00.docx", "original_path": "WG11/O-RAN.WG11.AppLCM-Security-TR.0-R003-v03.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "3eda2f9bbaaee413926dfecbbbd294489f176ceff7f8ad3ae153c0ee3ce12eab"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.Certficate-Management-Framework-TR.0-R004-v04.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.Certficate-Management-Framework-TR.0-R004-v04.00.docx", "original_path": "WG11/O-RAN.WG11.Certficate-Management-Framework-TR.0-R004-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "9f55f030a98ed4f88d7b96552d388cc8bb28b2c0c76445b0a45e87394793aa17"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.OAuth2.0-Security-TR.0-R004-v03.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.OAuth2.0-Security-TR.0-R004-v03.00.docx", "original_path": "WG11/O-RAN.WG11.OAuth2.0-Security-TR.0-R004-v03.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5d3d4693a904bc47fa5268456ae19ca4b6b70d2102229dfd5ff2fd5b2ad33fe6"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TR.O-RUCUM-R004-v04.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TR.O-RUCUM-R004-v04.00.docx", "original_path": "WG11/O-RAN.WG11.TR.O-RUCUM-R004-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "0031175d6eed1efdc73886b5f49478e9e50401dbdefadc08092781e5092fb4b8"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00.pdf", "original_path": "WG1/O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "042ac1000d6031ab80758e62902e723e7c2c6f21d2e7b51954e2a44e6c19831e"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG10/O-RAN.WG10.TS.OAM-Architecture-R004-v14.00/raw.md", "normalized_path": "original/WG10/O-RAN.WG10.TS.OAM-Architecture-R004-v14.00.pdf", "original_path": "WG10/O-RAN.WG10.TS.OAM-Architecture-R004-v14.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "29ec376fc9fc4992f93107c9172873eed4236e4f022b944a46c2e40eaf39a0a2"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.Security-Log-Management-TR.O-R004-v05.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.Security-Log-Management-TR.O-R004-v05.00.docx", "original_path": "WG11/O-RAN.WG11.Security-Log-Management-TR.O-R004-v05.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b527e25202264851de2f2fb680fd27de35d695feda7ec6edd8bd5de3a6e11f72"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TR.OAuth2.0-Security.O-R004-v04.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TR.OAuth2.0-Security.O-R004-v04.00.docx", "original_path": "WG11/O-RAN.WG11.TR.OAuth2.0-Security.O-R004-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "67f5af4b48ae03d550dd72ae6461fb9dcc2a10ac3e87c9040d1ef562af0913aa"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TS.Security-Protocols-Specification.0-R004-v11.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TS.Security-Protocols-Specification.0-R004-v11.00.docx", "original_path": "WG11/O-RAN.WG11.TS.Security-Protocols-Specification.0-R004-v11.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "f9b1398169c15cec27d92c5316cadada784ea03ea4a5536215b38bce89a839a0"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.Security-Near-RT-RIC-xApps-TR.0-R003-v05.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.Security-Near-RT-RIC-xApps-TR.0-R003-v05.00.docx", "original_path": "WG11/O-RAN.WG11.Security-Near-RT-RIC-xApps-TR.0-R003-v05.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "6533556b7bd530b9ddd40b9d4fd9fc83768bfe46c08cb2380970fd621115b198"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TR.Fronthaul-CUSPlane-Security.0-R004-v03.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TR.Fronthaul-CUSPlane-Security.0-R004-v03.00.docx", "original_path": "WG11/O-RAN.WG11.TR.Fronthaul-CUSPlane-Security.0-R004-v03.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "a52e8b1892429a6bca4d06d6b26e244bc184fdb1f2fe91de4358012909b9239e"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.O-CLOUD-Security-Analysis-TR.O-R004-v07.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.O-CLOUD-Security-Analysis-TR.O-R004-v07.00.docx", "original_path": "WG11/O-RAN.WG11.O-CLOUD-Security-Analysis-TR.O-R004-v07.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "a78561e0859782bc217b00b2356ec944c79ea782974857b4d628caeac95b8343"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG2/O-RAN.WG2.R1TP-v04.02/raw.md", "normalized_path": "original/WG2/O-RAN.WG2.R1TP-v04.02.docx", "original_path": "WG2/O-RAN.WG2.R1TP-v04.02.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "84f23dfb6f143926e416622ab7e3ac3e55bfc162bdc65b99af66da7246dbc2a4"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG2/O-RAN.WG2.TS.A1TP-R004-v03.04/raw.md", "normalized_path": "original/WG2/O-RAN.WG2.TS.A1TP-R004-v03.04.docx", "original_path": "WG2/O-RAN.WG2.TS.A1TP-R004-v03.04.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b40117b8c69c774f65694e0894690bedb6c1b23c334ad66c8c22b174418aa750"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-TR-v01.01/raw.md", "normalized_path": "original/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-TR-v01.01.pdf", "original_path": "WG2/O-RAN.WG2.Non-RT-RIC-ARCH-TR-v01.01.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "366cb05674d3104148c4e2a83610bb441d6a38dfc97dadf76c0b23d8db915f8f"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG2/O-RAN.WG2.AIML-v01.03/raw.md", "normalized_path": "original/WG2/O-RAN.WG2.AIML-v01.03.pdf", "original_path": "WG2/O-RAN.WG2.AIML-v01.03.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "afd260f0360d91e64516f637c17bdd25f24ec5594fe67429a48b5ffd69e4611c"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-R004-v06.00/raw.md", "normalized_path": "original/WG2/O-RAN.WG2.Non-RT-RIC-ARCH-R004-v06.00.docx", "original_path": "WG2/O-RAN.WG2.Non-RT-RIC-ARCH-R004-v06.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "37f5a26a106959e9ef264208d46972f08349132e39137e3e2fecf30d376bf71b"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG3/O-RAN.WG3.TR.ConMit-R004-v01.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TR.ConMit-R004-v01.00.docx", "original_path": "WG3/O-RAN.WG3.TR.ConMit-R004-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "bade55c3789c24f108f393f3dbbef2341cb46e67e5327e93060f99a727588e94"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2GAP-R004-v07.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2GAP-R004-v07.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2GAP-R004-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "9b28f7730c4f80d854bb2461d8df8d7f4716a24255281e845c366fc382b6b9e8"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2SM-LLC-R004-v01.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2SM-LLC-R004-v01.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2SM-LLC-R004-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b917d19e4dfbf6d5efca202012468f1b55b490937fb20b2f01f87a0953f37790"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2SM-KPM-R004-v06.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2SM-KPM-R004-v06.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2SM-KPM-R004-v06.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "950b9296382cbcbbb6b93bc1c34429ea8a10526174bb2e6afef4cbbdb4ba1946"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2SM-CCC-R004-v05.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2SM-CCC-R004-v05.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2SM-CCC-R004-v05.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "743bcbad23ecf20c7c6f2f31c1ede85b79688e6ff51eddf432b331a04852cc16"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG3/O-RAN.WG3.E2TS-R003-v02.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.E2TS-R003-v02.00.docx", "original_path": "WG3/O-RAN.WG3.E2TS-R003-v02.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "c7b25fb7d7f0269f03a75762c58d25316fb1384fb1e81f6f9b5dc274ddadf950"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2SM-R004-v07.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2SM-R004-v07.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2SM-R004-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "356eb9c84a4b11032051ad402659bc29c883b3a3267fec68b3559f6771de47e6"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TS.Security-Requirements-Specification.0-R004-v11.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TS.Security-Requirements-Specification.0-R004-v11.00.docx", "original_path": "WG11/O-RAN.WG11.TS.Security-Requirements-Specification.0-R004-v11.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "04435d0c9a9d3e57bd7af4a0e35ebf0657636239227565c1cbb94af7d0721c44"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TS.Security-Test-Specifications-R004-v09.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TS.Security-Test-Specifications-R004-v09.00.docx", "original_path": "WG11/O-RAN.WG11.TS.Security-Test-Specifications-R004-v09.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "76c9177987feebc9a5305a8b3e9da54d5a69d2604d1615c2e425113b85777a9f"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2AP-R004-v07.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2AP-R004-v07.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2AP-R004-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5393fd8ae38bd3999473669ef3aba8d010157f044476ed275efe956c90d4f2ac"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/O-RAN.WG11.TR.Threat-Modeling.O-R004-v05.00/raw.md", "normalized_path": "original/WG11/O-RAN.WG11.TR.Threat-Modeling.O-R004-v05.00.docx", "original_path": "WG11/O-RAN.WG11.TR.Threat-Modeling.O-R004-v05.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "2bad8afd31bdfb02b821007996a52de1e24108af5b7a47657950c5a6441c8c4a"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG5/O-RAN.WG5.Transport.0-v01.00/raw.md", "normalized_path": "original/WG5/O-RAN.WG5.Transport.0-v01.00.docx", "original_path": "WG5/O-RAN.WG5.Transport.0-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "9a87fa76d6536fe726eb1eb24ac0cc73c52d60708c33df1536e30628c16196c5"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG5/O-RAN.WG5.U.0-R003-v07.00/raw.md", "normalized_path": "original/WG5/O-RAN.WG5.U.0-R003-v07.00.docx", "original_path": "WG5/O-RAN.WG5.U.0-R003-v07.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "2211fac297e198afb1cfcb95e6392b42d9d88d61b22f1ea67bbf5ae0a626767a"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG4/O-RAN.WG4.CTI-TCP.0-R003-v04.00/raw.md", "normalized_path": "original/WG4/O-RAN.WG4.CTI-TCP.0-R003-v04.00.pdf", "original_path": "WG4/O-RAN.WG4.CTI-TCP.0-R003-v04.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "9c108c795dc448880b5905878ed4618b205017c9ca5b1e013733d25ad6415253"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG6/O-RAN.WG6.AAL FEC.R004-v04.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL FEC.R004-v04.00.docx", "original_path": "WG6/O-RAN.WG6.AAL FEC.R004-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ff7ab08dcfbb2bbfdd2f7b9fb3cb82da860f4f7c707e064ceb9f15c266ece98f"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG4/O-RAN.WG4.CTI-TMP.0-R003-v04.00/raw.md", "normalized_path": "original/WG4/O-RAN.WG4.CTI-TMP.0-R003-v04.00.pdf", "original_path": "WG4/O-RAN.WG4.CTI-TMP.0-R003-v04.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "802f2868e5a515ec085542477e53c82b23538ec5567b3cf3b26cac39ed25f7ae"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.AAL-MUMIMO-BF-Calc-Profile-R004-v01.01/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL-MUMIMO-BF-Calc-Profile-R004-v01.01.pdf", "original_path": "WG6/O-RAN.WG6.AAL-MUMIMO-BF-Calc-Profile-R004-v01.01.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "54235c70ad3969df02226a7b632ba2f49e6b5658aba56209440c62789b45c62e"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG5/O-RAN.WG5.O-CU-O1.0-R003-v07.00/raw.md", "normalized_path": "original/WG5/O-RAN.WG5.O-CU-O1.0-R003-v07.00.pdf", "original_path": "WG5/O-RAN.WG5.O-CU-O1.0-R003-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b760bcdfb863171c1cd88dbe021a911328a9a9fd420ef06f6ac04be330ca787e"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.AAL-Common-API-R003-v08.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL-Common-API-R003-v08.00.pdf", "original_path": "WG6/O-RAN.WG6.AAL-Common-API-R003-v08.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "090330c278bf4400f2cff7743b25e7161f70a1c99f0d5b4a4d072b20d6f36048"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG6/O-RAN.WG6.ASD-R003-v01.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.ASD-R003-v01.00.docx", "original_path": "WG6/O-RAN.WG6.ASD-R003-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "09e9e9f0e75fd15924ec0acda441304cf47ac9da146a9fdcb30b69a85fd879cc"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG5/O-RAN.WG5.O-DU-O1.0-R003-v09.00/raw.md", "normalized_path": "original/WG5/O-RAN.WG5.O-DU-O1.0-R003-v09.00.pdf", "original_path": "WG5/O-RAN.WG5.O-DU-O1.0-R003-v09.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ab8fffc95cc878329133f5eea4a00520fe7b643327f33add5aae4fba62bd49ed"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.AAL-HI_PHY-R004-v07.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL-HI_PHY-R004-v07.00.pdf", "original_path": "WG6/O-RAN.WG6.AAL-HI_PHY-R004-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ced86ef8813d6d5e86848f561af1e13b98f5341e577d122b73b803b19c5804aa"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.AAL-GAnP-R004-v11.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL-GAnP-R004-v11.00.pdf", "original_path": "WG6/O-RAN.WG6.AAL-GAnP-R004-v11.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "e08ae35486f62d0b2dd74b87fd6e733bb48f0826755d1ebccb9be9743100bcf6"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG6/O-RAN.WG6.AAL-GAnP-R004-v10.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.AAL-GAnP-R004-v10.00.docx", "original_path": "WG6/O-RAN.WG6.AAL-GAnP-R004-v10.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "f3b518bb23d8bddfa7303e66f5658da8e2c347f514a335c029e513c296a83c8f"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.O2-GAnP-v01.02/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.O2-GAnP-v01.02.pdf", "original_path": "WG6/O-RAN.WG6.O2-GAnP-v01.02.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "713f3370a2b05ec2b0ac7c665672095ef594596888e7c186b402fb0b0e4f480c"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.O-Cloud-ES-v02.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.O-Cloud-ES-v02.00.pdf", "original_path": "WG6/O-RAN.WG6.O-Cloud-ES-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "be84efe2ede6ce12dcf3324f9ca5de810b53570aa237fb1a4c33209840e39a8a"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG6/O-RAN.WG6.O-Cloud Notification API-v04.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.O-Cloud Notification API-v04.00.docx", "original_path": "WG6/O-RAN.WG6.O-Cloud Notification API-v04.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ba8b2c0c78ca4ff646de1e0d54c3452bec6aabbd1bfba05ef4896e1bda70d6c7"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/O-RAN.WG3.TS.E2SM-RC-R004-v07.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.TS.E2SM-RC-R004-v07.00.pdf", "original_path": "WG3/O-RAN.WG3.TS.E2SM-RC-R004-v07.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ffd8b69f954152a3d92a0dfb6ed1d029b6cde0711a90ade4c885adf276d78adf"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.CLOUD-REF-v02.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.CLOUD-REF-v02.00.pdf", "original_path": "WG6/O-RAN.WG6.CLOUD-REF-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "2d866f86e5e3a5f66211995a7274475aa2b81f57c95b8e7851a32c79c3121826"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.CADS-v08.01/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.CADS-v08.01.pdf", "original_path": "WG6/O-RAN.WG6.CADS-v08.01.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "e94cd5bf1cb98420bd9899c863c8875744f197f4ad9a0f728f4014170d47f57f"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG6/O-RAN.WG6.O2-IMS-K8s-R003-v01.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.O2-IMS-K8s-R003-v01.00.docx", "original_path": "WG6/O-RAN.WG6.O2-IMS-K8s-R003-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "2a64c20b788444340df053e67f12973014d3434319a2ab78f046cfeefb31d8cd"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.DSC.0-v04.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.DSC.0-v04.00.pdf", "original_path": "WG7/O-RAN.WG7.DSC.0-v04.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "9fe1cd2120c05b3f9492733f8374f4d4a976f69c06870c5677ee462f30353e15"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG1/O-RAN.WG1.TS.Slicing-Architecture-R004-v14.00/raw.md", "normalized_path": "original/WG1/O-RAN.WG1.TS.Slicing-Architecture-R004-v14.00.pdf", "original_path": "WG1/O-RAN.WG1.TS.Slicing-Architecture-R004-v14.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "cefaf25a5e01606cef1ad16bac934218fbadbcfa371b10033a011ae2acb24e48"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.FHGW-HRD.0-v02.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.FHGW-HRD.0-v02.00.pdf", "original_path": "WG7/O-RAN.WG7.FHGW-HRD.0-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "76f4e742bf4d832ce1c9e1a832795742c93b91f967294c0bb21eea7565681688"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.IPC-HAR.0-v03.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.IPC-HAR.0-v03.00.pdf", "original_path": "WG7/O-RAN.WG7.IPC-HAR.0-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "841ea58c835dc1a20e3fda2598987a149d535f2a6fa3b094902a25d763370248"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.TS.O-CLOUD-INTF-CONF-R004-v04.01/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.TS.O-CLOUD-INTF-CONF-R004-v04.01.pdf", "original_path": "WG6/O-RAN.WG6.TS.O-CLOUD-INTF-CONF-R004-v04.01.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "cf45238aed538d0f7d9bb3b35bbd1d7dfe05329fa7411a2669a4a724a621438b"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG6/O-RAN.WG6.TS.O-CLOUD-IM.0-R004-v03.00/raw.md", "normalized_path": "original/WG6/O-RAN.WG6.TS.O-CLOUD-IM.0-R004-v03.00.pdf", "original_path": "WG6/O-RAN.WG6.TS.O-CLOUD-IM.0-R004-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "56e85081f7282d916e822ac69feefbb96e25845be6102bae950dbb9a6b6ced23"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.IPC-HRD-Opt6-v02.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.IPC-HRD-Opt6-v02.00.pdf", "original_path": "WG7/O-RAN.WG7.IPC-HRD-Opt6-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "62c6c9f515c3764ffd7c905c598ee1873949bd6b02e4a8a286d10e478025bbb0"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.NES.0-R003-v02.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.NES.0-R003-v02.00.pdf", "original_path": "WG7/O-RAN.WG7.NES.0-R003-v02.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b42f07afcbced219d64d3c7a7496063a10d49d43cab41ec7e7e84aab235c1de7"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG7/O-RAN.WG7.IPC-TEST.0-v01/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.IPC-TEST.0-v01.docx", "original_path": "WG7/O-RAN.WG7.IPC-TEST.0-v01.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "d25fb773649cf3b21dac84dfa51b9b7e63fcc0ab417f0032ab58fc3b802efbfc"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.EMC-HAR-HRD.0-R003-v01.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.EMC-HAR-HRD.0-R003-v01.00.pdf", "original_path": "WG7/O-RAN.WG7.EMC-HAR-HRD.0-R003-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "d9eeced166f401dbbefb757e1b87651e13c715261d681009c8a4d6ee0ae428e7"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.OMC-HAR.0-v01.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.OMC-HAR.0-v01.00.pdf", "original_path": "WG7/O-RAN.WG7.OMC-HAR.0-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "2e8e9c983e097db97fab48dbedc32db2f006ccddbad820b63fd41147f8935222"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.OMAC-HAR.0-v05.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.OMAC-HAR.0-v05.00.pdf", "original_path": "WG7/O-RAN.WG7.OMAC-HAR.0-v05.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "78ffc4476839dd0ecda54f1c1c8bf29db073fda34d1f7b5419193219f40129b8"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.IPC-HRD-Opt7-2.0-v03.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.IPC-HRD-Opt7-2.0-v03.00.pdf", "original_path": "WG7/O-RAN.WG7.IPC-HRD-Opt7-2.0-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "ec5482e51b98d940764ea8243de97f405fcb0f35f4d7d25801f8dd244763bb41"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.OMAC-HRD.0-R003-v03.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.OMAC-HRD.0-R003-v03.00.pdf", "original_path": "WG7/O-RAN.WG7.OMAC-HRD.0-R003-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "b37f100898bfb7f40f0bdebb987c81d9a9ddc42581d65ccff9d869ed83bceba4"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG3/ORAN-WG3.E2SM-NI-v01.00/raw.md", "normalized_path": "original/WG3/ORAN-WG3.E2SM-NI-v01.00.pdf", "original_path": "WG3/ORAN-WG3.E2SM-NI-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "1f5e1012fb2d434e2088c54f5ec04d9bfc3c783f8476db913b8dfd7053fc5dfe"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XTRP-REQ-v01.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XTRP-REQ-v01.00.pdf", "original_path": "WG9/O-RAN.WG9.XTRP-REQ-v01.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5fb7291d88b92c1f554fd720d7b28fa6e0458f2feae9eb6c2248ffdc441a648b"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG3/O-RAN.WG3.O1-Interface-for-Near-RT-RIC-R003-v01.00/raw.md", "normalized_path": "original/WG3/O-RAN.WG3.O1-Interface-for-Near-RT-RIC-R003-v01.00.docx", "original_path": "WG3/O-RAN.WG3.O1-Interface-for-Near-RT-RIC-R003-v01.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "a8d98799bcff1b923aea0d8a0fb3855f42ae4d0ae66181f8ba6afd9256bb7195"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG11/ORAN-WG11-SharedORU-Security-Analysis-TR.0-R004-v06.00/raw.md", "normalized_path": "original/WG11/ORAN-WG11-SharedORU-Security-Analysis-TR.0-R004-v06.00.docx", "original_path": "WG11/ORAN-WG11-SharedORU-Security-Analysis-TR.0-R004-v06.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "7bece6f5f7b092cb31663c7d62d09e4e2ce574fe578f6a2fd6a70969b1f1dc32"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG7/O-RAN.WG7.IPC-HRD-Opt8.0-v03.00/raw.md", "normalized_path": "original/WG7/O-RAN.WG7.IPC-HRD-Opt8.0-v03.00.pdf", "original_path": "WG7/O-RAN.WG7.IPC-HRD-Opt8.0-v03.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "081806fa7e36a58dc6bfed233e59c31414e1c16f8ac190a01bafd6ba7edfd114"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/ORAN-WG9.WDM.0-R004-v05.00/raw.md", "normalized_path": "original/WG9/ORAN-WG9.WDM.0-R004-v05.00.pdf", "original_path": "WG9/ORAN-WG9.WDM.0-R004-v05.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "61ea3061689f7a39cd281e6d2c9e987d4d6a9c937d9b9d4a9a575fe78361b2ef"}
+{"body": "oran", "file_type": ".docx", "marked_path": "marked/WG8/O-RAN.WG8.IOT.0-R004-v12.00/raw.md", "normalized_path": "original/WG8/O-RAN.WG8.IOT.0-R004-v12.00.docx", "original_path": "WG8/O-RAN.WG8.IOT.0-R004-v12.00.docx", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "98b6a42a0cdf86b628555df316215875cde0870719f902f0e8a95ec5fdc2d56e"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XTRP-TST.0-R004-v05.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XTRP-TST.0-R004-v05.00.pdf", "original_path": "WG9/O-RAN.WG9.XTRP-TST.0-R004-v05.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5867d6330eadc4c90f94b922e710e7df951361b93c5217e8b38e5c2f76317c0d"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XTRP-MGT.0-R004-v09.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XTRP-MGT.0-R004-v09.00.pdf", "original_path": "WG9/O-RAN.WG9.XTRP-MGT.0-R004-v09.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "5c62d41e7a6dc7c1e32e8a3956b52392855a7b1ffea58728ea61bf0cc373f33b"}
+{"body": "oran", "file_type": ".pdf", "marked_path": "marked/WG9/O-RAN.WG9.XTRP-SYN.0-R004-v06.00/raw.md", "normalized_path": "original/WG9/O-RAN.WG9.XTRP-SYN.0-R004-v06.00.pdf", "original_path": "WG9/O-RAN.WG9.XTRP-SYN.0-R004-v06.00.pdf", "parse_status": "OK", "reason": "parsed", "section": "original", "sha256": "3af9137f21dcdcc5cf9f0335265b1aa04aaad4669607bae3cd97c481b827607e"}

marked/SuFG/O-RAN.SuFG.CE-v01.00/raw.md

@@ -0,0 +1,465 @@
+
+
+# --- **O-RAN Focus Group (Sustainability Focus Group)****Circular economy guidelines on network equipment**
+
+Copyright © 2022 by the O-RAN ALLIANCE e.V.
+
+The copying or incorporation into any other work of part or all of the material available in this document in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this document for your personal use, or copy the material of this document for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
+
+O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
+
+# --- Contents
+
+|                                                       |    |
+|-------------------------------------------------------|----|
+| List of figures .....                                 | 3  |
+| List of tables .....                                  | 3  |
+| Foreword.....                                         | 4  |
+| Modal verbs terminology .....                         | 4  |
+| Executive summary .....                               | 4  |
+| Introduction .....                                    | 4  |
+| 1 Scope .....                                         | 5  |
+| 2 References .....                                    | 5  |
+| 2.1 Informative references .....                      | 5  |
+| 3 Definition of terms, symbols and abbreviations..... | 6  |
+| 3.1 Terms .....                                       | 6  |
+| 3.2 Symbols .....                                     | 6  |
+| 3.3 Abbreviations.....                                | 6  |
+| 4 Circular economy on network equipment .....         | 7  |
+| 4.1 O-CU/O-DU .....                                   | 13 |
+| 4.2 O-RU .....                                        | 14 |
+| A.1 Equipment lifecycle aspects to consider .....     | 16 |
+| Revision history .....                                | 17 |
+| History .....                                         | 17 |
+
+# --- List of figures
+
+|                                                                                |    |
+|--------------------------------------------------------------------------------|----|
+| Figure A.1-1: Reduction of environmental impact through circular economy ..... | 16 |
+|--------------------------------------------------------------------------------|----|
+
+# --- List of tables
+
+|                                                                                            |    |
+|--------------------------------------------------------------------------------------------|----|
+| Table 4-1 Circularity aspects and indicators applicable on network equipment .....         | 8  |
+| Table 4-2 Priority level definition based on contribution effect to circular economy ..... | 13 |
+| Table 4.1-1 O-CU/O-DU priority definition based on circularity economy effect .....        | 13 |
+| Table 4.2-1 O-RU priority definition based on circularity economy effect .....             | 14 |
+
+# --- Foreword
+
+This Technical Report (TR) has been produced by O-RAN Alliance.
+
+---
+
+## Modal verbs terminology
+
+In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
+
+"must" and "must not" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
+
+---
+
+# Executive summary
+
+The implementation of circular economy transformative model on the telecommunications industry and its network equipment promotes the move to more sustainable business models. It favours both the manufacture of products with eco-design criteria, and the reuse and recycling of these at the end of their useful life. It also contributes to reducing the risk of resource depletion, provides continuity to the supply chain (components, critical raw materials, etc.) and helps reduce GHG emissions.
+
+This document defines circular economy criteria aspects and indicators applicable on network equipment based on the recommendation ITU-T L.1023 (08/2023) "Assessment method for circularity performance scoring", with the intention to reduce environmental impact through the homogenization and prioritization of said criteria based on the network equipment and its impact on the contribution to the circular economy model.
+
+---
+
+# Introduction
+
+Circular economy model reduces environmental impact supporting the reduction of material use, recycling, and recovering of product, product parts, components, and materials to circulate them in the value chain for as long as possible.
+
+The present document identifies circular economy aspects and indicators applicable on network equipment such as: O-CU, O-DU and O-RU including their respective description, contribution and non-contribution cases to circular economy and priority level according to the effect (for customer, environment etc.) of the indicator at hand.
+
+The objective of this information is to homogenize circularity criteria applicable to network equipment with the aim of reducing its environmental impact during the different phases involved in its life cycle, through improvements that allow achieving the greatest positive effect that contributes to the circular economy in aspects such as: product durability, ability to recycle, repair, reuse, upgrade at equipment level, and finally ability to recycle, repair, reuse, upgrade at manufacturer level. This goal will involve cooperation with stakeholders along the whole of the value chain.
+
+These guidelines are based on the latest recommendation ITU-T L.1023 (08/2023) "Assessment method for circularity performance scoring". Scoring methodology is out of scope on this document.
+
+# --- 1 Scope
+
+The contents of the present document are subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN Alliance modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
+
+version xx.yy.zz
+
+where:
+
+xx: the first digit-group is incremented for all changes of substance, i.e., technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
+
+yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
+
+zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
+
+The present document specifies circular economy criterias guidelines involved from the design & manufacturing to end of the equipment lifecycle applicable in OPEN RAN network equipment, such as: O-CU, O-DU and O-RU, with the intention of creating common aspects and indicators that are necessary to analyze the degree of maturity of the circular economy by network equipment.
+
+# --- 2 References
+
+## 2.1 Informative references
+
+References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.
+
+NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
+
+The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.
+
+[i.1] ITU-T L.1023 2.0/August 2023: "Assessment method for circularity performance scoring".
+
+[i.2] GSMA /March 2022: "Strategy Paper for Circular Economy: Network equipment".
+
+[i.3] NGMN 1.0/July 2021: " Green Future Networks. Network Equipment Eco-Design and End to End Service Footprint".
+
+# 3 Definition of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the following terms apply:
+
+**Circular economy** [ITU-T L.1020]: A circular economy is restorative and regenerative by design, and aims to keep products, components, and materials at their highest utility and value at all times while reducing waste streams. A concept that distinguishes between technical and biological cycles, the circular economy is a continuous, positive development cycle. It preserves and enhances natural capital, optimises resource yields, and minimises system risks by managing finite stocks and renewable flows, while reducing waste streams.
+
+**ICT goods** [b-ITU-T L.1410]: Tangible goods deriving from or making use of technologies devoted to or concerned with:
+
+- the acquisition, storage, manipulation (including transformation), management, movement, control, display, switching, interchange, transmission or reception of a diversity of data;
+- the development and use of the hardware, software, and procedures associated with this delivery; and
+- the representation, transfer, interpretation, and processing of data among persons, places, and machine
+
+**O-CU:** O-RAN Central Unit [O-RAN.WG1.Use-Cases-Detailed-Specification-R003-v11.00]: a logical node hosting O-CU-CP and O-CU-UPO-DU: O-RAN Distributed Unit: a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
+
+**O-DU:** O-RAN Distributed Unit [O-RAN.WG1.Use-Cases-Detailed-Specification-R003-v11.00]: a Logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
+
+**O-RU:** O-RAN Radio Unit [O-RAN.WG1.Use-Cases-Detailed-Specification-R003-v11.00]: a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction)
+
+**RAN** [O-RAN.WG1.Use-Cases-Detailed-Specification-R003-v11.00]: Generally referred as Radio Access Network. In terms of this document, any component below near-RT RIC per O-RAN architecture, including O-CU/O-DU/O-RU
+
+## 3.2 Symbols
+
+Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the [following] abbreviations [given in i.1 and the following] apply:
+
+|      |                                          |
+|------|------------------------------------------|
+| CE   | Circular Economy                         |
+| ICT  | Information and communication technology |
+| NE   | Network equipment                        |
+| O-CU | O-RAN Central Unit                       |
+
+|      |                                                                    |
+|------|--------------------------------------------------------------------|
+| O-DU | O-RAN Distributed Unit                                             |
+| O-RU | O-RAN Radio Unit                                                   |
+| PD   | Product durability                                                 |
+| RAN  | Radio Access Network                                               |
+| 3Rue | Ability to Recycle, Repair, Reuse, and Upgrade, Equipment level    |
+| 3Rum | Ability to Recycle, Repair, Reuse, and Upgrade, Manufacturer level |
+
+# 4 Circular economy on network equipment
+
+Based on ITU-T L.1023 recommendation, there is a three-step methodology to identify an information and communication technology (ICT) good's circularity in three dimensions via three circularity aspects: first, the ICT good durability, second, the ICT good ability to be recycled, repaired, reused and upgraded; and third, the manufacturers ability to recycle, repair, reuse and upgrade the ICT good put into the market. The three aspects are then divided into indicators for circular product design.
+
+In this document the circularity indicators are then assessed at three levels, applicability identification on network equipment (O-CU, O-DU and O-RU), how well circularity has been achieved and priority level according to the effect (for customer, environment etc) of the indicator at hand.
+
+Table 1 – Circularity Aspects – contains a list of circular principles that put all the indicators into different aspects. The description of each aspect is as follows:
+
+1. **Product durability (PD):** It included indicators related to promoting the life span and durability of products by adapting their design and upgrading software to a new version and service support by ensuring the product can be used for as long as possible by the first user or subsequent users.
+2. **Ability to recycle, repair, reuse, upgrade (3Rue) – equipment level:** It includes indicators related to the product's structure and access to its priority parts for repair, connecting, systems to facilitate disassembly and reassembly, spare parts, diagnostic and information availability. It relates to:
+  - a. Possibilities to refurbish the ICT good;
+  - b. Possibilities to reuse product parts and components within the ICT good (after first use) in refurbishment of similar or other ICT goods;
+  - c. Facilitate the identification, separation and recycling of materials. Addresses separate collection of products for better recycling and development of designated recycling technologies.
+3. **Ability to recycle, repair, reuse, upgrade (3Rum) – manufacturer level:** It includes indicators related to the manufacturer ability (on company level) to facilitate recycling, repair, reuse, and upgrade. These requirements are not directly connected to the equipment, but to the infrastructure and support to be developed or supported by the manufacturer. It relates to:
+  - a. Availability of service support in terms of information, infrastructure, and spare parts.
+
+**Table 4-1 Circularity aspects and indicators applicable on network equipment**
+
+| Product Durability                                                                                                                                               | Recycle, repair, reuse, upgrade<br>(Equipment level)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Recycle, repair, reuse, upgrade<br>(Manufacturer level)                                                                                                                                                                                                                                                                    |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <ul style="list-style-type: none"> <li>• Software and data support</li> <li>• Scratch resistance</li> <li>• Maintenance support</li> <li>• Robustness</li> </ul> | <ul style="list-style-type: none"> <li>• Fasteners and connectors</li> <li>• Diagnostic support</li> <li>• Material recycling compatibility - Plastic parts</li> <li>• Material recycling compatibility - Metal parts</li> <li>• Recycled/renewable plastics</li> <li>• Recycled metals</li> <li>• Material identification</li> <li>• Hazardous substances (Bromine and Chlorine)</li> <li>• Critical raw materials</li> <li>• Packaging recycling</li> <li>• Technical performance product mass-based material efficiency</li> </ul> | <ul style="list-style-type: none"> <li>• Service offered by manufacturer</li> <li>• Spare parts distribution</li> <li>• Spare parts availability</li> <li>• Disassembly information</li> <li>• Collection and recycling programmes</li> <li>• Environmental footprint assessment knowledge publically available</li> </ul> |
+
+In terms of network equipment circularity aspects and indicators and based on the latest publication of ITU-T L.1023 recommendation, two indicators such as: Battery for portable ICT goods and Data security have been excluded on the table above as they are not applicable on network equipment.
+
+In summary, each group contains a set of indicators that directly address the group's topic. The proposed table is in principle unlimited regarding the number of groups and indicators. For example, new indicators for scratch resistance for example for metals, glass, etc. can be added with their respective circularity contribution scenarios. Also new groups can be added accordingly.
+
+Following the second level of assessment of this document, below is described definition and contribution cases to circular economy of each indicator per aspect:
+
+## 1. Product durability
+
+**1.1. Software and data support:** Availability of software and firmware updates & upgrades (according to EN 45554).
+
+- The most contributing variable to the circularity of the equipment: Software and firmware updates & upgrades availability can be categorized as long-term (class A, i.e., for a duration of time that reflects the expected maximum useful life of the product, cf. EN 45554).
+- Does not contribute to the circular economy of the equipment: No information on duration of availability (class D, cf. EN 45554) is provided on software and firmware updates & upgrades availability.
+
+**1.2. Scratch resistance:** Resistance of housing parts subject to be scratched (resistance regarding ASTM D3363 – 05 (2011) e2 standard.)
+
+- The most contributing variable to the circularity of the equipment: Plastic scratch resistance equal or greater than 2H.
+- Does not contribute to the circular economy of the equipment: Plastic scratch resistance lower or equal to B.
+
+**1.3. Maintenance support:** Availability of consumables, wear-out parts expected to be replaced periodically and availability of maintenance infrastructure (according to EN 45554).
+
+- The most contributing variable to the circularity of the equipment: Consumables and wear-out parts expected to be replaced periodically can be categorized as publicly available (class A in EN 45554) or as available to independent maintenance service providers (class B in EN 45554).
+- Does not contribute to the circular economy of the equipment: Consumables and wear-out parts expected to be replaced periodically can be categorized as not available (class E in EN 45554). No maintenance infrastructure are offered by manufacturer.
+
+**1.4. Robustness:** Refers to the ability of the equipment to tolerate or resist perturbations that may affect its functional body. If the equipment is robust, it has greater durability and is therefore better from a circular economy point of view.
+
+- The most contributing variable to the circularity of the equipment: The product's design features have better characteristics than the minimum requirements for the environmental class in which the product is intended to be used and comply to the enhanced requirements (Example: a product intended to be used in non-weather protected location and satisfies the requirements of class 4.1E (extended severity level) of [b-EN 300 019-1-4] instead of class 4.1 (minimum severity level) and complies to the enhanced requirements of ITU-T K.20/21/45).
+- Does not contribute to the circular economy of the equipment: The product's design features characteristics do not comply to several of the minimum requirements for the environmental class in which the product is intended to be used.
+
+## 2. Recycle, repair, reuse, upgrade – Equipment level
+
+**2.1. Fasteners and connectors:** Fasteners, connectors and tools used to disassemble parts that are likely to need replacement during the expected lifetime of the product are reusable/removable per EN 45554.
+
+- The most contributing variable to the circularity of the equipment: Fasteners and connectors can be categorized as reusable (class A) and using no tools, basic tools or product specific tools (classes A-C as defined in EN 45554).
+- Does not contribute to the circular economy of the equipment: Fasteners and connectors can be categorized as neither removable nor reusable (class C).
+
+**2.2. Diagnostic support:** Facilitate the identification of problems or defects. Relates to the type of interface available and how intuitive it is for fault detection, parameter reset or default upgrade. An accessible diagnostic and reset interface facilitate further repair, reuse and upgrade. Diagnostic support classification by necessary interface.
+
+- The most contributing variable to the circularity of the equipment: Interface can be categorized as an intuitive interface (Class A) - cf. EN 45554.
+- Does not contribute to the circular economy of the equipment: Diagnostic is not possible with any type of interface (Class E) - cf. EN 45554.
+
+**2.3. Material recycling compatibility - Plastic parts:** Materials compatibility for joint recycling.
+
+- The most contributing variable to the circularity of the equipment: All of the following requirements shall be fulfilled;
+
+- a) Plastic parts >25g do not contain metal inlets or fasteners that are molded, heat or ultrasonically inserted or glued-in and cannot be separated by breaking off from the plastic part or with commonly available tools.
+- b) Plastic parts >100g do not have an adhesive, coating, paint or finish that is not compatible with recycled. NOTE: Plastic parts with >25% post-consumer recycled content and printed-circuit boards are exempt. Requirement does not apply to parts where such measures are required for safety, legal or technical requirements.
+- c) Plastic parts >25g are comprised of a single resin or combination of resins compatible for recycling and are separable by hand or with commonly available tools from other plastic parts >25g and not compatible for joint recycling. NOTE: Printed circuit boards, wires and cables, connectors, electronic, optical, acoustic, ESD and EMI components are excluded.
+- Does not contribute to the circular economy of the equipment: None of the requirements specified is fulfilled.
+
+## 2.4. Material recycling compatibility - Metal parts: Materials compatibility for joint recycling.
+
+- The most contributing variable to the circularity of the equipment: All of the following requirements shall be fulfilled.
+  - a) In metal parts with weight > 25 g, metals are kept separable for easy recycling, particularly the materials intended for different end-of-life treatment.
+  - b) Data on used alloys is available.
+  - c) Metal parts with weight > 25 g do not have such adhesive, coating, paint, or finish that is not compatible with recycling.
+- Does not contribute to the circular economy of the equipment: None of the requirements specified is fulfilled.
+
+## 2.5. Recycled/renewable plastics: Use of pre- or post-consumer recycled plastics. NOTE: Refers to plastics used in the ICT good itself.
+
+- The most contributing variable to the circularity of the equipment: Total content of recycled and biobased plastics 75-100%.
+- The less contributing variable to the circularity of the equipment: Total content of recycled and biobased plastics 0-25%.
+
+## 2.6. Recycled metals: Use of recycled metals.
+
+- The most contributing variable to the circularity of the equipment: Combined total recycled metals content in at least two predominant metals by mass is 75-100%.
+- Does not contribute to the circular economy of the equipment: Combined total recycled metals content in at least two predominant metals by mass is 0-25%.
+
+## 2.7. Material identification: Identification and marking of the materials contained in the equipment. The identification and marking of materials facilitate the subsequent recycling of the equipment. Materials identification according to ISO 11469.
+
+- The most contributing variable to the circularity of the equipment: Markings to identify base materials as per ISO 11469, ISO 1043-1 (plastics), ISO 1629 (rubbers) ISO 18064 (thermoplastic elastomers), as well as fillers and reinforcing materials (ISO 1043-2), plasticizers (ISO 1043-3) and flame retardants (ISO 1043-4)
+- Does not contribute to the circular economy of the equipment: No markings to identify materials on any part.
+
+## **2.8. Hazardous substances (Bromine and Chlorine):** Reduction of bromine and chlorine in plastic parts (The flame retardant used in plastic parts may contain these hazardous substances).
+
+- The most contributing variable to the circularity of the equipment: Each plastic part in the product exceeding 0.5 g shall not contain greater than 1000 ppm chlorine or greater than 1000 ppm bromine at the homogeneous level [b-IEEE1680]. Test methods such as IEC 62321-3-1 and 62321-3-2 are recommended. [b-IEEE1680]. NOTE: Parts which exceed 25% post-consumer recycled content may contain a maximum of 5000 ppm chlorine and a maximum of 5000 ppm bromine [b-IEEE1680]. Power cords - in jurisdictions where PVC-free power cords have not been approved by safety agencies for use in the product - are exempted. [b-IEEE1680].
+- Does not contribute to the circular economy of the equipment: The bromine and chlorine based substances content is unknown.
+
+## **2.9. Critical Raw Materials:** Declaration of Critical Raw Materials Content. NOTE: CRMs are different for each region. Examples of defined CRM include L.1100 and the list of CRM for the EU [b-EU-CRM]. Each product has to choose the appropriate CRM list.
+
+- The most contributing variable to the circularity of the equipment: Based on the CRM content assessment, the location of the CRM in the ICT good is available to improve recyclability.
+- Does not contribute to the circular economy of the equipment: The CRM content is unknown.
+
+## **2.10. Packaging recycling:** Material recycling aspects included in the primary packaging.
+
+- The most contributing variable to the circularity of the equipment: All the aspects of material efficiency are considered for the packaging, by fulfilling all of the following five requirements:
+  - a) Elimination of elemental chlorine as a bleaching agent used to bleach virgin or recovered fibers subsequently used in product packaging.
+  - b) Elimination of the use of expanded polystyrene in product packaging.
+  - c) Packaging is designed in a way that it allows reuse, recycling or recovery.
+  - d) Sum of the concentrations of intentionally added lead, cadmium, mercury and hexavalent chromium present in primary packaging shall not exceed 100 ppm by weight.
+  - e) Minimum used 30% recycled content by mass of plastic and fibre-based materials.
+- Does not contribute to the circular economy of the equipment: None of the requirements for packaging material recycling are fulfilled.
+
+## **2.11. Technical performance product mass-based materials efficiency:** Technical performance per product mass.
+
+- The most contributing variable to the circularity of the equipment: Technical performance per product mass used improved > 15% in between product at hand and previous corresponding product model.
+- Does not contribute to the circular economy of the equipment: Technical performance per product mass not improved in between product at hand and previous corresponding product model.
+
+## 3. Ability to Recycle, Repair, Reuse, upgrade - Manufacturer level
+
+**3.1. Service offered by manufacturer:** Duration of Repair, Reuse, upgrade services (according to EN 45554).
+
+- The most contributing variable to the circularity of the equipment: Repair, Reuse and upgrade service availability can be categorized as long-term (class A). NOTE: Expected durability is the time a customer (the user of the ICT good) can expect the product to last.
+- Does not contribute to the circular economy of the equipment: No Repair, Reuse and upgrade service availability is offered.
+
+**3.2. Spare parts distribution:** Availability of spare parts to different categories of persons/ organisations to facilitate equipment repairability (according to EN 45554).
+
+- The most contributing variable to the circularity of the equipment: Spare parts are publicly available or available to independent repair service providers (Class A and Class B, as defined in EN 45554).
+- Does not contribute to the circular economy of the equipment: Spare parts are not available (Class E, as defined in EN 45554).
+
+**3.3. Spare parts availability:** Duration of spare parts availability (according to EN 45554). The longer the availability of spare parts, the greater the circularity.
+
+- The most contributing variable to the circularity of the equipment: Spare parts availability can be categorized as long-term (class A, i.e., a repair, re-use or upgrade process, for which the required spare part(s) is/are available for a duration of time that reflects the expected durability of the product category, cf. EN 45554)
+- Does not contribute to the circular economy of the equipment: No information on duration of availability is provided for spare parts (class D, i.e., repair, re-use or upgrade process, for which the required spare part(s) is/are available at the time of sale, but for which the duration of availability cannot be determined, cf. EN 45554).
+
+**3.4. Disassembly information:** Classification of information availability by comprehensiveness (according to EN 45554).
+
+- The most contributing variable to the circularity of the equipment: Information is publicly available (class A, i.e., repair, re-use or upgrade process, for which the relevant information is available to all interested parties, cf. EN 45554).
+- Does not contribute to the circular economy of the equipment: Information is available to the manufacturer only (class D, i.e., repair, re-use or upgrade process, for which the relevant information is available to the product manufacturer, cf. EN 45554).
+
+**3.5. Collection and recycling programmes:** Designated collection and recycling programs.
+
+- The most contributing variable to the circularity of the equipment: A designated collection program for refurbish, remanufacturing, repair and a designated selective, recycling program for specific parts of ICT goods (e.g., specific recycling process able to recover Germanium from optical fiber, Tantalum from Tantalum capacitors or Indium from LCD/OLED displays, etc.) is available.
+- Does not contribute to the circular economy of the equipment: Neither designated collection nor designated recycling program is available.
+
+**3.6. Environmental footprint assessment knowledge publically available:** Knowledge on the equipment environmental footprint.
+
+- The most contributing variable to the circularity of the equipment: An [b-ISO 14040] / [b-ISO 14044] or [b-ITU-T L.1410] compliant life cycle assessment (LCA) has been carried out on the ICT good and the results are made available on demand.
+- Does not contribute to the circular economy of the equipment: Neither an environmental footprint assessment have been done on the ICT good, nor an environmental footprint assessment on a similar type of equipment are made available on demand.
+
+As a last step of assessment of this document, and part of the third level, below is described priority level definition and will be detailed in the following sub-chapter by each network equipment included in the scope of this document.
+
+Table 2 – Priority level – consist of a level of relevance of each circularity indicator based on relevance characteristics
+
+**Table 4-2 Priority level definition based on contribution effect to circular economy**
+
+| Level | Priority Level | Description                                                                            |
+|-------|----------------|----------------------------------------------------------------------------------------|
+| 1     | Very HIGH      | Indicator with a very high positive effect to the contribution of the circular economy |
+| 2     | HIGH           | Indicator with a high positive effect to the contribution of the circular economy      |
+| 3     | LOW            | Indicator with a low positive effect to the contribution of the circular economy       |
+| 4     | Very LOW       | Indicator with a very low positive effect to the contribution of the circular economy  |
+
+## 4.1 O-CU/O-DU
+
+**Table 4.1-1 O-CU/O-DU priority definition based on circularity economy effect**
+
+| Circularity aspects                               | Circularity indicator     | Priority |
+|---------------------------------------------------|---------------------------|----------|
+| Product Durability                                | Software and data support | 1        |
+|                                                   | Scratch resistance        | 4        |
+|                                                   | Maintenance support       | 1        |
+|                                                   | Robustness                | 3        |
+| Recycle, repair, reuse, upgrade – Equipment level | Fasteners and connectors  | 1        |
+|                                                   | Diagnostic support        | 2        |
+
+|                                                         |                                                                   |   |
+|---------------------------------------------------------|-------------------------------------------------------------------|---|
+|                                                         | Material recycling compatibility - Plastic parts                  | 2 |
+|                                                         | Material recycling compatibility - Metal parts                    | 1 |
+|                                                         | Recycled/renewable plastics                                       | 2 |
+|                                                         | Recycled metals                                                   | 1 |
+|                                                         | Material identification                                           | 1 |
+|                                                         | Hazardous substances (Bromine and Chlorine)                       | 1 |
+|                                                         | Critical Raw Materials                                            | 1 |
+|                                                         | Packaging recycling                                               | 2 |
+|                                                         | Technical performance product mass-based material efficiency      | 1 |
+| Recycle, repair, reuse, upgrade<br>– Manufacturer level | Service offered by manufacturer                                   | 1 |
+|                                                         | Spare parts distribution                                          | 2 |
+|                                                         | Spare parts availability                                          | 1 |
+|                                                         | Disassembly information                                           | 1 |
+|                                                         | Collection and recycling programmes                               | 2 |
+|                                                         | Environmental footprint assessment knowledge publically available | 1 |
+
+## 4.2 O-RU
+
+**Table 4.2-1 O-RU priority definition based on circularity economy effect**
+
+| Circularity aspects                                  | Circularity indicator                            | Priority |
+|------------------------------------------------------|--------------------------------------------------|----------|
+| Product Durability                                   | Software and data support                        | 1        |
+|                                                      | Scratch resistance                               | 4        |
+|                                                      | Maintenance support                              | 1        |
+|                                                      | Robustness                                       | 1        |
+| Recycle, repair, reuse, upgrade<br>– Equipment level | Fasteners and connectors                         | 1        |
+|                                                      | Diagnostic support                               | 2        |
+|                                                      | Material recycling compatibility - Plastic parts | 2        |
+|                                                      | Material recycling compatibility - Metal parts   | 1        |
+
+|                                                         |                                                                   |   |
+|---------------------------------------------------------|-------------------------------------------------------------------|---|
+|                                                         | Recycled/renewable plastics                                       | 2 |
+|                                                         | Recycled metals                                                   | 1 |
+|                                                         | Material identification                                           | 1 |
+|                                                         | Hazardous substances (Bromine and Chlorine)                       | 1 |
+|                                                         | Critical Raw Materials                                            | 1 |
+|                                                         | Packaging recycling                                               | 2 |
+|                                                         | Technical performance product mass-based material efficiency      | 1 |
+| Recycle, repair, reuse, upgrade<br>– Manufacturer level | Service offered by manufacturer                                   | 1 |
+|                                                         | Spare parts distribution                                          | 2 |
+|                                                         | Spare parts availability                                          | 1 |
+|                                                         | Disassembly information                                           | 1 |
+|                                                         | Collection and recycling programmes                               | 2 |
+|                                                         | Environmental footprint assessment knowledge publically available | 1 |
+
+# Annex A (informative): Reduction of environmental impact through circular economy
+
+## A.1 Equipment lifecycle aspects to consider
+
+![Diagram showing the equipment lifecycle stages: Design & Manufacturing, Use, Reuse, and End of life, with a feedback loop from End of life back to Design & Manufacturing.](83557251ef78793fdb5e0084561b5391_img.jpg)
+
+**Reduction of environmental impact through circular economy**
+
+Equipment lifecycle aspects to consider...
+
+```
+
+graph LR
+    DM[Design & Manufacturing] --> U[Use]
+    U --> R[Reuse]
+    R --> EL[End of life]
+    EL --> DM
+  
+```
+
+**Design & Manufacturing**
+
+Design with circularity criteria:
+
+- Durability
+- Material resistance
+- Repairability
+- Upgradability
+- Content of recycled material
+- Low resource and energy consumption
+- Manufacturing environmental standards (without pollution)
+- Eco-friendly packaging
+
+**Use**
+
+Extend equipment operational lifespan:
+
+- Available and affordable repair services
+- Spare parts replacement availability
+- Avoidance of planned obsolescence
+- Sharing equipment and infrastructure to increase usage
+- Upgradable software and firmware
+- Equipment maintenance
+
+**Reuse**
+
+Repurpose equipment to prevent it from becoming waste:
+
+- Refurbishment
+- Remanufacture
+- Reverse logistics
+- Facilitate the purchase and sale of second-hand equipment (transferable licences, warranties, maintenance and technical support when ownership of equipment changes)
+
+**End of life**
+
+Closing the loop:
+
+- Recycling compatible materials
+- Easy disassembly
+- Considering waste as a resource through recycling (sale of recoverable materials)
+
+Diagram showing the equipment lifecycle stages: Design & Manufacturing, Use, Reuse, and End of life, with a feedback loop from End of life back to Design & Manufacturing.
+
+**Figure A.1-1: Reduction of environmental impact through circular economy**
+
+# --- Revision history
+
+| Date       | Revision | Description                                                                                       |
+|------------|----------|---------------------------------------------------------------------------------------------------|
+| 2023.12.11 | 01.00    | First version of circular economy guidelines on network equipment based on ITU-T L.1023 (08/2023) |
+
+## --- History
+
+| Date | Revision | Description |
+|------|----------|-------------|
+|      |          |             |
+|      |          |             |
+|      |          |             |
+|      |          |             |

marked/TIFG/O-RAN.TIFG.CGofOTIC.0-v06.00/raw.md

@@ -0,0 +1,616 @@
+
+
+# **O-RAN ALLIANCE Test and Integration Focus Group****Criteria and Guidelines of Open Testing and Integration Centre**
+
+Copyright © 2025 by the O-RAN ALLIANCE e.V.
+
+The copying or incorporation into any other work of part or all of the material available in this specification in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this specification for your personal use, or copy the material of this specification for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
+
+O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
+
+---
+
+|    |                                                                  |                                     |    |
+|----|------------------------------------------------------------------|-------------------------------------|----|
+| 1  | <b>Contents</b>                                                  |                                     |    |
+| 2  | Foreword.....                                                    |                                     | 2  |
+| 3  | Modal verbs terminology .....                                    |                                     | 2  |
+| 4  | 1 Scope.....                                                     |                                     | 3  |
+| 5  | 2 References.....                                                |                                     | 3  |
+| 6  | 2.1 Normative references.....                                    |                                     | 3  |
+| 7  | 2.2 Informative references.....                                  |                                     | 4  |
+| 8  | 3 Definition of terms, symbols and abbreviations.....            |                                     | 4  |
+| 9  | 3.1 Terms.....                                                   |                                     | 4  |
+| 10 | 3.2 Symbols.....                                                 |                                     | 5  |
+| 11 | 3.3 Abbreviations.....                                           |                                     | 5  |
+| 12 | 4 Overview of OTIC .....                                         |                                     | 6  |
+| 13 | 5 General Requirements of OTIC .....                             |                                     | 7  |
+| 14 | 5.1 Participants and roles in OTIC.....                          |                                     | 7  |
+| 15 | 5.1.1 Host.....                                                  |                                     | 7  |
+| 16 | 5.1.2 Partner.....                                               |                                     | 8  |
+| 17 | 5.1.3 Client.....                                                |                                     | 8  |
+| 18 | 5.1.4 Observer.....                                              |                                     | 8  |
+| 19 | 5.2 OTIC Physical Lab Architecture and Layout .....              |                                     | 9  |
+| 20 | 5.3 Basic Guidelines for OTIC Agreements.....                    |                                     | 9  |
+| 21 | 6 Application and Qualification Processes.....                   |                                     | 10 |
+| 22 | 6.1 Application for OTIC Qualification.....                      |                                     | 10 |
+| 23 | 6.2 OTIC Application Reviewing and Evaluation .....              |                                     | 11 |
+| 24 | 6.3 OTIC Application Approval .....                              |                                     | 11 |
+| 25 | 6.4 OTIC Catalogue.....                                          |                                     | 12 |
+| 26 | 6.5 Complaints and Disqualification.....                         |                                     | 12 |
+| 27 | Annex A (normative): OTIC application form.....                  |                                     | 14 |
+| 28 | Annex B (informative): Guidelines on OTIC application form ..... |                                     | 20 |
+| 29 | Annex C (normative): Hosting agreement.....                      |                                     | 21 |
+| 30 | Revision history.....                                            |                                     | 25 |
+| 31 | History .....                                                    | <b>Error! Bookmark not defined.</b> |    |
+
+---
+
+# 32 Foreword
+
+33 This Process Document has been produced by O-RAN ALLIANCE.
+
+---
+
+# 34 Modal verbs terminology
+
+35 In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**",  
+36 "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal  
+37 forms for the expression of provisions).
+
+"must" and "must not" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
+
+# --- 1 Scope
+
+The contents of the present document are subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN Alliance modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
+
+version xx.yy.zz
+
+where:
+
+xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
+
+yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
+
+zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
+
+The present document describes the essential criteria and guidelines (guiding principles) from process, organization, space and technical perspective on the qualified Open Testing and Integration Centre (OTIC).
+
+The conformance and interoperability certification/validation/badging processes will be described in a separate set of documents (e.g. [1]), incl. the definition on who can and how to issue O-RAN certificate or badge.
+
+# --- 2 References
+
+## 2.1 Normative references
+
+References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.
+
+NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
+
+The following referenced documents are necessary for the application of the present document.
+
+- [1] O-RAN.TIFG.Cert-Badge.0-v05.00: O-RAN ALLIANCE Test and Integration Focus Group, Certification and Badging Processes and Procedures, Version 05.00, October 2022"
+- [2] O-RAN.WG1.O-RAN-Architecture-Description-v07.00: O-RAN ALLIANCE WG1, O-RAN Architecture Description, Version 7.0, October 2022
+- [3] O-RAN.TSC.WORKPROC-v03.00: "O-RAN Working Procedures"
+- [4] O-RAN ALLIANCE Constitution, version 27-06-2018 , available at [www.o-ran.org/membership-info](http://www.o-ran.org/membership-info)
+
+1
+
+# 2 2.2 Informative references
+
+3 References are either specific (identified by date of publication and/or edition number or version number)  
+4 or non-specific. For specific references, only the cited version applies. For non-specific references, the latest  
+5 version of the referenced document (including any amendments) applies.
+
+6 NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN  
+7 cannot guarantee their long-term validity.
+
+8 The following referenced documents are not necessary for the application of the present document, but  
+9 they assist the user with regard to a particular subject area.
+
+10
+
+# --- 11 3 Definition of terms, symbols and abbreviations
+
+# 12 3.1 Terms
+
+13 For the purposes of the present document, the following terms apply:
+
+14 **Affiliate:** the definition is given in [4].
+
+15 **Blueprint:** is the set of inputs which is used to describe a specific O-RAN deployment from several aspects.  
+16 These aspects include the specification of the O-RAN deployment at the system level (e.g. architecture,  
+17 performance metrics) as well as subsystem level and the interfaces between the specified subsystems. This  
+18 would then allow definition and documentation of the testing methodology and the test cases using the  
+19 blueprint specification.
+
+20 **Client:** is a participant in OTIC who provides its O-RAN equipment, components and/or services for the testing  
+21 in OTIC.
+
+22 **Host:** is a founder and main sponsor of Open Testing and Integration Centre (OTIC). Only O-RAN Member  
+23 (including the affiliates [4]) or non-vendor O-RAN Participants (including the affiliates [4]) may become a host.  
+24 Host is mandatory entity in OTIC.
+
+25 **IOT profile:** specifies a specific selection of parameters, optional features, default values and ranges of  
+26 configurable attributes and mechanisms from O-RAN subsystem interface specification(s) that shall be  
+27 supported and used in order to guarantee interoperability between implementations from different vendors.
+
+28 **Observer:** is a participant in OTIC who is allowed to observe the testing activities in OTIC for a limited period  
+29 and/or a limited purpose.
+
+30 **OTIC:** is a qualified Open Testing and Integration Centre meeting the relevant subset of criteria and guidelines  
+31 mentioned in the present document.
+
+32 **O-RAN Academic Contributor:** the definition is given in [3].
+
+33 **O-RAN Contributor:** the definition is given in [3].
+
+34 **O-RAN Entity:** the definition is given in [3].
+
+- 1 **O-RAN Member:** the definition is given in [3].
+- 2 **O-RAN Participant:** the definition is given in [3].
+- 3 **Partner:** is a participant in OTIC who can provide, maintain and/or operate test and measurement equipment  
+4 and tools, can provide space and services, can design, set-up, conduct and evaluate the testing activities on  
+5 behalf of host.
+- 6 **Testing:** any activity involving testing of O-RAN equipment, e.g. plugfest, demo, lab trial, field trial.
+
+# 7 3.2 Symbols
+
+8 For the purposes of the present document, the following symbols apply:
+
+9
+
+# 10 3.3 Abbreviations
+
+11 For the purposes of the present document, the following abbreviations apply:
+
+|    |         |                                                 |
+|----|---------|-------------------------------------------------|
+| 12 | IOT     | Interoperability                                |
+| 13 | IUT     | Interface under Test                            |
+| 14 | O-CU-CP | O-RAN Central Unit – Control Plane              |
+| 15 | O-CU-UP | O-RAN Central Unit – User Plane                 |
+| 16 | O-DU    | O-RAN Distributed Unit                          |
+| 17 | O-RU    | O-RAN Radio Unit                                |
+| 18 | OTIC    | Open Testing and Integration Centre             |
+| 19 | PoC     | Proof of Concept                                |
+| 20 | RIC     | RAN Intelligent Controller                      |
+| 21 | TIFG    | O-RAN ALLIANCE Test and Integration Focus Group |
+| 22 | TSC     | O-RAN ALLIANCE Technical Steering Committee     |
+| 23 |         |                                                 |
+
+# 4 Overview of OTIC
+
+The Open Testing and Integration Centre (OTIC) provides a collaborative, open, and impartial working environment; however, the intellectual property of participants in OTIC must be protected in this environment as well.
+
+The environment meeting all of the criteria and guidelines from this document may be qualified as OTIC and may be named as “Open Testing and Integration Centre (OTIC)”. OTIC may or may not have its own legal incorporation. OTIC is an activity outside O-RAN ALLIANCE.
+
+Multiple OTICs may exist in different regions around the world. Each OTIC may focus on different O-RAN functions [2] (such as Near-RT RIC, O-CU-CP and O-CU-UP, O-DU, O-RU), interfaces [2] (such as Open Fronthaul, E2, O1, O2, A1), blueprints, IOT profiles, etc. The testing results, experiences, best practices, knowledge, lesson-learned, adopted processes, etc. are assumed to be shared among the OTICs in order to reduce the overall costs and resources and coordinate the efforts. The learning and experiences may also be published and shared outside the O-RAN community with specified level of confidentiality. The Open Testing and Integration Centre is proposed as vendor-independent<sup>1</sup>, open and qualified physical space in order to, among others (not everything must be included in the scope of work of a particular OTIC):
+
+- a) Support of wide adoption of O-RAN specifications and promote the openness of O-RAN ecosystem via demos, community events (e.g. speaker sessions, workshops, tutorials), lab and field trials, etc.
+- b) Demonstrate implementations and solutions based on O-RAN specifications via plugfests and proofs of concept “PoCs”.
+- c) Test and verify the conformity of RAN equipment with O-RAN interface specifications, based on O-RAN conformance test specifications.
+- d) Test and verify the interoperability of RAN equipment from different vendors (or the same vendor) using O-RAN interface specifications, based on O-RAN interoperability test specifications.
+- e) Foster and develop the integrator’s technical capabilities via workshops, tutorials, etc.
+- f) Conduct functional as well as performance (load, capacity) tests of both end-to-end systems as well as sub-systems.
+- g) Give O-RAN (in particular O-RAN workgroups, O-RAN contributors) feedback about the experiences made with O-RAN specifications during the testing activities (i.e. implementation driven specification).
+
+The coordination (in terms of considered focus areas, test scenarios, operators’ specific requirements, plugfests) among worldwide OTICs is required to avoid fragmentation and repeating the same functional as well as performance tests (with the same vendors) multiple times. The services offered by OTICs should be complementary rather than competitive.
+
+The O-RAN ALLIANCE in cooperation with TIFG (O-RAN ALLIANCE Test and Integration Focus Group) is the governing body to resolve any un-clarity, inconsistency and ambiguity in the present document, as well as any conflict and complaint which cannot be resolved internally inside OTIC.
+
+---
+
+<sup>1</sup> Vendors include all commercial suppliers of equipment and tools, including test and measurement companies.
+
+# 5 General Requirements of OTIC
+
+## 5.1 Participants and roles in OTIC
+
+The following roles with relations and responsibilities are defined in Open Testing and Integration Centre (OTIC):
+
+- a) Host
+- b) Partner
+- c) Client
+- d) Observer
+
+### 5.1.1 Host
+
+- a) Host is a founder, main contact (designated multi-host representative in case of co-hosted OTIC) and main sponsor of OTIC. The financial flows inside the OTIC are controlled and managed by the host itself. Host is also an entity which coordinates and is fully responsible for all the activities in OTIC.
+- b) Host shall be an O-RAN Member [3] (i.e. mobile operator, including the affiliates [4]) or an O-RAN Participants [3] (i.e. O-RAN Contributor or O-RAN Academic Contributor, including the affiliates [4]); in order to ensure a high level of credibility, confidentiality, the O-RAN Participant shall demonstrate vendor-independence<sup>2</sup>. For example, a third-party authorized test laboratory (an open lab) may also host OTIC, but it shall become O-RAN Participant first. Note that only O-RAN Entities may present the results, proposals, etc. at O-RAN ALLIANCE meetings, and upload the results and reports to O-RAN ALLIANCE wiki and other shared folders.
+- c) OTIC may be hosted by one or more hosts (co-hosted OTIC). In this case a designated multi-host representative will be designated as main OTIC contact among the involved hosts.
+- d) Host provides the space (test rooms, server rooms) for conducting of the tests and hosting the events (incl. IOT and conformance testing, plugfest, PoC, demo), network connectivity, and test/measurement equipment, tools and services. These can be fully or partially provided by the host itself or by the contracted partner(s), but the host assumes responsibility for meeting the required criteria, conditions, and guidelines.
+- e) Host guarantees the openness and fairness to any client who has interest in testing its equipment in OTIC. It means OTIC is available and open for all clients, and any client may not be disqualified from testing in OTIC without cause. All clients shall be handled equally.
+- f) Host guarantees the credibility, confidentiality, openness and vendor-independence<sup>2</sup> of OTIC. Host also guarantees that the agreed test procedures are properly followed, and the results are produced in agreed format and with certain level of quality and confidentiality.
+- g) Host enters into agreements (e.g. participant agreement, testing agreement) with all other participants in OTIC. The agreement shall be in compliance with the criteria and requirements stated in the present document.
+- h) Host shall take all necessary steps (e.g. participant's agreement, testing agreement, isolated space) to work towards protecting the intellectual property each participant in OTIC in a mutually collaborative environment; however, OTIC participants shall recognize that it may not be possible to safeguard intellectual property in all situations, e.g. outdoor equipment.
+
+<sup>2</sup> Vendors include all commercial suppliers of equipment and tools, including test and measurement companies.
+
+- i) Host shall take necessary steps to ensure that the used test and measurement equipment and tools are properly calibrated and ready to use.
+- j) Host allows the detailed results, blueprints, interface profiles, experiences, best practices, knowledges, lesson-learned, adopted processes, etc. to be shared following the confidentiality levels from the agreements.
+- k) Host regularly presents the summary of testing results, experiences, best practices, knowledges, lesson-learned and adopted processes at TIFG meetings (and optionally on request to any other O-RAN meeting).
+- l) Host or multi-host designated representative responds to the request for information or testing results from TIFG in a timely manner.
+- m) Host acts as a mediator trying to resolve any complaint inside OTIC. The complaint resolution processes (incl. documentation of resolution of complaint) shall be set up in each OTIC. O-RAN ALLIANCE in cooperation with TIFG acts as the governing body in case the complaint might not be resolved by the host(s) inside OTIC.
+- n) In the multi-host scenario, O-RAN ALLIANCE and TIFG will only communicate officially with the multi-host designated representative.
+
+### 5.1.2 Partner
+
+- a) Partner is any company/organization with or without O-RAN ALLIANCE membership in good standing.
+- b) Partner can provide maintain, and/or operate test and measurement equipment and tools (e.g. emulators, log tools, analysers, generators) on behalf of the host on permanent basis or temporary basis per test.
+- c) Partner can provide, maintain space (rooms, servers) and services in OTIC on behalf of the host.
+- d) Partner can design, set-up, conduct and evaluate the testing activities on behalf of the host, but the host always guarantees that the test procedures are properly followed with certain level of quality and confidentiality (e.g. using a confidentiality agreement signed between host and partner).
+- e) All the aforementioned items can be also provided by the host itself, i.e. OTIC can have no contracted partner.
+
+### 5.1.3 Client
+
+- a) Client (or customer) is any company/organization with or without O-RAN ALLIANCE membership in good standing producing O-RAN equipment and components which are subsequently provided for the testing in OTIC.
+- b) Client can choose any OTIC for the testing of its RAN equipment and components.
+- c) The host or delegated partner should sign a testing agreement with the client.
+- d) Client is encouraged to leave at least one representative product in the OTIC for a reasonable time period. Leaving more than one product is encouraged, as is replacing outdated products with newer models.
+
+### 5.1.4 Observer
+
+- a) Observer (or Visitor) is any company/organization with or without O-RAN ALLIANCE membership in good standing which is allowed to observe the testing activities in OTIC for a limited period and/or a limited purpose. The period and purpose shall be clearly specified and known in advance to all participants in OTIC involved in testing activity. The role is expected to be more related to the O-RAN PlugFest.
+
+- b) The host guarantees that the confidentiality in OTIC is not violated by the observer (e.g. using a confidentiality agreement signed between host/delegated partner and observer).
+
+## 5.2 OTIC Physical Lab Architecture and Layout
+
+The OTIC physical lab is designed to create an open and collaborative environment, but at the same time satisfy IPR protection concerns of all OTIC participants. OTIC is a place where different participating companies are onsite collaborating, and where multiple different testing activities can be hosted at the same time. Therefore, the space layout, architecture and network setups shall be flexible and ensure restricted access to specific components only to specific participants engaged in specific testing activity.
+
+A logical and physical separation between OTIC and the rest of facilities (e.g. host's own internal lab(s)) shall be provided and ensured in order to minimize any security risk. The OTIC environment should be presented as an OTIC resource.
+
+Every testing activity shall be assigned a separated work area with restricted access (e.g. a badging access) only to participants engaged in that testing activity. The work area shall be equipped with working desks and secure connections to the server room(s) with server racks. The size of specified work area is related to the number of engaged participants and complexity of the testing activity.
+
+The server room(s) shall be separated from the work area. The restricted access to server room is granted only to participants engaged in the testing activity(ies). The server room might be shared for multiple testing activities but the physical and/or logical separation between servers shall be ensured (e.g. physical servers separated in locked racks, virtual servers logically separated).
+
+The access to the network and sharing of the resources and equipment should be secured (e.g. using subnets, access lists).
+
+The host of OTIC is responsible (also, where appropriate, by engaging into specific agreements with any contracted partners) for the security, configuration and maintenance of network (e.g. assignment of subnets, VPNs to each testing activity and participants) as well as for identification and provision of the proper test and measurement equipment and tools within hosted testing activities and supported services and focus areas. The additional equipment and tools, which are not available in OTIC, might be needed for the period of the testing activity.
+
+Each OTIC is encouraged to have the capability to easily and securely connect to the other OTICs in case different HW or SW components from each individual OTIC need to communicate with each other.
+
+The vendors may remotely connect their O-RAN functions to the OTIC and run the specified remote testing (e.g. remote testing of A1 interface between Non-RT RIC and Near-RT RIC, or O1 interface between Service Management and Orchestration system and O-RAN functions). This will allow vendors to scale logistic issues.
+
+The OTIC support of remote connectivity is optional.
+
+## 5.3 Basic Guidelines for OTIC Agreements
+
+O-RAN ALLIANCE foresees the following two types of agreements that OTIC will adopt
+
+- Legal agreement between host and its potential partners, clients or observers
+
+- Legally binding Hosting agreement between the underlying OTIC (OTIC host(s)) and O-RAN ALLIANCE (see Annex C)
+
+In general, the host or hosts have the full flexibility and authorization to negotiate and sign legal agreements with its partners, clients and observers. O-RAN ALLIANCE will not interfere in such processes. However, O-RAN ALLIANCE recommends the following main common items to be included in the agreement:
+
+- Confidentiality
+- Openness and fairness
+- Rights to share the testing/validation results and other outcomes
+
+It is required for the underlying OTIC and its host(s) to sign the Hosting agreement with O-RAN ALLIANCE to be qualified as Open Testing and Integration Centre (OTIC), which may cover the following processes and main considerations:
+
+- Qualification and disqualification process
+- Reporting and results sharing process
+- Complaint resolution process
+
+# --- 6 Application and Qualification Processes
+
+## 6.1 Application for OTIC Qualification
+
+This section describes OTIC qualification process. The OTIC applicant (i.e. host or designated multi-host representative in case of co-hosted OTIC) needs to send the complete application to *otic@groups.o-ran.org* in order to start OTIC qualification process. The OTIC application can be submitted at any time. The submitted application is received by the O-RAN Office and sent to TIFG for handling the review. The approval process is handled by O-RAN Office. The OTIC application form is defined in Annex A (with the guidelines on how to fill OTIC application form in Annex B), and it contains among others the following information:
+
+- General information about OTIC, incl. name of OTIC, location (address) and main contacts
+- Information about the host(s) and potential partners, if any
+- Information about the lab(s), incl. space layout and architecture
+- Information about the supported focus area and work scope – supported services and test cases
+- OTIC applicant self-declaration confirming that the requirements for qualification have been fulfilled.
+
+The name of OTIC shall be unique and English name including word “OTIC”. The proposed OTIC name may be revised and harmonized with other OTIC names during the review meeting. It would be also recommended (optional) to use the naming convention (scheme) based on geographic location of OTIC lab(s) and/or hosting company/organization name(s) whenever possible. Please visit <https://www.o-ran.org/> for already approved OTIC names.
+
+The following changes are subject to O-RAN approval. The OTIC needs to send a request for such approval to *otic@groups.o-ran.org*.
+
+- Changing of name of OTIC
+- Changing of host(s) of the OTIC
+
+## 6.2 OTIC Application Reviewing and Evaluation
+
+Once the O-RAN Office sends the application to the TIFG, TIFG co-chairs assign each application to a reviewer who is the next in line and who has no relation to the OTIC applicant or OTIC host(s). The applications should be equally distributed to the reviewers.
+
+The reviewer is selected from the list of reviewers which is maintained by TIFG. The reviewer list is accessible to all O-RAN Entities [3], and it contains information about the reviewers such as name, e-mail address, phone number, company affiliation, and assigned OTIC applications. Any representative of O-RAN Entity can be registered in or deregister from the list of reviewers at his or her own request at any time. The TIFG co-chairs can re-select the assigned reviewer if needed.
+
+The assigned reviewer checks the application to ensure it is complete and in compliance with the requirements. If needed, the reviewer may request OTIC applicant to provide additional information for any missing or unclear information in the application. The reviewer is designated as the point of contact for all communications with OTIC applicant. The reviewer helps OTIC applicant to complete the application. The reviewer guarantees completeness and compliance of the application. The reviewer does not approve or evaluate the application.
+
+Once the application is completed, the assigned reviewer needs to inform TIFG co-chairs to schedule a review meeting where OTIC applicant will present and defend the application. If needed, TIFG can also try to coordinate the application with other OTICs in order to avoid fragmentation, overlap, etc.
+
+If the review meeting does not take place within 2 months of the date when application was submitted, the application may be withdrawn from review process. The applicant can still submit new OTIC application later on.
+
+The preliminary favourable or unfavourable recommendations should be collected by TIFG co-chairs during the review meeting, and provided to OTIC applicant after the review meeting. The TIFG co-chairs also add the recommendations and summary of the review meeting to OTIC application. OTIC applicant has the rights to provide their statements and any necessary information or correction if the unfavourable recommendation is made. The OTIC applicant statements and corrections are also added to OTIC application.
+
+It needs to be noted that the OTIC application cannot be approved or rejected by TIFG.
+
+## 6.3 OTIC Application Approval
+
+The completed application with TIFG recommendations and with OTIC applicant statements, if provided, shall be sent back to the O-RAN Office for further approvals. The OTIC application is handled as a process document and not as a technical specification. OTIC applicant needs to address any question or inquiry raised during this official approval process.
+
+After passing O-RAN ALLIANCE approval process, OTIC applicant will be required to sign the **Hosting agreement** with O-RAN ALLIANCE, which is defined in Annex C. The OTIC qualification process is considered completed after the Hosting agreement is signed.
+
+It needs to be noted that O-RAN ALLIANCE can terminate the Hosting agreement without cause at any time with prior written notice.
+
+It needs to be also noted that the additional criteria and requirements on conformance and interoperability validation processes (certification, badging, etc.) can be added and described in a separate set of documents (e.g. [1]).
+
+There may be a future requirement to make a contribution or to pay a license fee to the O-RAN ALLIANCE for the use of their logos (e.g., “O-RAN”, “OTIC”) or fees for O-RAN qualification services in the event that an OTIC collects a fee.
+
+## 6.4 OTIC Catalogue
+
+The assigned reviewer will create new record (page) with the information about approved OTIC in the list of OTICs (OTIC catalogue) at O-RAN ALLIANCE wiki and at O-RAN ALLIANCE web site. The reviewer will be also assigned as the initial page administrator in the OTIC catalogue. The list of OTICs is maintained by TIFG (via assigned page administrator), and each **OTIC needs to keep all published information up to date** – any relevant change, which does not require approval (see chapter 6.1 for changes requiring approval), shall be reported to assigned page administrator as soon as possible. The page administrator ensures changes at all relevant places. TIFG co-chairs can re-select the assigned page administrator if needed.
+
+## 6.5 Complaints and Disqualification
+
+O-RAN ALLIANCE encourages each underlying OTIC to resolve internally the complaints and disagreements raised by its partners, clients or observers. O-RAN ALLIANCE has no intent and will not involve in the daily operations of OTIC and resulting normal business operation issues, which could be arbitrated or resolved by legal challenges among the involved parties.
+
+However, when O-RAN ALLIANCE receives the official request with convincing evidence that this guideline has been violated or the following situations have happened, O-RAN ALLIANCE will launch the formal investigation and may request the further information from all underlying parties
+
+- The behaviour of OTIC has seriously undermined the healthy operation of global OTICs.
+- The OTIC is not following the testing process. For example, OTIC releases detailed test results without the written consent of participant (vendor).
+- OTIC unable to fulfil its obligations and responsibilities with O-RAN ALLIANCE.
+
+The O-RAN Entity [3] can submit the complaint directly to O-RAN ALLIANCE, while the others can use the contact form at [www.o-ran.org](http://www.o-ran.org) for this purpose (as they have no access to O-RAN internal documents and procedures).
+
+The OTIC host(s) has/have the obligation to provide the information requested, as well as full rights to appeal and defend its/their position by providing evidence and supporting materials.
+
+O-RAN ALLIANCE will review the materials submitted by all parties, collect and verify all necessary information, and present the findings and preliminary recommendation to O-RAN ALLIANCE TSC/EC/Board,
+
+- 1 and follow the legal process defined in the Hosting agreement between the OTIC host and O-RAN ALLIANCE
+- 2 for the disqualification process.
+- 3 All participants in OTIC should be acquainted with the complaint rights and procedures (e.g. via OTIC charter,
+- 4 testing agreements).
+
+# --- 1 Annex A (normative): OTIC application form
+
+2 The following application form is used during OTIC qualification process as described in Chapter 6.
+
+3
+
+4
+
+## Open Testing and Integration Centre – Application form
+
+### A. GENERAL INFORMATION
+
+|                                                                  |                                                               |
+|------------------------------------------------------------------|---------------------------------------------------------------|
+| A1 Full name of OTIC                                             | A1-1 Proposed O-RAN ALLIANCE designator of OTIC (3-4 letters) |
+| A2 Link to OTIC web site                                         | A3 E-mail address                                             |
+| A4 Correspondence address: street – city – country – postal code |                                                               |
+| A5 Description and introduction of OTIC (max 100 words)          |                                                               |
+| Contact 1                                                        |                                                               |
+| A7 First name                                                    | A8 Surname                                                    |
+| A9 Telephone number (incl. country code)                         | A10 E-mail address                                            |
+| A11 Responsibilities/duties                                      |                                                               |
+| Contact 2                                                        |                                                               |
+| A12 First name                                                   | A13 Surname                                                   |
+| A14 Telephone number (incl. country code)                        | A15 E-mail address                                            |
+| A16 Responsibilities/duties                                      |                                                               |
+
+*Note A1: Name of OTIC is unique and English name including word “OTIC”. The proposed OTIC name can be revised and harmonized during the review meeting.*
+
+*Note A1-1: Proposed O-RAN ALLIANCE designator of OTIC needs to be a unique identifier within O-RAN ALLIANCE and is subject to harmonization.*
+
+*The assigned O-RAN ALLIANCE designator will be mentioned in item F4.*
+
+#### 1 The designed single point of contact for all communication between OTIC and O-RAN ALLIANCE
+
+|                                           |                    |
+|-------------------------------------------|--------------------|
+| A17 First name                            | A18 Surname        |
+| A19 Telephone number (incl. country code) | A20 E-mail address |
+
+#### 2 OTIC Applicant
+
+|                                                                                                              |                    |
+|--------------------------------------------------------------------------------------------------------------|--------------------|
+| A21 Full legal name of company                                                                               |                    |
+| A22 Correspondence address: street – city – country – postal code                                            |                    |
+| The point of contact for all communication between applicant and O-RAN ALLIANCE during qualification process |                    |
+| A23 First name                                                                                               | A24 Surname        |
+| A25 Telephone number (incl. country code)                                                                    | A26 E-mail address |
+
+3
+
+#### 4 B. HOSTS AND PARTNERS
+
+5 The OTIC has at least one host, and no or more partners.
+
+|                          |                             |
+|--------------------------|-----------------------------|
+| B1 Total number of hosts | B2 Total number of partners |
+|--------------------------|-----------------------------|
+
+6
+
+#### 7 Host 1<sup>#</sup>
+
+|                                                                                                                                                                          |                   |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| B3 Full legal name of company                                                                                                                                            |                   |
+| B4 Correspondence address: street – city – country – postal code                                                                                                         |                   |
+| Contact                                                                                                                                                                  |                   |
+| B5 First name                                                                                                                                                            | B6 Surname        |
+| B7 Telephone number (incl. country code)                                                                                                                                 | B8 E-mail address |
+| B9 O-RAN membership<br><input type="checkbox"/> Member (i.e. mobile network operator) <input type="checkbox"/> Contributor <input type="checkbox"/> Academic Contributor |                   |
+
+8 Note #: The OTIC has at least one host. The other host(s) is optional. Please copy the table if OTIC has more than one host.
+
+#### 1 Partner 1<sup>#</sup>
+
+|                                                                                                                                                                                                                           |                    |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| B10 Full legal name of company                                                                                                                                                                                            |                    |
+| B11 Correspondence address: street – city – country – postal code                                                                                                                                                         |                    |
+| Contact                                                                                                                                                                                                                   |                    |
+| B12 First name                                                                                                                                                                                                            | B13 Surname        |
+| B14 Telephone number (incl. country code)                                                                                                                                                                                 | B15 E-mail address |
+| B16 O-RAN membership<br><input type="checkbox"/> Member (i.e. mobile network operator) <input type="checkbox"/> Contributor <input type="checkbox"/> Academic Contributor<br><input type="checkbox"/> No O-RAN membership |                    |
+
+2 Note #: The OTIC has no or more partners. Please leave the table empty if OTIC has no partner, and copy the table if OTIC has more than one  
+3 partner.
+
+4
+
+#### 5 C. PHYSICAL LAYOUT AND ARCHITECTURE OF LAB(S)
+
+6 The OTIC has at least one physical lab. An additional information about the lab(s) can be asked during  
+7 O-RAN ALLIANCE review meeting.
+
+|                                                                                            |
+|--------------------------------------------------------------------------------------------|
+| C1 Total number of physical labs                                                           |
+| C2 Description of OTIC architecture (max 100 words) - the pictures/photos can be including |
+
+8
+
+#### 9 Lab 1<sup>#</sup>
+
+|                                                                  |
+|------------------------------------------------------------------|
+| C3 Name of lab                                                   |
+| C4 Correspondence address: street – city – country – postal code |
+
+C5 Please describe the applied security and IPR protection mechanisms in the lab such as isolation of the lab from host own facilities (offices), capability of quickly setting up a separate work area with restricted access based on projects, etc.
+
+Note #: If OTIC has more than one lab, please copy the table.
+
+### D. SUPPORTED WORK SCOPE AND SERVICES
+
+Please tick the relevant box(es) based on the **current OTIC testing capabilities** (e.g. based on the available test and measurement equipment in the OTIC today).
+
+D1 Brief description of testing and other services currently supported by OTIC that can be offered to clients (text max 100 words)
+
+D2 Is anechoic chamber available in the OTIC?
+
+Yes, FR1  Yes, FR2  No
+
+D3 Is RF shielded chamber/room available in the OTIC?
+
+Yes, FR1  Yes, FR2  No
+
+D4 O-RAN Certificates and Badges that can be awarded by OTIC, as defined in Clause 5.3 [1]
+
+| Type of award | Interface under test | Device under test | RAT under test |
+|---------------|----------------------|-------------------|----------------|
+|               |                      |                   |                |
+|               |                      |                   |                |
+
+### E. SELF-DECLARATION
+
+OTIC applicant declares fulfilment of the requirements for qualification as an OTIC HOST as defined in the Criteria and Guidelines of Open Testing and Integration Centre, dated ....., Version ..... OTIC applicant also hereby confirms the accuracy of data provided in this application form.
+
+Representative of OTIC applicant
+
+Date
+
+Signature
+
+1
+
+### 2 **F. PROCESSING INFORMATION**
+
+3 Please do not fill the following items. The following items will be filled by O-RAN ALLIANCE.
+
+|                                                                                       |                                                             |
+|---------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| F1 Date of application received                                                       | F2 Assigned reviewer                                        |
+| F3 O-RAN ALLIANCE unique reference ID for this application                            | F4 O-RAN ALLIANCE designator assigned to OTIC (3-4 letters) |
+| F5 Recommendations and summary from the review meeting, and OTIC applicant statements |                                                             |
+
+4
+
+5
+
+- 
+- # Annex B (informative): Guidelines on OTIC application form
+- VOID
+
+# --- 1 Annex C (normative): Hosting agreement
+
+- 2 After passing O-RAN ALLIANCE approval process, OTIC applicant will be required to sign the legally binding  
+3 Hosting agreement with O-RAN ALLIANCE.  
+4
+
+### HOSTING AGREEMENT
+
+Between
+
+<Company Name>
+
+(“OTIC Host”)
+
+<Address>
+
+<Address>
+
+And
+
+**O-RAN ALLIANCE e.V.**
+
+(“O-RAN ALLIANCE”)
+
+Buschkauler Weg 27
+
+53347 Alfter/Germany
+
+1. O-RAN ALLIANCE has accepted <Company> as OTIC HOST on <DATE>.
+2. O-RAN ALLIANCE confirms that OTIC HOST fulfills the requirements for qualification as an OTIC HOST as defined in the Criteria and Guidelines of Open Testing and Integration Centre, dated ....., Version ..... (“Criteria and Guidelines”) and as declared by OTIC Host in its self-declaration (OTIC application form).
+3. OTIC HOST as the founder, main contact and main sponsor of OTIC will take full responsibility for all OTIC activities, including the organization as well as all budget and financial flows inside the OTIC.
+4. OTIC HOST will in particular:
+  - a. Provide the space (test rooms, server rooms) for conducting of tests and hosting events (incl. IOT and conformance testing, PlugFest, PoC, demo), network connectivity, and test/measurement equipment, tools and services; these services may also be provided by partner(s) contracted by the OTIC HOST;
+  - b. Guarantee the openness and fairness to any client who has interest in testing its equipment in OTIC;
+  - c. Guarantee the credibility, confidentiality, openness and vendor-independence of OTIC;
+  - d. Guarantee that the agreed O-RAN ALLIANCE test procedures (e.g. for certification and badging) are properly followed, and the results are produced in agreed format and with certain level of quality and confidentiality;
+
+- e. Enter into agreements (e.g. participant agreement, testing agreement) with all other participants in OTIC; all agreements shall be in compliance with the criteria and requirements stated in the “Criteria and Guidelines”;
+  - f. Take all necessary steps (e.g. participation agreement, testing agreement, isolated space) to work towards protecting the intellectual property of each participant in OTIC; to safeguard intellectual property in all situations, e.g., outdoor equipment;
+  - g. Take all necessary steps to ensure that the used test and measurement equipment and tools are properly calibrated and ready to use;
+  - h. Allow the detailed results, blueprints, interface profiles, experiences, best practices, knowledges, lesson-learned, adopted processes, etc. to be shared following the confidentiality levels from the agreements;
+  - i. Regularly present the summary of testing results, experiences, best practices, knowledges, lesson-learned and adopted processes at O-RAN ALLIANCE TIFG meetings (and optionally on request to any other O-RAN ALLIANCE meeting);
+  - j. Host or multi-host designated representative responds to the request for information or testing results from O-RAN ALLIANCE in a timely manner;
+  - k. Acts as a mediator trying to resolve any complaint and disagreements inside OTIC raised by its partners, clients or observers; and
+  - l. Set-up a complaint resolution processes (incl. documentation of resolution of complaint) as described in the “Criteria and Guidelines”.
+5. OTIC HOST has flexibility and authorization to negotiate and sign bilateral legal agreements with its partners, clients and observers. At minimum these agreements should include confidentiality, openness and fairness, and rights to share the testing/validation results according to the “Criteria and Guidelines”.
+6. OTIC HOST must notify the O-RAN ALLIANCE immediately if any of the requirements for qualification as an OTIC Host as defined in the “Criteria and Guidelines” are not fulfilled any longer.
+7. O-RAN ALLIANCE must notify OTIC HOST immediately if any of the requirements for qualification as OTIC HOST as defined in the “Criteria and Guidelines”, are changed.
+8. There is no obligation to pay fees to O-RAN ALLIANCE. In case that OTIC HOST collects fees from OTIC participants O-RAN ALLIANCE reserves the right to charge fees for the use of its logos (e.g. “O-RAN”, “OTIC” ) and/or fees for O-RAN ALLIANCE qualification services.
+9. Having regard to the considerable commercial value of confidential information, OTIC HOST shall keep confidential and secret and not disclose to any third party confidential information. "Confidential Information" means all financial, commercial, technical, operational, staff, management and other information, data and know-how relating to Specifications or Contributions, which may be supplied to or may otherwise come into the possession of the OTIC HOST, whether orally or in writing or in any other form, and which is confidential or proprietary in nature or otherwise expressed by the disclosing party to be confidential.
+10. The restrictions on use and disclosure of Confidential Information as described above shall not apply to any information which:
+- a) is already in the possession of the receiving party prior to its disclosure;
+  - b) is or comes into the public domain or otherwise ceases to be of a confidential nature other than as a result of wrongful disclosure hereunder by the receiving party;
+
+- c) becomes available to the receiving party on a non-confidential basis from a source other than the Disclosing Party or any of its Associates;
+- d) is separately generated by the receiving party who are not privy to the Confidential Information; or
+- e) is required to be disclosed by any law or order of a court of competent jurisdiction, recognised stock exchange, governmental department or agency provided that the receiving party (where legally permitted to do so) promptly notifies the OTIC HOST of any such requirement.
+11. O-RAN ALLIANCE grants OTIC HOST a royalty-free, non-exclusive, non-transferable, non-sublicensable license to use the registered O-RAN logos (“O-RAN”, “OTIC”) solely for the purpose of this Hosting Agreement. In the event of termination of this Hosting Agreement, OTIC HOST must immediately cease all use of the Logo.
+12. OTIC HOST will comply with the rules on data protection as provided by the European General Data Protection Regulation (GDPR) in effect since May 25, 2018.
+13. O-RAN ALLIANCE reserves the right to suspend or withdraw OTIC HOST its status as OTIC HOST if it reasonably believes that OTIC is not in compliance with the terms of this Hosting Agreement by following the procedure described in the “Criteria and Guidelines”. The OTIC HOST shall reasonably cooperate with O-RAN ALLIANCE and provide all the requested necessary information and data during investigation of received complaints.
+14. O-RAN ALLIANCE and OTIC HOST can terminate this Hosting Agreement without cause at any time with prior written notice of ninety (90) days.
+15. Upon termination of this Hosting Agreement OTIC HOST shall on demand promptly return to or destroy all originals of Confidential Information, whether in paper or in electronic form, supplied to it and promptly destroy all copies made of the Confidential Information and all notes, memoranda and other documents or computer files or records prepared by it to the extent of the Confidential Information contained in them, provided that the Receiving Party may keep one copy of Confidential Information for archiving purposes.
+16. OTIC HOST agrees and acknowledges that the obligations contained in this Hosting Agreement are legally binding upon it and that they will be construed and interpreted in accordance with German law.
+17. The OTIC HOST agrees that any disputes which may rise out of or in connection with this Hosting Agreement or otherwise in connection with its involvement in or with the O-RAN ALLIANCE shall be finally settled under the Rules of Conciliation and Arbitration of the International Chamber of Commerce by one or more arbitrators appointed in accordance with these Rules. The OTIC HOST further agrees that the place of arbitration shall be Geneva/Switzerland and all proceedings in the arbitration shall be in English.
+18. The obligations in this Hosting Agreement in respect of confidentiality shall survive termination of this Hosting Agreement howsoever arising.
+
+Signatures:
+
+Company Name (“OTIC Host”): ..... (Name and Date)
+
+O-RAN ALLIANCE e.V.: ..... (Name and Date)
+
+## Annex: Change history/Change request (history)
+
+| Date       | Revision | Description                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 2020.07.02 | 01.00    | First published version                                                                                                                                                                                                                                                                                                                                                                                                               |
+| 2020.11.07 | 02.00    | The details of OTIC qualification process have been added in Chapter 4. The OTIC application form has been added in Annex A.                                                                                                                                                                                                                                                                                                          |
+| 2021.05.07 | 03.00    | The format of document has been changed from technical specification to process document. The OTIC application approval process has been updated in Chapter 4. The Hosting agreement has been added in Annex C. The OTIC application form in Annex A has been extended by Self-declaration.                                                                                                                                           |
+| 2022.06.01 | 04.00    | Legal review of the document. The guidelines on mapping of OTIC testing capabilities and services to OTIC application form have been added to Annex B. The OTIC application form in Annex A has been updated. The format and structure of document has been updated according to the latest O-RAN templates.                                                                                                                          |
+| 2023.03.01 | 05.00    | Harmonization of OTIC names – adding requirements on OTIC names and recommended naming convention (scheme) in chapter 6.1. The changes which require additional O-RAN approval have been listed in chapter 6.1. Limitation of 2 months on duration of OTIC review process has been added to chapter 6.2. The OTIC application form (Annex A) has been updated accordingly, and new item for O-RAN ALLIANCE designator has been added. |
+| 2025.01.15 | 06.00    | Updated and simplified OTIC application form in Annex A. Alignment of terminology with O-RAN Working procedures and O-RAN Constitution. Clarification of who can be OTIC host, including O-RAN Contributors as well as O-RAN Academic Contributors.                                                                                                                                                                                   |