Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.7.0

Top   Top   Up   Prev   Next
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…

 

7.7  LI at NEFp. 257

7.7.1  Provisioning over LI_X1p. 257

7.7.1.1  Generalp. 257

For NIDD using NEF:
  • If delivery type for the warrant is "IRI and CC", then the IRI-POI and the CC-POI in the NEF, the MDF2 and MDF3 shall be provisioned.
  • If delivery type for the warrant is "IRI", then the IRI-POI in the NEF and the MDF2 shall be provisioned.
  • Delivery type "CC" is not applicable to the warrant.
For device triggering, MSISDN-less MO SMS and Parameter Provisioning:
  • the delivery type for the warrant is "IRI"; the IRI-POI in the NEF and the MDF2 shall be provisioned.
Up

7.7.1.2  Provisioning of the IRI-POI and CC-POI in NEFp. 257

The IRI-POI and CC-POI present in the NEF are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the NEF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • SUPIIMSI.
  • SUPINAI.
  • GPSIMSISDN.
  • GPSINAI.
Up

7.7.2  LI for NIDD using NEFp. 258

7.7.2.1  Generation of xIRI at IRI-POI in NEF over LI_X2p. 258

7.7.2.1.1  Generalp. 258
The IRI-POI present in the NEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.9.2.3 of TS 33.127, the details of which are described in the following clauses. Each event will be based on PDU session between NEF and target UE, except for Unsuccessful Procedure event. The IRI-POI in the NEF shall also send a SeparatedLocationReporting xIRI (as described in clause 7.3.4.1) when the IRI-POI provisioned in the NEF receives updated UE location information via the Nnef_Location_LocationUpdateNotify service operation destined for an external AF.
Up
7.7.2.1.2  PDU session establishmentp. 258
The IRI-POI in the NEF shall generate an xIRI containing an NEFPDUSessionEstablishment record when the IRI-POI present in the NEF detects that an unstructured PDU session using NEF has been established for the target UE. The IRI-POI present in the NEF shall generate the xIRI for the following event:
  • NEF returns Nnef_SMContext_Create Response towards the SMF confirming the establishment of the unstructured PDU session to the NEF for the target UE (as defined in clause 5.2.2.2 of TS 29.541) and connection to the AF is established.
Field name Value M/C/O
sUPISUPI associated with the PDU session (e.g. as provided by the SMF in the associated Nnef_SMContext_Create Request).M
gPSIGPSI associated with the PDU session.M
pDUSessionIDPDU Session ID.M
sNSSAISlice identifier associated with the PDU session.C
nEFIDNEF identity handling the PDU session.M
dNNData Network Name associated with the target traffic. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
rDSSupportTrue if Reliable Data Service is supported in the PDU session, otherwise False.M
sMFIDIdentifier of the SMF associated with the target UE for that that PDU Session.M
aFIDIdentifier of the AF.M
Up
7.7.2.1.3  PDU session modificationp. 258
The IRI-POI in the NEF shall generate an xIRI containing an NEFPDUSessionModification record when the IRI-POI present in the NEF detects that an unstructured PDU session using NEF has been modified for the target UE. The IRI-POI present in the NEF shall generate the xIRI for the following events:
  • NEF returns Nnef_SMContext_Update Response to SMF to confirm the modification of the connection between SMF and NEF (see clause 5.2.2.5 of TS 29.541).
  • NEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Reserve port" to confirm the reservation of a combination of source and destination port numbers for use for a traffic to be sent by the UE to a specific application on an AF (see clause 5.4.2.6.2 of TS 24.250).
  • NEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by the NEF with an "Action" field set to "Reserve port" to confirm the reservation of a combination of source and destination port numbers for use for a traffic to be sent by an AF to a specific application on the UE (see clause 5.4.2.6.2 of TS 24.250).
  • NEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Release port" to confirm the release of a combination of source and destination port numbers for an application on an AF (see clause 5.4.2.6.3 of TS 24.250).
  • NEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by the NEF with an "Action" field set to "Release port" to confirm the release of a combination of source and destination port numbers for an application on the UE (see clause 5.4.2.6.3 of TS 24.250).
