Title:Considerations for using portals to support requests from <br>Authorized Organisations
Spec Number:TR 104 196
Version:v0.6.0
Date:2025-11
keywords:Markdown, Gitlab
Copyright Year:2025
Long ISG Name:Technical Committee Lawful Interception
Short ISG Name:TC LI
---
<!--- Table of contents will be inserted by Pandoc when generating the DOCX specification
<!--- Table of contents will be inserted by Pandoc when generating the DOCX specification
# Contents
# Contents
-->
-->
<!--- Extra breaklines can be inserted at any place by adding this tag
<!--- Extra breaklines can be inserted at any place by adding this tag
<br/>
\
-->
-->
# Intellectual Property Rights
# Intellectual Property Rights
Essential patents
Essential patents
@@ -108,9 +111,8 @@ Adoption of the present document does not imply that a system is compliant with
The approach in Figure 4.4-1 is recommended. The key point is to run one system with two front ends (one for meeting an ETSI Technical Specification, and one for a portal). The goal is to make the front end systems as thin as possible i.e. to put most of the functionality in the main Request Processing System.
The approach in Figure 4.4-1 is recommended. The key point is to run one system with two front ends (one for meeting an ETSI Technical Specification, and one for a portal). The goal is to make the front end systems as thin as possible i.e. to put most of the functionality in the main Request Processing System.


**Figure 4.4-1: Approach to portal design**
The design in Figure 4.4-1 is not a strict architecture or design and is not intended to constrain data flows or security boundaries.
The design in Figure 4.4-1 is not a strict architecture or design and is not intended to constrain data flows or security boundaries.
@@ -251,7 +253,7 @@ No additional comments on this topic are made in the present document.