name: WAF
full_form: WebRTC Authorisation Function
context: registraton on behalf of the WebRTC client The details of the signalling flows are as follows: NOTE 4: If the WAF resides in the operator domain, we can use the WAF control to authorize the WWSF. If WAF is not in the operator domain, then we can use the authorization of the WWSF by S-CSCF and HSS. 0) Token request (WWSF to WAF) If the WAF resides in the operator domain, when the WAF receives a token request, it can either authenticate the user itself as part of the token issuance process, or it trusts the user identity supplied by the WWSF which is assumed to have authenticated the user prior to sending the token request. Only if this check is successful will the WAF return the authorization token; otherwise, the WAF rejects the request of the WWSF. And if a WWSF is suspected of a security breach the WAF will block all token requests originating from that WWSF. 1) REGISTER request (WebRTC IMS Client to Trusted Node) The WebRTC IMS Client establishes a secure WebSocket connection with
description: The WebRTC Authorisation Function (WAF) is responsible for authorizing and authenticating WebRTC clients and WebRTC Web Server Functions (WWSF) within the operator domain. It handles token requests, user authentication, and authorization of WWSFs, ensuring secure communication between WebRTC IMS Clients and Trusted Nodes.
explanation: The context explicitly describes the role of WAF in authorizing and authenticating WebRTC clients and WWSFs, which aligns with the definition of a Network Function. The WAF's involvement in token requests, user authentication, and authorization processes further solidifies its classification as a Network Function.
section_title: 6.1.2.2	Use of Trusted Node Authentication (TNA)
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Device,I-Device,I-Device,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O