Field name Value M/C/O
sUPISUPI associated with the PDU sessionM
gPSIGPSI associated with the PDU sessionM
sNSSAISlice identifier associated with the PDU sessionM
InitiatorInitiator of the modification of the PDU session, UE, SMF or NEFM
rDSSourcePortNumberRDS source port numberC
rDSDestinationPortNumberRDS destination port numberC
applicationIDApplication identifier on the UE or on the AF if RDS is usedC
aFIDIdentifier of the AF if RDS is usedC
rDSAction Action if RDS is used. Possible values: "ReservePort", "ReleasePort" C
serializationFormatData format exchanged between UE and AF if RDS is usedC
pDUSessionIDPDU Session ID (see NOTE below)M
NOTE:
For the backward compatibility purposes the parameter is coded as OPTIONAL in the ASN.1 schema (Annex A).
Up
7.7.2.1.4  PDU session releasep. 259
The IRI-POI in the NEF shall generate an xIRI containing an NEFPDUSessionRelease record when the IRI-POI present in the NEF detects that an unstructured PDU session using NEF related to the target UE needs to be released. The IRI-POI present in the NEF shall generate the xIRI for the following events:
  • NEF notifies the SMF that the SMF-NEF Connection for NIDD via NEF is no longer valid using Nnef_SMContext_DeleteNotify service operation when NEF receives a notification from the UDM that the NIDD authorization has ended. NEF releases the SM Context for NIDD on NEF as described in clause 5.2.2.4 of TS 29.541. This corresponds to NEF Initiated SMF-NEF Connection Release procedure.
  • NEF returns Nnef_SMContext_Delete Response towards SMF confirming release of the SMF-NEF session for the target UE. In this scenario, SMF releases the SM Context for NIDD on NEF as specified in clause 5.2.2.3 of TS 29.541).
Field name Value M/C/O
sUPISUPI associated with the PDU sessionM
gPSIGPSI associated with the PDU sessionM
pDUSessionIDPDU Session ID as assigned by the AMFM
timeOfFirstPacketTime of first packet for the PDU sessionC
timeOfLastPacketTime of last packet for the PDU sessionC
uplinkVolumeNumber of uplink octets for the PDU sessionC
downlinkVolumeNumber of downlink octets for the PDU sessionC
releaseCauseCause of PDU Session ReleaseM
Up
7.7.2.1.5  Unsuccessful procedurep. 259
The IRI-POI in the NEF shall generate an xIRI containing an NEFUnsuccessfulProcedure record when the IRI-POI present in the NEF detects an unsuccessful procedure or error condition for a UE matching one of the target identifiers provided via LI_X1.
Accordingly, the IRI-POI in the NEF generates the xIRI when one of the following events are detected as described in clause 6.1.7.3 of TS 29.541 and clause 5.4.2.6 of TS 24.250:
  • NEF sends a Nnef_SMContext_Create Reject message to the SMF with a reject cause set to "USER_UNKNOWN" or "NIDD_CONFIGURATION_NOT_AVAILABLE".
  • NEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Port not free" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Reserve port".
  • NEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Port not free" in response to a RDS MANAGE PORT command sent by NEF with an "Action" field set to "Reserve port".
  • NEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Port not associated with specified application" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Release port".
  • NEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Port not associated with specified application" in response to a RDS MANAGE PORT command sent by NEF with an "Action" field set to "Release port".
Field name Value M/C/O
failureCauseProvides the value of the failure cause.M
sUPISUPI associated with the procedure.M
gPSIGPSI used in the procedure, if available.C
pDUSessionIDPDU Session ID.C
dNNData Network Name associated with the target traffic, if available. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.C
sNSSAISlice requested for the procedure, if available.C
rDSDestionationPortNumberRDS destination port number.C
applicationIDApplication associated with the RDS destination port number.C
aFID Application Function identifier. If the Application Function idenitifer is not available, the placeholder value "Unknown" shall be used. C
Up
7.7.2.1.6  Start of interception with established PDU sessionp. 260
The IRI-POI in the NEF shall generate an xIRI containing an NEFStartOfInterceptionWithEstablishedPDUSession record when the IRI-POI present in the NEF detects that an unstructured PDU session using NEF has already been established, at the time the POI on NEF is provisioned with a new target ID.
The IRI-POI in the NEF shall generate the xIRI containing the NEFStartOfInterceptionWithEstablishedPDUSession record for each of the PDU sessions for NIDD using NEF associated with the target UE with a different value of correlation information.
Field name Value M/C/O
sUPISUPI associated with the PDU session (e.g. as provided by the SMF in the associated Nnef_SMContext_Create Request).M
gPSIGPSI associated with the PDU session.M
pDUSessionIDPDU Session ID.M
sNSSAISlice identifier associated with the PDU session.M
dNNData Network Name associated with the target traffic. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
nEFIDNEF identity handling the PDU session.M
rDSSupportTrue if Reliable Data Service is supported in the PDU session, otherwise False.M
sMFIDIdentifier of the SMF associated with the target UE for that that PDU Session.M
aFIDString Identifying the AF the traffic will be delivered to.M
The IRI-POI present in the SMF generating an xIRI containing a NEFStartOfInterceptionWithEstablishedPDUSession record shall set the Payload Direction field in the PDU header to not applicable (see ETSI TS 103 221-2 [8] clause 5.2.6).
Up

