name: N9HR
full_form: N9 Home Routed
context: The N9HR LI process applicable to all inbound roamers with home-routed roaming is illustrated in figure 4.8.4-1. Figure 4.8.4-1: N9HR LI process â initial configuration (applicable to all inbound roamers) The following describe the steps shown in figure 4.8.4-1: LIPF initiates the N9HR LI process by provisioning the LMISF-IRI (over the LI_X1 reference point) with "HR" + "IMSSignaling"as the target identities. However, there is no DID specified in the Activate Task as the LMISF-IRI is not supposed to forward any of the received notifications. LIPF provisions the BBIFF-C present in the SMF (over the LI_X1 reference point) with the "HR" as the target identity for xIRI and with "HR" + "IMSSignaling" as the target identities for xCC that corresponds to the IMS signalling. LMISF-IRI is the DID for both. The BBIFF-C present in the SMF detects that PDU sessions are being established for the inbound roaming UEs with home-routed roaming (i.e. for N9HR DNN). The BBIFF-C notifies the LMISF-IRI
description: The N9 Home Routed (N9HR) Lawful Interception (LI) process is a procedure applicable to all inbound roamers with home-routed roaming, as described in 3GPP TS 33.929 section 4.8.4.1.1. It involves the initiation of the LI process by the LIPF, provisioning of LMISF-IRI and BBIFF-C, and notification of PDU sessions establishment for inbound roaming UEs.
explanation: The context describes a specific sequence of steps (initiation, provisioning, detection, and notification) related to the N9HR LI process, which is a procedure for handling lawful interception in home-routed roaming scenarios. This matches the definition of a Procedure entity type.
section_title: 4.8.4.1.1	Initial configuration - applicable to all inbound roamers
biotag_Context: O,B-Procedure,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,B-Parameter,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,B-Network Function,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Network Function
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,O,B-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,O,O,O,O