Content for TS 33.128 Word version: 18.6.0

0… 4… 5… 5.7… 6… 6.2.2.2A… 6.2.3… 6.2.3.2.7… 6.2.3.3… 6.2.4… 6.3… 6.3.2.2A… 6.3.3… 6.3.3.2… 6.3.3.2.4… 6.3.3.2A… 7… 7.3… 7.3.3… 7.3.3.2.21… 7.3.3.2.42… 7.3.3.2.63… 7.3.4… 7.4… 7.4.3.8… 7.5… 7.6… 7.7… 7.7.4… 7.8… 7.8.4… 7.9… 7.10… 7.10.4… 7.11… 7.12… 7.13… 7.13.3… 7.13.3.4… 7.14… 7.15… 8… A… D… E… M…

6.2.4 LI at UDM for 5G 6.2.4.1 General description 6.2.5 LI at SMSF 6.2.5.1 Provisioning over LI_X1 6.2.5.2 Generation of xIRI over LI_X2 6.2.5.3 SMS Message 6.2.5.4 Generation of IRI over LI_HI2 6.2.6 LI support at NRF
...

6.2.4 LI at UDM for 5G p. 108

6.2.4.1 General description p. 108

In 5G packet core network, the UDM provides the unified data management for UE. The UDM shall have LI capabilities to generate the target UE's service area registration related xIRI. See clause 7.2.2 for the details.

6.2.5 LI at SMSF p. 108

6.2.5.1 Provisioning over LI_X1 p. 108

The IRI-POI present in the SMSF is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.

The IRI-POI in the SMSF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages:

SUPIIMSI.
SUPINAI.
PEIIMEI.
PEIIMEISV.
GPSIMSISDN.
GPSINAI.

If service scoping is to be performed at the IRI-POI in the SMSF, the IRI-POI in the SMSF shall support the following CSP service types (see clauses 4.4.2 and 5.2.4):

Messaging.

If the IRI-POI in the SMSF receives an ActivateTask message and the ListOfServiceTypes parameter contains a ServiceType that is not supported, the IRI-POI in the SMSF shall reject the task with an appropriate error as described in ETSI TS 103 221-1 [7] clause 6.2.1.2.

Table 6.2.5-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI in the SMSF.

Table 6.2.5-1: ActivateTask message for the IRI-POI in the SMSF

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF.	M
TargetIdentifiers	One of the target identifiers listed in the paragraph above.	M
DeliveryType	Set to "X2Only".	M
ListOfDIDs	Delivery endpoints for LI_X2 for the IRI-POI in the SMSF. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.	M
TaskDetailsExtensions/ SMSFExtensions	This field shall be included if the delivery of the full TPDU is not authorised. See Table 6.2.5-2.	C
ListOfServiceTypes	Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.	C

Table 6.2.5-2: TruncateTPUserData Parameters

Field Name	Description	M/C/O
TruncateTPUserData	If included, the truncatedSMSTPDU field of the sMSTPDUData (as described in Table 6.2.5-7) structure shall be used when applicable (see text below table). If absent, the sMSTPDU field of the sMSTPDUData structure shall be used.	C

If the TruncateTPUserData field of the LI_X1 ActivateTask message is included, the IRI-POI in the SMSF shall use the truncatedSMSTPDU field in xIRI generated at the IRI-POI in the SMSF for SMS-SUBMIT and SMS-DELIVER TPDUs, otherwise, the sMSTPDU field shall be used.

The MDF2 listed as the delivery endpoint for the LI_X2 generated by the IRI-POI in the SMSF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. If SMS Content delivery is not authorized, the MDF2 shall be provisioned with the TruncateTPUserData included, otherwise it shall be be left absent.

Table 6.2.5-3 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.

Table 6.2.5-3: ActivateTask message for MDF2

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF.	M
TargetIdentifiers	One of the target identifiers listed in clause 6.2.5.1.	M
DeliveryType	Set to "X2Only". (Ignored by the MDF2).	M
ListOfDIDs	Delivery endpoints for LI_HI2. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.	M
ListOfMediationDetails	Sequence of Mediation Details, see Table 6.2.5-4.	M
TaskDetailsExtensions/ SMSFExtensions	This field shall be included if the delivery of the full TPDU is not authorised. See Table 6.2.5-2.	C

Table 6.2.5-4: Mediation Details for MDF2

ETSI TS 103 221-1 [7] field name	Description	M/C/O
LIID	Lawful Interception ID associated with the task.	M
DeliveryType	Set to "HI2Only".	M
ListOfDIDs	Details of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations specified in the ListOfDIDs field in the ActivateTask Message.	C
ServiceScoping	Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of sub-parameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C Table C.2.	C

6.2.5.2 Generation of xIRI over LI_X2 p. 110

The IRI-POI present in the SMSF shall send xIRI over LI_X2 for the event listed in clause 6.2.5.3 of TS 33.127, the details of which are described in the following clause.

6.2.5.3 SMS Message p. 110

The IRI-POI in the SMSF shall generate an xIRI containing an SMSMessage record for the following cases:

SMS-MO case:

When a target UE originates an SMS message or when any UE originates an SMS message destined to a target non-local ID.

SMS-MT case:

When an SMS message delivery to a target UE is attempted or when an SMS message delivery originated from a target non-local ID is attempted to any UE.
When an SMS message is successfully delivered to a target UE or when an SMS message originated from a target non-local ID is successfully delivered to any UE.

The SMS-MT case can also apply to the scenario when a receipt of SMS delivery from the far end is delivered successfully to the target UE or when a receipt of SMS delivery from a target non-Local ID is successfully delivered to the originating UE.

The IRI-POI present in the SMSF shall generate the xIRI containing the SMSMessage record when it detects following events:

The SMSF receives an SMCP message CP-DATA_RP-DATA [SMS-SUBMIT, SMS-COMMAND] (via AMF in Nsmsf_SMService_UplinkSMS message) from a target UE.
The SMSF receives an SMCP message CP-DATA_RP-DATA [SMS-SUBMIT] (via AMF in Nsmsf_SMService_UplinkSMS message) from any UE with TP-DA field within the SMS-SUBMIT containing a target non-Local ID and SMSF returns the SMCP: CP-ACK to that originating UE.
The SMSF receives an SMCP message CP-DATA_RP-DATA [SMS-COMMAND] (via AMF in Nsmsf_SMService_UplinkSMS message) from any UE with TP-DA field within the SMS-COMMAND containing a target non-Local ID and SMSF returns the SMCP: CP-ACK to that originating UE.
The SMSF receives a TCAP message MAP MT-FORWARD-SHORT-MESSAGE Request [SMS-DELIVER, SMS-STATUS-REPORT] destined to a target UE.
The SMSF receives a TCAP message MAP MT-FORWARD-SHORT-MESSAGE Request [SMS-DELIVER] destined to any UE with the TP-OA field within the SMS-DELIVER containing a target non-Local ID.
The SMSF receives a TCAP message MAP MT-FORWARD-SHORT-MESSAGE Request [SMS-STATUS-REPORT] destined to any UE with the TP-RA field within the SMS-STATUS-REPORT containing a target non-Local ID.

The IRI-POI present in the SMSF shall generate the xIRI containing the SMSReport record when it detects following events:

The SMSF sends a SMCP message CP-DATA_RP-ACK [SMS-SUBMIT-REPORT] (via AMF in Namf_ Communication_N1N2MessageTransfer message) in response to a previously intercepted CP-DATA_RP-DATA.
The SMSF sends a SMCP message CP-DATA_RP-ERROR [SMS-SUBMIT-REPORT] (via AMF in Namf_ Communication_N1N2MessageTransfer message) in response to a previously intercepted CP-DATA_RP-DATA.
The SMSF sends a TCAP message MAP MT-FORWARD-SHORT-MESSAGE Response [SMS-DELIVER-REPORT] in response to a previously intercepted MAP MT-FORWARD-SHORT-MESSAGE Request.

If the IRI-POI is provisioned with the TruncateTPUserData parameter included and the IRI-POI is generating xIRI for the SMS-SUBMIT type (clause 9.2.2.2 of TS 23.040) or SMS-DELIVER type (clause 9.2.2.1 of TS 23.040) TPDUs, the IRI-POI shall use the truncatedSMSTPDU (as described in Table 6.2.5-7), otherwise, the IRI-POI shall use the sMSTPDU.

Table 6.2.5-5: Payload for SMSMessage record

Field name	Type	Cardinality	Description	M/C/O
originatingSMSParty	SMSParty	1	Identity of the originating SMS party. See NOTE 2.	M
terminatingSMSParty	SMSParty	1	Identity of the terminating SMS party. See NOTE 3.	M
direction	Direction	1	Direction of the SMS with respect to the target. See NOTE 4.	M
linkTransferStatus	SMSTransferStatus	1	Indicates whether the SMSF sent the TPDU to the next network element. See NOTE 5.	M
otherMessage	SMSOtherMessageIndication	0..1	In the event of a server-initiated transfer, indicates whether the server will send another SMS. May be omitted if the transfer is target-initiated. See NOTE 6.	C
location	Location	0..1	Location information associated with the target sending or receiving the SMS, if available and authorised. See NOTE 7. Shall be encoded using the Location.locationInfo.userLocation parameter. If available, other parameters reportable via Location shall be included.	C
peerNFAddress	SMSNFAddress	0..1	Address of the other network function (SMS-GMSC/IWMSC/SMS-Router) involved in the communication of the SMS, if available.	C
peerNFType	SMSNFType	0..1	Type of the other network function (SMS-GMSC/IWMSC/SMS-Router) involved in the communication of the SMS, if available.	C
sMSTPDUData	SMSTPDUData	0..1	See Table 6.2.5-7. Shall be provided. This parameter is conditional only for backwards compatibility.	C
messageType	SMSMessageType	0..1	See Table 6.2.5-8. Shall be provided. This parameter is conditional only for backwards compatibility.	C
rPMessageReference	SMSRPMessageReference	0..1	The SM-RL Message Reference of the message per clause 7.3 of TS 24.011. Shall be provided. This parameter is conditional only for backwards compatibility.	C