7.7.2.2  Generation of xCC at CC-POI in NEF over LI_X3p. 260

The CC-POI present in the NEF shall send xCC over LI_X3 for each NIDD packet.
Each X3 PDU shall contain the contents of the user plane packet (i.e. NIDD) using an unstructured payload format.
The CC-POI present in the NEF shall set the payload format to indicate the appropriate payload type (i.e. unstructured payload) as described in ETSI TS 103 221-2 [8] clause 5.4.

7.7.2.3  Generation of IRI over LI_HI2p. 261

When an xIRI is received over LI_X2 from the IRI-POI in the NEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the NEF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.7.2-6.
IRI message Record type
NEFPDUSessionEstablishmentBEGIN
NEFPDUSessionReleaseEND
NEFPDUSessionModificationCONTINUE
NEFStartOfInterceptionWithEstablishedPDUSessionBEGIN
NEFUnsuccessfulProcedureREPORT or CONTINUE
IRI messages associated with the same PDU Session shall be assigned the same CIN (see ETSI TS 102 232-1 [9] clause 5.2.4).
The threeGPP33128DefinedIRI field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.
Up

7.7.2.4  Generation of CC over LI_HI3p. 261

When xCC is received over LI_X3 from the CC-POI in the NEF, the MDF3 shall populate the threeGPP33128DefinedCC field with a CCPayload structure containing NIDDCCPDU and send it over LI_HI3 interface to LEMF without undue delay.
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time that the NEF observed the data (i.e. the timestamp field of the xCC). The LIID and CID fields shall correctly reflect the target identity and communication session to which the CC belongs.
Up

7.7.3  LI for device triggeringp. 261

7.7.3.1  Generation of xIRI LI_X2 at IRI-POI in NEF over LI_X2p. 261

7.7.3.1.1  Generalp. 261
The IRI-POI present in the NEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.9.3.4 of TS 33.127, the details of which are described in the following clauses.
7.7.3.1.2  Device triggerp. 261
The IRI-POI in the NEF shall generate an xIRI containing a NEFDeviceTrigger record when the IRI-POI present in the NEF detects that an AF has sent a Device trigger to a target UE matching one of the target identifiers.
Accordingly, the IRI-POI in the NEF generates the xIRI when any of the following events is detected:
  • NEF sends a Nnef_Trigger_Delivery Response to the AF to acknowledge the reception of Nnef_Trigger_Delivery Request with GPSI matching the target identifier (see clause 4.13.2.1 of TS 23.502 and clause 4.4.3 of TS 29.522).
  • NEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to TRIGGER and User-Identifier AVP matching the SUPI of the target UE as described in clause 5.2.1 of TS 29.337.
Field name Value M/C/O
sUPISUPI associated with the UE.M
gPSIGPSI used with the UE.M
triggerIdIdentity of the Device trigger that should be provided in the deviceTriggeringDeliveryReportNotification IRI, Device trigger replacement IRI and Device trigger cancellation IRI.M
aFIDThe AF sending the Device trigger.M
triggerPayloadThe Device triggering payload.C
validityPeriodThe validity time in seconds for the specific action requested.C
priorityDTThe priority indication for a trigger payload.C
sourcePortIdApplication identity on the AF which delivers the Device trigger.C
destinationPortIdUsed to uniquely identify the triggering application addressed in the device.C
Up
7.7.3.1.3  Device trigger replacep. 262
The IRI-POI in the NEF shall generate an xIRI containing a NEFDeviceTriggerReplace record when the IRI-POI present in the NEF detects that an AF has sent a Device trigger replacement for a previously sent Device trigger to a UE matching one of the target identifiers provided via LI_X1 to the IRI POI in the NEF. It replaces a previously submitted Device trigger message which has not yet been delivered to the UE.
Accordingly, the IRI-POI in the NEF generates the xIRI when any of the following events is detected:
  • NEF receives a Nnef_Trigger_Delivery Request (for a device trigger replacement) from an AF as described in clause 4.4.3 of TS 29.522 with GPSI matching the target identifier.
  • NEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to REPLACE and User-Identifier AVP matching the SUPI of the target UE as specified in 29.337 [60] clause 5.2.1.
