Difference between revisions of "My 33.128 Notes"
m (added 5.2) |
|||
| Line 32: | Line 32: | ||
| LI_HIQR || Used to send warrant and other identifier association query information from LEA to CSP and used by the CSP to send query responses to the LEA. || ETSI TS 103 120 shall be supported. || See clause 5.7 | | LI_HIQR || Used to send warrant and other identifier association query information from LEA to CSP and used by the CSP to send query responses to the LEA. || ETSI TS 103 120 shall be supported. || See clause 5.7 | ||
|} | |} | ||
== 5.2 Protocols for LI_X1 and LI_T interfaces == | |||
=== 5.2.7 Usage for realising LI_XEM1 === | |||
The IEF shall be enabled by sending the following ActivateTask message from the LIPF. | |||
The <code>IdentityAssociationTargetIdentifier</code> Identifier Type is defined for the use of LI_XEM1. Unless otherwise specified, use of any other Target Identifier Type (including adding a target identifier more than once) shall result in the ActivateTask message being rejected with the appropriate error. | |||
The IEF may be reconfigured to send identity associations to a different ICF using a ModifyTask message to modify the delivery destinations. | |||
The IEF shall be disabled by sending the following DeactivateTask message from the LIPF. | |||
The LIPF should send one ActivateTask command to each IEF. | |||
:NOTE: The IEF may receive multiple ActivateTask messages conforming to LI_XEM1 ActivateTask, each of which can be independently deactivated. The IEF shall remain active as long as at least one valid Task remains active. | |||
<center>[[Telecommunications info|To Telecommunications info]]</center> | <center>[[Telecommunications info|To Telecommunications info]]</center> | ||
Revision as of 09:35, 3 October 2022
4.2 Basic principles for internal interfaces
This grid lists internal interfaces associated to identity mapping and indicates the protocol used to realize each interface, and gives a reference to the relevant clauses of the 3GPP TS 33.128 V18.0.0 (2022-06) document that specify how the protocol is to be used for the given interface.
| Interface | Description | Protocol used to realize interface | Usage |
|---|---|---|---|
| LI_ADMF | Used to pass intercept provisioning information form the LICF to the LIPF. | Out of scope of the V18.0.0 document. | |
| LI_IQF | Used to pass information related to IEFs and ICF to IQF. | Out of scope of the V18.0.0 document. | |
| LI_XEM1 | Used by the LICF/LIPF to manage IEFs and ICF. | ETSI TS 103 221-1 | See clause 5.2.7 |
| LI_XER | Used to pass identifier association event records from IEFs to ICF. | See Clause 5.9 | See Clause 5.9 |
| LI_XQR | Used to pass queries from IQF to ICF and responses from ICF to IQF. | ETSI TS 103 221-1 | See Clause 5.8 |
4.3 Basic principles for external handover interfaces
This grid lists the external handover interfaces (HI) associated to identity mapping shown in clause 4.1, indicates the protocol used to realize each interface, and gives a reference to the relevant clauses of the present document that specify how the protocol is to be used for the given interface.
| Interface | Description | Protocol used to realize interface | Usage |
|---|---|---|---|
| LI_HI1 | Used to send warrant and other interception request information from LEA to operator. | ETSI TS 103 120 shall be supported. Other methods (e.g. manual exchange) may be used depending on national regulatory requirements. | See clause 5.4 |
| LI_HIQR | Used to send warrant and other identifier association query information from LEA to CSP and used by the CSP to send query responses to the LEA. | ETSI TS 103 120 shall be supported. | See clause 5.7 |
5.2 Protocols for LI_X1 and LI_T interfaces
5.2.7 Usage for realising LI_XEM1
The IEF shall be enabled by sending the following ActivateTask message from the LIPF.
The IdentityAssociationTargetIdentifier Identifier Type is defined for the use of LI_XEM1. Unless otherwise specified, use of any other Target Identifier Type (including adding a target identifier more than once) shall result in the ActivateTask message being rejected with the appropriate error.
The IEF may be reconfigured to send identity associations to a different ICF using a ModifyTask message to modify the delivery destinations.
The IEF shall be disabled by sending the following DeactivateTask message from the LIPF.
The LIPF should send one ActivateTask command to each IEF.
- NOTE: The IEF may receive multiple ActivateTask messages conforming to LI_XEM1 ActivateTask, each of which can be independently deactivated. The IEF shall remain active as long as at least one valid Task remains active.