The sMSTPDU field shall always be used for the sMSTPDUData field of the SMSReport record.

Table 6.2.5-6: Payload for SMSReport record

Field name	Type	Cardinality	Description	M/C/O
location	Location	0..1	Location information associated with the target sending or receiving the SMS, if available and authorised. See NOTE 7.	C
sMSTPDUData	SMSTPDUData	1	SMS TPDU, encoded as per clause 9 of TS 23.040.	M
messageType	SMSMessageType	1	See Table 6.2.5-8.	M
rPMessageReference	SMSRPMessageReference	1	The SM-RL Message Reference of the message per clause 7.3 of TS 24.011.	M

Table 6.2.5-7: Choices for SMSTPDUData field

Field Name	Type	Description
sMSTPDU	SMSTPDU	SM-TL PDU encoded per the PDUs defined in clause 9.2.2 of TS 23.040. Shall be chosen if the TruncateTPUserData Parameter is absent.
truncatedSMSTPDU	TruncatedSMSTPDU	SM-TL PDU encoded per the PDUs defined in clause 9.2.2 of TS 23.040 but truncated to remove TP-User-Data (clause 9.2.3.24 of TS 23.040). Shall be chosen if the TruncateTPUserData Parameter is set.

Table 6.2.5-8: SMSMessageType values

messageType value	RP MTI Value	RP Message Type	TP-MTI Value	SMS TPDU Message Type
deliver	001	RP-DATA (network→UE)	00	SMS-DELIVER
deliverReportAck	010	RP-ACK (UE→network)	00	SMS-DELIVER-REPORT
deliverReportError	100	RP-ERROR (UE→network)	00	SMS-DELIVER-REPORT
statusReport	001	RP-DATA (network→UE)	10	SMS-STATUS-REPORT
command	000	RP-DATA (UE→network)	10	SMS-COMMAND
submit	000	RP-DATA (UE→network)	01	SMS-SUBMIT
submitReportAck	011	RP-ACK (network→UE)	01	SMS-SUBMIT-REPORT
submitReportError	101	RP-ERROR (network→UE)	01	SMS-SUBMIT-REPORT
reserved		Reserved	11	Reserved

The IRI-POI in the SMSF shall populate the messageType field with the values listed in Table 6.2.5-8 based on the SMS TPDU message type (see clause 9.2.2 of TS 23.040) and the RP Message Type (see clause 8.2.2 of TS 24.011) that triggered the generation of the xIRI. The SMS TPDU Message Type is indicated by the value of the TP-Message Type Indicator (TP-MTI) (see clause 9.2.3.1 of TS 23.040) as described in clause 9.2.3.1 of TS 23.040. The RP Message Type is indicated by the value of the RP MTI (See clause 8.2.2 of TS 24.011).

NOTE 5:

This field is set to transferSucceeded or transferFailed as follows:

SMS-MO case:
- To transferSucceeded: when the IRI-POI in the SMSF detects that SMSF sends the MO-FORWARD-SHORT-MESSAGE-Request [SMS-SUBMIT] message to the SMS-IWMSC.
- To transferFailed: when the IRI-POI in SMSF detects the scenarios where SMSF cannot send the MO-FORWARD-SHORT-MESSAGE-Request [SMS-SUBMIT] to the SMS-IWMSC, but still generates an xIRI containing the SMSMessage record.
SMS-MT case:
- To transferSucceeded: when the IRI-POI in the SMSF detects that SMSF sends the MT-FORWARD-SHORT-MESSAGE-Response [SMS-DELIVER-REPORT] message to the SMS-GMSC.
- To transferFailed: when the IRI-POI in SMSF detects the scenarios where SMSF cannot send the MT-FORWARD-SHORT-MESSAGE-Response [SMS-DELIVER-REPORT] to the SMS-GMSC, but an xIRI containing the SMSMessage record is still generated.

6.2.5.4 Generation of IRI over LI_HI2 p. 113

When an xIRI containing the SMSMessage record is received over LI_X2 from the IRI-POI in SMSF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the SMSMessage record received over LI_X2. The SMSMessage record may be enriched by other information available at the MDF (e.g. additional location information).

If the MDF2 is provisioned with the TruncateTPUserData parameter included, the truncatedSMSTPDU field shall be used in SMSMessage IRI message, otherwise, the sMSTPDU field shall be used.

The threeGPP33128DefinedIRI field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.

The timestamp field of the PSHeader structure shall be set to the time that the SMSF event was observed (i.e. the timestamp field of the xIRI).

Each SMSMessage record shall be delivered as an IRI REPORT (see ETSI TS 102 232-1 [9] clause 5.2.10) with a new CIN assigned (see ETSI TS 102 232-1 [9] clause 5.2.4).

Each SMSReport record shall be delivered as a separate IRI REPORT (see ETSI TS 102 232-1 [9] clause 5.2.10) with the same CIN as the IRI REPORT of the associated SMSMessage record.

6.2.6 LI support at NRF p. 114

The SIRF present within the NRF provides SBA-related information to the LIPF over the LI_SI interface. Details for this interface are not considered in the present document and are for further study.