Field name Value M/C/O
sUPISUPI associated with the target UE.M
gPSIGPSI used with the taget UE.M
triggerIdIdentity of the corresponding Device trigger to be replaced.M
aFIDThe AF replacing an existing Device trigger which has not been delivered yet to the device (e.g. because the device is unreachable) by a new Device trigger.M
triggerPayloadThe device triggering payload.C
validityPeriodThe validity time in seconds for the specific action requested.C
priorityDTPriority indication for a trigger payload.C
sourcePortIdPort on the AF which delivers the device trigger.C
destinationPortIdPort on the device which is the recipient of the device trigger.C
Up
7.7.3.1.4  Device trigger cancellationp. 262
The IRI-POI in the NEF shall generate an xIRI containing a NEFDeviceTriggerCancellation record when the IRI-POI present in the NEF detects that an AF has sent a Device trigger cancellation for a previously sent Device trigger to a UE matching one of the target identifiers provided via LI_X1 to the IRI-POI in the NEF. It cancels previously submitted Device trigger message which has not yet been delivered to the target UE.
Accordingly, the IRI-POI in the NEF generates the xIRI when any of the following events is detected:
  • NEF receives a Nnef_Trigger_Delivery Request (for a device trigger cancellation) with GPSI matching the target identifier as described in clause 4.4.3 of TS 29.522.
  • NEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to RECALL and User-Identifier AVP matching the SUPI of the target UE as specified in clause 5.2.1 of TS 29.337.
Field name Value M/C/O
sUPISUPI associated with the target UE.M
gPSIGPSI used with the target UE.M
triggerIdIdentity of the corresponding device trigger to be cancelled.M
Up
7.7.3.1.5  Device trigger report notificationp. 263
The IRI-POI in the NEF shall generate an xIRI containing a NEFDeviceTriggerReportNotify record when the IRI-POI present in the NEF detects that the NEF has returned a Device trigger report to the AF with a cause value indicating the trigger delivery outcome (e.g. succeeded, unknown or failed).
Accordingly, the IRI-POI in the NEF generates the xIRI when any of the following events is detected:
  • NEF sends a Nnef_Trigger_DeliveryNotify service operation with the GPSI of the target UE to inform the AF on the delivery outcome of the device trigger as described in clause 4.4.3 of TS 29.522.
  • SM-SC sends a T4 Delivery-Report-Request (DRR) to the NEF with User-Identifier matching the SUPI of the target UE as specified in 29.337 [60] clause 5.2.2.
Field name Value M/C/O
sUPISUPI associated with the target UE.M
gPSIGPSI used with the target UE.M
triggerIdIdentity of the corresponding Device trigger.M
deviceTriggerDeliveryResultDelivery result represents the result of the delivery of a device triggering request:
  • SUCCESS: The value indicates that the device action request was successfully completed.
  • UNKNOWN: The value indicates any unspecified errors.
  • FAILURE: The value indicates that this trigger encountered a delivery error and is deemed permanently undeliverable.
  • TRIGGERED: The value indicates that Device triggering request is accepted by the NEF.
  • EXPIRED: The value indicates that the validity period expired before the trigger could be delivered.
  • UNCONFIRMED: The value indicates that the delivery of the device action request is not confirmed.
  • REPLACED: The value indicates that the device triggering replacement request is accepted by the NEF.
  • TERMINATE: The NEF includes this value in the response for a successful device triggering cancellation request. The value indicates that the delivery of the device action request is terminated by the AF.
M
Up

7.7.3.2  Generation of IRI over LI_HI2p. 263

When an xIRI is received over LI_X2 from the IRI-POI in the NEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the NEF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.7.3-5.
IRI message Record type
NEFDeviceTriggerREPORT
NEFDeviceTriggerReplaceREPORT
NEFDeviceTriggerCancellationREPORT
NEFDeviceTriggerReportNotifyREPORT
Up

Up   Top   ToC