hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
2.2M
c3dea0100f00b9b204a008ec459da259
103 701
5.12.2.0 Test group objective
The test group addresses the provision 5.12-2. Guidance entails describing what the setup parameters are that have an impact on security, issuing a recommendation on how to configure the parameters to achieve a secure setup.
c3dea0100f00b9b204a008ec459da259
103 701
5.12.2.1 Test case 5.12-2-1 (functional)
Test purpose The purpose of this test case is the functional assessment of the user guidance on securely setting up the DUT. Test units a) The TL shall set up the DUT using the "Documentation of Secure Setup" described in IXIT 2-UserInfo. b) The TL shall functionally assess whether in the "Documentation of Secure Setup...
c3dea0100f00b9b204a008ec459da259
103 701
5.12.3 Test group 5.12-3
c3dea0100f00b9b204a008ec459da259
103 701
5.12.3.0 Test group objective
The test group addresses the provision 5.12-3. Because the methods available to check whether a device is securely set up vary from product to product, the test group focuses on verifying the existence of guidance documentation and its key characteristics: accessible, on topic, concise, accurate, with clear verificatio...
c3dea0100f00b9b204a008ec459da259
103 701
5.12.3.1 Test case 5.12-3-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of the user guidance on checking whether the DUT is securely set up and maintained in a secure state. Test units a) The TL shall conceptually assess whether each step (where necessary, including the parameter to verify) for checking that the DUT is...
c3dea0100f00b9b204a008ec459da259
103 701
5.12.3.2 Test case 5.12-3-2 (functional)
Test purpose The purpose of this test case is the functional assessment of the user guidance on checking whether the DUT is securely set up and maintained in a secure state. Test units a) The TL shall set up the DUT using a secure example configuration. b) The TL shall functionally assess whether checking the example c...
c3dea0100f00b9b204a008ec459da259
103 701
5.13 TSO 5.13: Validate input data
5.13.1A Test group 5.13-1A 5.13.1A.0 Test group objective The test group addresses the provision 5.13-1A. Input data validation ensures that the receiving end can process the data without causing unexpected behaviour. This entails verifying that the provided data is of the correct type (allowed data format and data str...
c3dea0100f00b9b204a008ec459da259
103 701
5.14 TSO 6: Data protection for consumer IoT
c3dea0100f00b9b204a008ec459da259
103 701
5.14.1 Test group 6-1
c3dea0100f00b9b204a008ec459da259
103 701
5.14.1.0 Test group objective
The test group addresses the provision 6-1.
c3dea0100f00b9b204a008ec459da259
103 701
5.14.1.1 Test case 6-1-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of the user information about the processing of personal data. ETSI ETSI TS 103 701 V2.1.1 (2025-05) 94 Test units a) For each category of personal data in IXIT 21-PersData, the TL shall assess whether the method of documenting the "Description", "...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.1.2 Test case 6-1-2 (functional)
Test purpose The purpose of this test case is the functional assessment of the user information about the processing of personal data. Test units a) For each category of personal data in IXIT 21-PersData, the TL shall check whether the information provided to the consumers about what personal data is processed and for ...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.2 Test group 6-2
c3dea0100f00b9b204a008ec459da259
103 701
5.14.2.0 Test group objective
The test group addresses the provision 6-2. According to ETSI TS 103 645 [1]/ETSI EN 303 645 [2], obtaining consent "in a valid way" normally involves giving consumers a free, obvious and explicit opt-in choice of whether their personal data is used for a specified purpose. ETSI ETSI TS 103 701 V2.1.1 (2025-05) 95
c3dea0100f00b9b204a008ec459da259
103 701
5.14.2.1 Test case 6-2-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of the consumers' consent for the processing of personal data. Test units a) For each personal data in IXIT 21-PersData that is processed on the basis of consumers' consent according to "Obtaining Consent", the TL shall assess whether the opt-in ch...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.2.2 Test case 6-2-2 (functional)
Test purpose The purpose of this test case is the functional assessment of the consumers' consent for the processing of personal data. Test units a) For each personal data in IXIT 21-PersData that is processed on the basis of consumers' consent according to "Obtaining Consent", the TL shall functionally assess whether ...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.4 Test group 6-4
c3dea0100f00b9b204a008ec459da259
103 701
5.14.4.0 Test group objective
The test group addresses the provision 6-4.
c3dea0100f00b9b204a008ec459da259
103 701
5.14.4.1 Test case 6-4-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of the processing of telemetry data. Test units a) The TL shall assess whether the personal data in IXIT 21-PersData that are referenced in "Personal Data" in IXIT 24-TelData is necessary for the intended functionality as described in the "Purpose"...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.5 Test group 6-5
c3dea0100f00b9b204a008ec459da259
103 701
5.14.5.0 Test group objective
The test group addresses the provision 6-5. ETSI ETSI TS 103 701 V2.1.1 (2025-05) 98
c3dea0100f00b9b204a008ec459da259
103 701
5.14.5.1 Test case 6-5-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of the user information about the processing of telemetry data. Test units a) The TL shall assess whether the "Documentation of Telemetry Data" in IXIT 2-UserInfo is suitable for the consumer to obtain the information about processing telemetry dat...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.5.2 Test case 6-5-2 (functional)
Test purpose The purpose of this test case is the functional assessment of user the information about the processing of telemetry data. Test units a) The TL shall functionally assess whether the provided information about processing telemetry data (obtained information) is consistent with the description in "Documentat...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.6 Test group 6-6
c3dea0100f00b9b204a008ec459da259
103 701
5.14.6.0 Test group objective
The test group addresses the provision 6-6. ETSI ETSI TS 103 701 V2.1.1 (2025-05) 99
c3dea0100f00b9b204a008ec459da259
103 701
5.14.6.1 Test case 6-6-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of whether the collected personal data is valid for the defined purpose and that it is deleted when it is no longer required for the associated purpose. Test units a) For each personal data in IXIT 21-PersData, the TL shall assess whether processin...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.6.2 Test case 6-6-2 (functional)
Test purpose The purpose of this test case is the functional assessment of whether the collection of personal data is valid for the defined purpose and that it is deleted when it is no longer required for the associated purpose. Test units a) The TL shall create typical personal data on the DUT with regard to the usage...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.7 Test group 6-7
c3dea0100f00b9b204a008ec459da259
103 701
5.14.7.0 Test group objective
The test group addresses the provision 6-7.
c3dea0100f00b9b204a008ec459da259
103 701
5.14.7.1 Test case 6-7-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of whether: • data is solely used to compute an aggregate result; and • the data collected should be the minimum required to compute the aggregate; and • the aggregation should happen as early as possible; and • the retention of both collected data...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.7.2 Test case 6-7-2 (functional)
Test purpose The purpose of this test case is the functional assessment of whether: • data is solely used to compute an aggregate result; and • the data collected should be the minimum required to compute the aggregate; and • the aggregation should happen as early as possible; and • the retention of both collected data...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.8 Test group 6-8
c3dea0100f00b9b204a008ec459da259
103 701
5.14.8.0 Test group objective
The test group addresses the provision 6-8.
c3dea0100f00b9b204a008ec459da259
103 701
5.14.8.1 Test case 6-8-1 (conceptual)
Test purpose The purpose of this test case is the conceptual assessment of whether data anonymization technologies are used and that they are appropriate to protect privacy during data collection, processing and storage. Test units a) For each personal data in IXIT 21-PersData, the TL shall assess whether anonymization...
c3dea0100f00b9b204a008ec459da259
103 701
5.14.8.2 Test case 6-8-2 (functional)
Test purpose The purpose of this test case is the functional assessment of whether data anonymization technologies are used to protect privacy during data collection, processing and storage. Test units a) The TL shall create typical personal data on the DUT which is foreseen to be anonymized as described in IXIT 21-Per...
046ae8c023450d9a8fef646879ce6273
103 848
1 Scope
The present document defines security provisions for Home Gateways resulting from the analysis presented in ETSI TR 103 743 [i.1], and extending from the provisions for consumer IoT devices defined in ETSI EN 303 645 [1]. NOTE 1: The Home Gateway (HG) is not an IoT device as defined in ETSI EN 303 645 [1]. However, due...
046ae8c023450d9a8fef646879ce6273
103 848
2 References
046ae8c023450d9a8fef646879ce6273
103 848
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. Referenced documents which a...
046ae8c023450d9a8fef646879ce6273
103 848
2.2 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 i...
046ae8c023450d9a8fef646879ce6273
103 848
3 Definition of terms, symbols and abbreviations
046ae8c023450d9a8fef646879ce6273
103 848
3.1 Terms
For the purposes of the present document, the terms given in ETSI EN 303 645 [1], ETSI TR 103 743 [i.1] and the following apply: community Wi-Fi®: Wi-Fi® channel made available from the HG independently of the user and guest provisions to allow public access to the Internet Hardware-Based Root of Trust (HBRT): hardware...
046ae8c023450d9a8fef646879ce6273
103 848
3.2 Symbols
Void.
046ae8c023450d9a8fef646879ce6273
103 848
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI EN 303 645 [1] and the following apply: ACL Access Control List(s) CPE Customer Premises Equipment DoS Denial of Service EN European Standard HBRT Hardware-Based Root of Trust HG Home Gateway HMEE Hardware Mediated Execution Enclave HSM Hardware ...
046ae8c023450d9a8fef646879ce6273
103 848
4 Methodology and general requirements
046ae8c023450d9a8fef646879ce6273
103 848
4.1 Introduction
A Home Gateway (HG) is connected on one side to the Internet Service Provider (ISP) network and on the other side to the user's Local Area Network (LAN). On the ISP network side, the HG is exposed to other risks and attacks as an IoT device, which justifies the promotions, refinements, extensions and additions of the p...
046ae8c023450d9a8fef646879ce6273
103 848
4.2 Handling of provisions
The present document adopts the provisions of ETSI EN 303 645 [1] as a baseline for the HG. The methodology used for the adoption is described in the present clause, which includes different operations to modify provisions from ETSI EN 303 645 [1] and add new provisions specific to the present document. All provisions ...
046ae8c023450d9a8fef646879ce6273
103 848
4.3 Naming conventions
The provisions in the present document are named following the naming conventions described in the present clause. Each provision contains an acronym representing the HG. The acronym for the HG is set to HG. Names for provisions that are specific to the present document are constructed as follows: • The name starts wit...
046ae8c023450d9a8fef646879ce6273
103 848
4.4 Reporting implementation
Provision HG 4-1 (extended): A justification shall be recorded for each recommendation in the present document that is considered to be not applicable for or not fulfilled by the device.
046ae8c023450d9a8fef646879ce6273
103 848
5 Adapted cyber security provisions for the HG
046ae8c023450d9a8fef646879ce6273
103 848
5.1 No universal default passwords
Existing provisions from ETSI EN 303 645 [1], clause 5.1 are modified as follows. In an HG, it is broadly assumed that a user and administrator can be the same person (not all users will be the same person as the administrator) but for the purposes of the present document the terms user and administrator refer to roles...
046ae8c023450d9a8fef646879ce6273
103 848
5.2 Implement a means to manage reports of vulnerabilities
Existing provisions from ETSI EN 303 645 [1], clause 5.2 are modified as follows. Provision HG 5.2-1 (information) and Provision HG 5.2-2 (information): The above-named provisions in clause 5.2 of ETSI EN 303 645 [1] require the manufacturer to publish a policy for vulnerability disclosure and recommends handling vulne...
046ae8c023450d9a8fef646879ce6273
103 848
5.3 Keep software updated
Existing provisions from ETSI EN 303 645 [1], clause 5.3 are modified as follows. Provision HG 5.3-1 (extended) a: If not all software components are updateable, those components affected shall be noted and indicated in the user guidance. Provision HG 5.3-1 (extended) b: The HG shall implement software version control ...
046ae8c023450d9a8fef646879ce6273
103 848
5.4 Securely store sensitive security parameters
An information to the provision from ETSI EN 303 645 [1], clause 5.4 is defined in the present document. Provision HG 5.4-1 (information): NOTE 1: See note in the ETSI EN 303 645 [1]. ETSI ETSI TS 103 848 V1.2.1 (2025-02) 12 NOTE 2: Critical security parameters as defined by the ETSI EN 303 645 [1] is extended to the b...
046ae8c023450d9a8fef646879ce6273
103 848
5.5 Communicate securely
Existing provisions from ETSI EN 303 645 [1], clause 5.5 are modified as follows. NOTE 1: For the core purpose of the HG to maintain separation of LAN and WAN traffic, the provisions of clause 5.1 apply to ensure data from any connected device to the HG is protected. Provision HG 5.5-1 (information): NOTE 2: Best pract...
046ae8c023450d9a8fef646879ce6273
103 848
5.6 Minimize exposed attack surfaces
Existing provisions from ETSI EN 303 645 [1], clause 5.6 are modified as follows. As a guide to the HG developer, the default configuration settings for the HG puts it into a condition where the best protection against the attacks outlined in ETSI TR 103 309 [i.5] is achieved, taking due note of the analysis provided i...
046ae8c023450d9a8fef646879ce6273
103 848
5.7 Ensure software integrity
Existing provisions from ETSI EN 303 645 [1], clause 5.7 are modified as follows. Provision HG 5.7-1 (extended): The HG should not provide any command or API to disable the secure boot feature or to circumvent this feature and boot from other sources. Provision HG 5.7-2 (extended): If any integrity verification fails d...
046ae8c023450d9a8fef646879ce6273
103 848
5.8 Ensure that personal data is secure
No modifications to the provisions from ETSI EN 303 645 [1], clause 5.8 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
5.9 Make systems resilient to outages
Existing provisions from ETSI EN 303 645 [1], clause 5.9 are modified as follows. Having firmware and log file backups mitigates against the consequences of a data integrity failure. In the event of a failure, the original data can be recovered from an uncorrupted copy stored on a different device. Provision HG 5.9-2 (...
046ae8c023450d9a8fef646879ce6273
103 848
5.10 Examine system telemetry data
No modifications to the provisions from ETSI EN 303 645 [1], clause 5.10 are defined in the present document. The timely examination of telemetry, including log data, is often useful for security evaluation and can allow problems (e.g. faults or attacks) to be identified early and dealt with, minimizing security risk a...
046ae8c023450d9a8fef646879ce6273
103 848
5.11 Make it easy for users to delete user data
No modifications to the provisions from ETSI EN 303 645 [1], clause 5.11 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
5.12 Make installation and maintenance of devices easy
Existing provisions from ETSI EN 303 645 [1], clause 5.12 are modified as follows. Provision HG 5.12-1 (extended): The HG should use secure interfaces for remote configuration during initial device setup. EXAMPLE 1: Initial configuration by the ISP via Simple Network Management Protocol (SNMP). EXAMPLE 2: Initial confi...
046ae8c023450d9a8fef646879ce6273
103 848
5.13 Validate input data
No modifications to the provisions from ETSI EN 303 645 [1], clause 5.13 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
6 Adapted data protection provisions for HGs
No modifications to the provisions from ETSI EN 303 645 [1], clause 6 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
7 Additional cybersecurity provisions for HGs
046ae8c023450d9a8fef646879ce6273
103 848
7.1 No universal default passwords
Provision HG 7.1-1 (added): The supply chain should be designed in such a way that leakage of the HG specific credentials is prevented. ETSI ETSI TS 103 848 V1.2.1 (2025-02) 15 NOTE 1: Clause 7 of ETSI TR 103 743 [i.1] describes attacks across the supply chain. EXAMPLE: A HG requires that Wi-Fi®, user and administrator...
046ae8c023450d9a8fef646879ce6273
103 848
7.2 Implement a means to manage reports of vulnerabilities
No additions to the provisions from ETSI EN 303 645 [1], clause 5.2 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
7.3 Keep software updated
Provision HG 7.3-1 (added): The public verification key of the manufacturer or software provider shall be pre-installed on the HG. EXAMPLE 1: The pre-installed public key for the integrity verification and validation of the SW update package is used. Provision HG 7.3-2 (added): If the manufacturer deploys a software pr...
046ae8c023450d9a8fef646879ce6273
103 848
7.4 Securely store sensitive security parameters
Provision HG 7.4-1 (added): Access to the Wi-Fi® and local administrator credentials shall be restricted to the authenticated local administrator of the HG. ETSI ETSI TS 103 848 V1.2.1 (2025-02) 16 Provision HG 7.4-2 (added): Access to the ISP administrator credentials shall be restricted to the authenticated ISP admin...
046ae8c023450d9a8fef646879ce6273
103 848
7.5 Communicate securely
Provision HG 7.5-1 (added): The HG should support VPN for tunnelling data during transport. EXAMPLE 1: A secure data transfer is realized by sending data via an established VPN tunnel. Provision HG 7.5-2 (added): Each user should be authenticated by the HG and then assigned access rights according to their specific rol...
046ae8c023450d9a8fef646879ce6273
103 848
7.6 Minimize exposed attack surfaces
Provision HG 7.6-1 (added): Any physical interfaces for debugging purpose during development shall be permanently disabled (or physically removed) from devices before delivery. EXAMPLE 1: Debug and test physical interfaces include UART, JTAG, etc. Disable JTAG by blowing an on-chip eFuse. Provision HG 7.6-2 (added): An...
046ae8c023450d9a8fef646879ce6273
103 848
7.7 Ensure software integrity
Provision HG 7.7-1 (added): The HG should support file integrity check feature to detect file tampering. Provision HG 7.7-2 (added): The HG should support firmware backup to the NVM. NOTE: The firmware is executable code and does not contain personal or other user specific data as the firmware is the same on any equal ...
046ae8c023450d9a8fef646879ce6273
103 848
7.8 Ensure that personal data is secure
No additions to the provisions from ETSI EN 303 645 [1], clause 5.8 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
7.9 Make system resilient to outages
No additions to the provisions from ETSI EN 303 645 [1], clause 5.9 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
7.10 Collecting log data
Security logs record the time and relevant data associated to system security events. To fulfil its purpose, the stored security log file contains security event data sufficient to identify the condition of the HG at the time of the event. Such data can include the IP addresses and ports of the triggering event (source...
046ae8c023450d9a8fef646879ce6273
103 848
7.11 Make it easy for users to delete user data
No additions to the provisions from ETSI EN 303 645 [1], clause 5.11 are defined in the present document.
046ae8c023450d9a8fef646879ce6273
103 848
7.12 Make installation and maintenance of devices easy
Provision HG 7.12-1 (added): Telnet shall be disabled by default.
046ae8c023450d9a8fef646879ce6273
103 848
7.13 Validate input data
No additions to the provisions from ETSI EN 303 645 [1], clause 5.13 are defined in the present document. ETSI ETSI TS 103 848 V1.2.1 (2025-02) 20 Annex A (informative): Basic concepts and models The models from ETSI EN 303 645 [1] apply. The threat analysis specific to HG is addressed in ETSI TR 103 743 [i.1]. ETSI ET...
5754bd19bafa05bbe706ece8856c1177
103 698
1 Scope
The present document describes a lightweight session-based emergency chat protocol that extends the base messaging functionality as defined in ETSI TS 103 479 [1]. The messaging service is based only on methods of the SIP signalling plane and interworks with Border Control Function (BCF), Emergency Service Routing Prox...
5754bd19bafa05bbe706ece8856c1177
103 698
2 References
5754bd19bafa05bbe706ece8856c1177
103 698
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. Referenced documents which a...
5754bd19bafa05bbe706ece8856c1177
103 698
2.2 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 i...
5754bd19bafa05bbe706ece8856c1177
103 698
3 Definition of terms, symbols and abbreviations
5754bd19bafa05bbe706ece8856c1177
103 698
3.1 Terms
Void.
5754bd19bafa05bbe706ece8856c1177
103 698
3.2 Symbols
Void.
5754bd19bafa05bbe706ece8856c1177
103 698
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply: AP Application Provider APP APPlication ASP Application Service Provider BCF Border Control Function ETSI ETSI TS 103 698 V1.2.1 (2026-02) 10 BGP Border Gateway Protocol CA Certificate Authority CAP Common Alerting Protocol CERT Computer Emerg...
5754bd19bafa05bbe706ece8856c1177
103 698
4 General
5754bd19bafa05bbe706ece8856c1177
103 698
4.1 Overview
Per ETSI TS 103 479 [1], emergency communications are routed by the ESRF to the ESRP via a BCF. Depending on national PSAP models the ESRP may then forward directly to the appropriate PSAP as explained in NG112 LTD [i.1]. The same mechanism applies to instant messaging in a non-session mode. The present document define...
5754bd19bafa05bbe706ece8856c1177
103 698
4.2 Architecture
The definition of core elements and interfaces supporting a Lightweight Messaging Protocol for Emergency service accessibility (LMPE) is based on the core concept introduced in ETSI TS 103 479 [1]. LMPE utilizes IP technology and requires public and private managed, and routed IP networks. The present document introduc...
5754bd19bafa05bbe706ece8856c1177
103 698
4.3 Mandatory Interfaces
Mandatory interfaces are either referenced (ETSI TS 103 479 [1]), or introduced by the present document to define simple chat capabilities of an APP and ESInet core elements. Figure 3 shows the following mandatory interfaces: • SIP-1, SIP-2: Interface between APP, BCF, ESRP and PSAP elements that defines SIP transport ...
5754bd19bafa05bbe706ece8856c1177
103 698
4.4 Optional Interfaces
In addition, optional interfaces as defined in ETSI TS 103 479 [1], are referenced by the present document to extend mandatory capabilities. Figure 4 shows the following optional interfaces: • HTTP-2: Interface between BCF and PSAP elements that defines domain specific web service capabilities. • HTTP-3: Interface betw...
5754bd19bafa05bbe706ece8856c1177
103 698
5 Entities
5754bd19bafa05bbe706ece8856c1177
103 698
5.1 Border Control Function (BCF)
5754bd19bafa05bbe706ece8856c1177
103 698
5.1.1 Overview
A BCF is the entry point (point-of-interconnect) to the ESInet infrastructure where all traffic from external networks transits. General procedures and interfaces are specified in ETSI TS 103 479 [1].
5754bd19bafa05bbe706ece8856c1177
103 698
5.1.2 Mandatory Interfaces
To be compliant with the procedures in the present document, a BCF shall support: 1) the SIP-1 interface as specified in ETSI TS 103 479 [1], clause 6.1.1; 2) the SIP-2 interface as specified in ETSI TS 103 479 [1], clause 6.1.2. Figure 5 shows BCF mandatory interfaces and neighbouring entities. ETSI ETSI TS 103 698 V1...
5754bd19bafa05bbe706ece8856c1177
103 698
5.1.3 Optional Interfaces
In addition to all mandatory interfaces, a BCF may support any other specific interface as listed in ETSI TS 103 479 [1]: • the HTTP-2 interface as specified in ETSI TS 103 479 [1], clause 6.2.2. Figure 6 shows BCF optional interfaces and neighbouring entities. Figure 6: BCF optional interfaces
5754bd19bafa05bbe706ece8856c1177
103 698
5.2 Emergency Service Routing Proxy (ESRP)
5754bd19bafa05bbe706ece8856c1177
103 698
5.2.1 Overview
The Emergency Service Routing Proxy (ESRP) is the base routing function for emergency chat. General procedures and interfaces are specified in ETSI TS 103 479 [1]. Invocation of identity verification, if an Identity header field value conforming to IETF RFC 8224 [19] is received in incoming signalling, is specified in ...
5754bd19bafa05bbe706ece8856c1177
103 698
5.2.2 Mandatory Interfaces
To be compliant with the procedures in the present document, an ESRP shall support: 1) the SIP-1 interface as specified in ETSI TS 103 479 [1], clause 6.1.1; 2) the SIP-2 interface as specified in ETSI TS 103 479 [1], clause 6.1.2; 3) the LOST-1 interface as specified in ETSI TS 103 479 [1], clause 6.4.1; 4) the LOST-2...
5754bd19bafa05bbe706ece8856c1177
103 698
5.2.3 Optional Interfaces
In addition to all mandatory interfaces, an ESRP may support any other specific interface as listed in ETSI TS 103 479 [1].
5754bd19bafa05bbe706ece8856c1177
103 698
5.3 Emergency Call Routing Function (ECRF)