Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4   5…   5A…   6…   7…   7A…   8…   9…   10…   11…   12…   12.2…   12.3…   12.4…   12.5…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…   B…   C…   D…   E…   F…   G…   H…   I…   J…   L…

 

12.4  Functional requirements for LI in case of trusted non-3GPP IP accessWord‑p. 139

12.4.0  General |R12|

Differently to what happens in E-UTRAN case, in which the user traffic passes through the S-GW and then through the PDN-GW, there are two cases of access to the network through S2a (trusted Non-3GPP access) that require additional consideration. Specifically, the PDN-GW is the only possible ICE in the 3GPP network in the case of non-roaming (PDN-GW in the HPLMN) and in the case of roaming with local breakout (PDN-GW is located in the VPLMN) Therefore, in these cases, interception at the PDN-GW is required.
LI based on HSS reporting is a national option. Requirements on the HSS specified in clause7A.2 and subsections apply also to the case in which non-3GPP IP access and 3GPP AAA server are based. Intercept Related Information (Events) are in such case: serving system, subscriber record change, registration termination, and location information request.In case of access to the network through S2a (trusted Non-3GPP access) for roaming without local breakout (PDN-GW in the HPLMN and S-GW in the VPLMN), interception at the PDN-GW is a national option.
Interception in the S-GW and PDN-GW shall be based on IMSI or NAI.
For the delivery of the CC and IRI, the S-GW and/or PDN-GW provides correlation number and target identity to the DF2 and DF3 which is used there in order to select the different LEAs where the product shall be delivered.
The correlation number is unique in the whole PLMN and is used to correlate CC with IRI and the different IRI's of one IP-CAN session. However, when different protocols (i.e. GTP and PMIP) are used in the network, different values can be generated by different nodes
The correlation number shall be generated by using existing parameters related to the IP-CAN session.
If interception has been activated for both parties of the Packet Data communication both CC and IRI shall be delivered for each party as separate intercept activity.
Up

12.4.1  Provision of Intercept Related InformationWord‑p. 140

12.4.1.0  General |R12|

Intercept Related Information (Events) shall be sent at attach/tunnel activation on interfaces s2a and s2c, session modification, detach/tunnel deactivation, start of interception with active tunnel, PDN-GW reallocation upon initial attach on s2c, PDN GW initiated resource allocation Deactivation on s2a, Serving Evolved Packet System.
Serving Evolved Packet System reporting is a national option.

12.4.1.1  X2-interface

The following information needs to be transferred from the S-GW, PDN-GW or the HSS to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity;
  • events and associated parameters as defined in clause 12.4.1.2 and 12.4.3 may be provided;
  • the target location (if available) or the IAs in case of location dependent interception; (FFS)
  • date/time of Location (if target location provided);
  • correlation number;
  • Quality of Service (QoS) information, if available;
  • encryption parameters (keys and associated parameters for decrypting CC), if available and necessary.
The PDN-GW/S-GW detect packets containing packet header information in the communications path but the information needed for Packet Data Header Information Reporting may need to be transferred from the PDN-GW/S-GW either directly to the DF2 or via another network entity in order to allow the DF2 to perform its functionality.
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

12.4.1.2  Structure of the events

There are several different events in which the information is sent to the DF2 if this is required. The events for interception are configurable (if they are sent to DF2) in the S-GW, PDN-GW or the HSS and can be suppressed in the DF2.
The following events are applicable to the S-GW:
  • PMIP attach/tunnel activation;
  • PMIP detach/tunnel deactivation;
  • PMIP session modification;
  • Start of interception with active PMIP tunnel;
  • Packet Data Header Information.
The following events are applicable to the PDN-GW:
  • PMIP attach/tunnel activation;
  • PMIP detach/tunnel deactivation;
  • PMIP session modification;
  • Start of interception with active PMIP tunnel;
  • MIP registration/tunnel activation;
  • DSMIP registration/tunnel activation;
  • DSMIP session modification;
  • MIP deregistration/tunnel deactivation;
  • DSMIP deregistration/tunnel deactivation;
  • Start of interception with active MIP tunnel;
  • Start of interception with active DSMIP tunnel;
  • DSMIP HA Switch;
  • PMIP Resource Allocation Deactivation;
  • MIP Resource Allocation Deactivation;
  • Bearer activation;
  • Bearer deactivation;
  • Bearer modification;
  • Start of interception with active bearer;
  • Packet Data Header Information.
The following event is applicable to the HSS, which may be requested by national regulations:
  • Serving Evolved Packet System;
  • Subscriber record change;
  • Registration termination;
  • Location information request.
A set of elements as shown below can be associated with the events. The events trigger the transmission of the information from the nodes to DF2. Available IEs from this set of elements as shown below can be extended in the nodes, if this is necessary as a national option. DF2 can extend available information if this is necessary as a national option. In case GTP protocol is used over s2a interface, elements from table 12.2.1.2 are included in the applicable events. If interception is performed at the PDN GW, then Packet Data Header Information reporting shall also be performed at the PDN GW and not at the Serving GW.
Element
Description

Observed MN NAI
The Network Access Identifier of the Mobile Node (target identity).
Observed IMSI
The IMSI of the target
New observed MN NAI
The new Network Access Identifier of the Mobile Node (target identity).
New observed IMSI
The new IMSI of the target
Old observed MN NAI of the target (if available)
Old observed IMSI of the target (if available)
Event type
Indicates which type of event is delivered: PMIP attach/tunnel activation, PMIP detach/tunnel deactivation, PMIP session modification, Start of interception with active PMIP tunnel, MIP registration/tunnel activation, DSMIP registration/tunnel activation, DSMIP session modification, MIP deregistration/tunnel deactivation, DSMIP deregistration/tunnel deactivation, Start of interception with active MIP tunnel, Start of interception with active DSMIP tunnel, DSMIP HA Switch, PMIP resource Allocation Deactivation, MIP Resource Allocation Deactivation, Serving Evolved Packet System, Subscriber record change, Registration termination, Location information request, Packet Data Header Information.
Event time
Time of the event generation in the ICE. Time stamp shall be generated relative to ICE internal clock.
Event date
Date of the event generation in the ICE.
Change type
This indicates what has been changed (MSISDN, IMSI, or IMEI) in the Subscriber Change Record
Correlation number
The correlation number is used to correlate CC and IRI.
Network Element Identifier
Unique identifier for the ICE reporting the event.
Logical Function Information
Used to distinguish between multiple logical functions operating in a single physical network element.
Lifetime
Indicates the lifetime of the tunnel; shall be set to a nonzero value in the case of registration or lifetime extension; is set to zero in case of deregistration.
Failed attach reason
Reason for the failed attach/tunnel deactivation of the target.
Session modification failure reason
Reason for a failure of a session modification attempt for the target
Access technology type
Indicates the Radio Access Type.
Handover indicator
Provides information on whether the triggered as part of a handover.
APN
The Access Point Name used for the connection.
UE address info
Includes one or more IP addresses allocated to the UE.
Additional Parameters
Additional information provided by the UE, such as protocol configuration options.
PDN address(es)
The UE IP address(es) for the PDN connection.
Home address
Contains the UE Home IP address.
Home Agent address
Contains the IP address of the Home Agent.
Requested IPv6 Home Prefix
The IPv6 Home Prefix requested by the UE.
IPv6 home prefix
The IPv6 home prefix assigned by the PDN GW to the UE.
Care of Address
The Local IP address assigned to the UE by the Access Network, used as Care of Address for DSMIPv6 over S2c reference point.
HSS/AAA address
The address of the HSS/AAA triggering the PDN-GW reallocation.
Target PDN-GW address
The address of the PDN-GW which the UE will be reallocated to.
Revocation trigger
Contains the cause for the revocation procedure.
Foreign domain address
The relevant IP address in the foreign domain.
Visited network identifier
An identifier that allows the home network to identify the visited network TS 29.273
Location Information
Location information of the target, e.g. 3GPP2-BSID TS 29.212. Provided if available from the PCRF.
Time of Location
Date/Time of location. The time when location was obtained by the location source node.
Initiator
The initiator of the procedure, either the network or the UE.
Destination IP Address
The IP address, including type IPv4 or IPv6, of the destination of the IP packet.
Destination Port Number
The port number of the destination of the IP packet.
Flow Label (IPv6 only)
The field in the IPv6 header that is used by a source to label packets of a flow (see RFC 3697 [41]).
Packet Count
The number of packets detected and reported (for a particular summary period).
Packet Data Summary Reason
The reason for a Packet Data Summary message being sent to the LEMF (e.g., timed out, counter expiration, end of session)
Packet Size
The size of the packet. (i.e., Total Length Field in IPv4 or Payload Length field in IPv6)
Source IP Address
The IP address, including type IPv4 or IPv6, of the source of the IP packet.
Source Port Number
The port number of the source of the IP packet.
Sum of Packet Sizes (for a particular summary period)
The sum of values contained in the Total Length fields of the IPv4 packets or the sum of the values contained in the Payload Length fields of the IPv6 packets.
Summary Period
Includes the dates and times of the first and last packets in a particular packet data interval.
Transport Protocol (e.g., TCP)
The identification of the transport protocol of the packet or packet flow being reported.
Any User-Data (AVP Name):
any change in the profit and identities of the target (if available in the Diameter message)
Any Associated-Identities (AVP Name):
any change of any associated identities of the target
Request direction:
Information if the serving node is requesting to the HSS, or requested by the
HSS.
Other update:
carrier specific of target's data that are in the intercepted diameter messages
Other Public User Identities
Other IMPU or IMPI that was allocated to Target and will be deregistered (if available)
Requesting node identifier
(I CSCF; AS) that are interfaced directly in the HSS and transmitting a diameter message from a network
Requesting network node identifier
such as IP-SM-GW Id, GMSC Id, SGSN Id, MME Id GMLC Id (country identifier is included in such request) that are in the different diameter messages related to location request for information (to route the right SMS or Call attempt, or GMLC based location request, to the right node on which is attached the target.)
Requesting node type
(IP-SM-GW AS, GMSC, SGSN, MME, GMLC) (if available)

Up

12.4.2  X3-interfaceWord‑p. 144
The access method for the delivering of S-GW and/or PDN-GW Intercept Product is based on duplication of packets without modification at the S-GW and/or PDN-GW. The duplicated packets with additional information in a header are sent to DF3 for further delivery to the LEA.
[not reproduced yet]
Figure 12.4.2.1: Configuration for interception of S-GW/PDN-GW product data
Up
In addition to the intercepted content of communication, the following information needs to be transferred from the S-GW and/or the PDN-GW to the DF3 to perform its functionality:
  • target identity;
  • correlation number;
  • time stamp (optional);
  • direction (indicates whether T-PDU is MO or MT) - optional;
  • the target location (if available) or the IAs in case of location dependent interception;
  • date/time of Location (if target location provided).

12.4.3  LI events for trusted Non-3GPP IP access

12.4.3.1  Initial Attach and PDN connection activation with PMIPv6 on S2a

When the Attach or PDN connectivity activation is detected over PMIP at the S-GW, PDN-GW, a PMIP attach/tunnel activation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Lifetime
  • Failed attach reason
  • Access Technology Type
  • Handover Indicator
  • APN
  • UE Address Info
  • Additional Parameters
  • Location Information
  • Time of Location

12.4.3.2  Initial Attach and PDN connection activation procedures with MIPv4 FACoA on S2aWord‑p. 145
When the Attach or PDN connectivity activation is detected over MIP at the PDN-GW, a MIP registration/tunnel activation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Lifetime
  • Failed attach reason
  • Home Address
  • Care of Address
  • Home Agent Address
  • APN
As the S-GW has no Home Agent function, the event is not applicable to the S-GW. The use of MIPv4 in roaming case requires Local Breakout (PDN-GW in VPLMN), so LI in the PDN-GW is mandatory in order to intercept in this scenario.
Up

12.4.3.3  Initial Attach and PDN connection activation procedures with DSMIPv6 over S2c

When the Attach or PDN connectivity activation is detected over DSMIP at the PDN-GW, a DSMIP registration/tunnel activation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Lifetime
  • Requested IPv6 home prefix
  • Home address
  • APN
  • Care of Address
  • Failed attach reason

12.4.3.4  Detach and PDN disconnection with PMIPv6 on S2aWord‑p. 146
When a Detach or PDN disconnection is detected over PMIP at the S-GW, PDN-GW, a PMIP detach/tunnel deactivation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • APN
  • Initiator
  • Location Information
  • Time of Location

12.4.3.5  Detach and PDN disconnection with MIPv4 FACoA

When a Detach or PDN disconnection is detected over MIP at the PDN-GW, a MIP deregistration/tunnel deactivation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Home Address
  • Home Agent Address
  • Care of address
  • Initiator

12.4.3.6  Detach and PDN disconnection with DSMIPv6 on S2c

When a Detach or PDN disconnection is detected over DSMIP at the PDN-GW, a DSMIP deregistration/tunnel deactivation event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Home Address
  • Initiator

12.4.3.7  PDN-GW reallocation upon initial attach on s2cWord‑p. 147
When a PDN GW reallocation procedure is detected by the PDN-GW, a DSMIP HA Switch event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Network Element Identifier
  • Logical Function Information
  • HSS/AAA address
  • Target PDN-GW address

12.4.3.8  PDN GW initiated Resource Allocation Deactivation with S2a PMIP

When a PDN GW initiated resource allocation deactivation is detected by the S-GW/PDN-GW, a PMIP Resource Allocation Deactivation event shall be sent. The following elements will be delivered to DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Network Element Identifier
  • Logical Function Information
  • Revocation trigger
  • UE address info
  • Correlation number
  • Location Information
  • Time of Location

12.4.3.9  PDN GW initiated Resource Allocation Deactivation with S2a MIP v4

When a PDN GW initiated resource allocation deactivation is detected, a MIP Resource Allocation Deactivation event shall be sent. The following elements will be delivered to DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Date
  • Event Time
  • Network Element Identifier
  • Logical Function Information
  • Home Address
  • Foreign domain address
  • Correlation number

12.4.3.10  Serving Evolved Packet SystemWord‑p. 148
The Serving Evolved Packet System report event is generated at the HSS, when the HSS has detected that the target has roamed. Such events could be mainly triggered by Diameter messages such as:
  • Through SWx interface, Server-Assignment-Request in case of command of 3GPP AAA to HSS (see clause A of TS 29.273, and clause 5 of GSMA IR.61 [65]).
The elements of table 12.4.3.10 will be delivered to the DF2 if available:
Information Element

Observed MSISDN
Observed IMSI
Observed ME Identity
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Visited Network Identifier (for example: AVP name such as Visited-PLMN-Id)

Up

12.4.3.11  Start of interception with active tunnel or bearer

When interception is started at the S-GW, PDN-GW and the target has an already active tunnel or bearer, a start of interception with active tunnel/bearer shall be generated. Separate events are defined for the different protocols. The event shall be detected by the same node for which tunnel/bearer activation reporting is applicable and reported with the same parameters required for the specific protocol (PMIP, MIP, DSMIP, GTP) tunnel/bearer activation event, as defined in the related sections. One event shall be sent for each active tunnel/bearer.
Up

12.4.3.12  PMIP session modification |R11|

When a session modification is detected at the S-GW/PDN-GW, a PMIP session modification event shall be generated by the S-GW/PDN-GW. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed MSISDN
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Correlation number
  • Lifetime
  • UE Address Info
  • Access Technology Type
  • Additional Parameters
  • Session modification failure reason
  • Serving Network
  • Handover indicator
  • DHCPv4 Address Allocation Indication
  • Location information
  • Time of Location
Up

12.4.3.13  DSMIP session modification |R11|

When the session modification is detected over DS-MIPv6 at the PDN-GW, a DSMIP session modification event shall be generated. The following elements will be delivered to the DF2 if available:
  • Observed MN NAI
  • Observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Lifetime
  • Session modification failure reason
  • Home address
  • Care of Address
  • APN
  • Requested IPv6 Home Prefix

12.4.3.14  Bearer activation |R12|Word‑p. 149
When the Initial attach in WLAN on GTP S2a (TS 23.402) or the Dedicated bearer activation in WLAN on GTP S2a (TS 23.402) is detected in the PDN-GW, a Bearer activation event shall be generated. The elements listed in the section 12.2.3.3 will be delivered to the DF2 if available.

12.4.3.15  Bearer deactivation |R12|

When the Detach and PDN disconnection in WLAN on GTP S2a (TS 23.402) or the PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2 (TS 23.402 is detected in the PDN-GW, a Bearer deactivation event shall be generated. The elements listed in the section 12.2.3.4 will be delivered to the DF2 if available.

12.4.3.16  Bearer modification |R12|

When the Network initiated bearer modification in WLAN on GTP S2a (TS 23.402) is detected in the PDN-GW, a Bearer modification event shall be generated. The elements listed in the section 12.2.3.5 will be delivered by the PDN-GW to the DF2 if available.

12.4.3.17  Packet Data Header Information |R12|

12.4.3.17.0  Introduction
Packet Data Header Information reporting can be done either on a per-packet (i.e., non-summarized) basis or in a summary report.
12.4.3.17.1  Packet Data Header Report
This event is used to provide packet header reports on a per packet basis (non-summarized reporting) and is triggered by each packet sent or received by the target. These elements will be delivered by the S-GW/PDN-GW either directly to the DF2 or via another network entity if available:
  • Observed MN NAI
  • Observed MSISDN
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Correlation number
  • Lifetime
  • UE Address Info
  • Access Technology Type
  • Serving Network
  • Home address
  • Care of Address
  • APN
  • Location information
  • Time of Location
  • Source IP Address
  • Source Port Number
  • Destination IP Address
  • Destination Port Number
  • Transport Protocol (e.g., TCP)
  • Packet Size
  • Flow Label (IPv6 only)
Up
12.4.3.17.2  Packet Data Summary ReportWord‑p. 150
This event is used to report:
  1. the source and destination information derived from the packet headers, including:
    1. source and destination IP Addresses,
    2. IP next-layer protocol,
    3. Layer-4 ports, and
    4. Flow label, if the packet is IPv6
  2. summary information for the number of packets and bytes transmitted or received by the target for each unique packet flow within an EPS bearer, and
  3. the date and the time of the first and last packets associated with that packet flow. A packet flow is defined as the 6-tuple of source/destination IP address/port number and the layer 4 protocol and EPS bearer.
    IP addresses and the IP next-layer protocol are always reported, the flow label is reported if the packet is IPv6, and the layer-4 ports are reported.
The event provides packet summary reports for each unique packet data session (EPS bearer) and packet flow, and is triggered by one of the following:
  • start of a packet flow associated with an EPS bearer
  • an interim report for a packet flow associated with an EPS bearer is to be reported
  • end of a packet flow associated with an EPS bearer (including end of the EPS bearer itself).
An interim report can be triggered by
  • The expiration of a configurable timer per intercept (called a Summary Timer). The Summary Timer is configurable in units of seconds;
  • A per-intercept configurable count threshold is reached.
These elements will be delivered either directly to the DF2 or via a MF for each packet flow if available:
  • Observed MN NAI
  • Observed MSISDN
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Correlation number
  • Lifetime
  • UE Address Info
  • Access Technology Type
  • Serving Network
  • Home address
  • Care of Address
  • APN
  • Location information
  • Time of Location
  • Source IP Address
  • Source Port Number
  • Destination IP Address
  • Destination Port Number
  • Transport Protocol (e.g., TCP)
  • Flow Label (IPv6 only)
  • Summary Period
  • Packet Count (for this summary period)
  • Sum of Packet Sizes (for this summary period)
If the packets are IPv4, the sum of all observed packet sizes is the sum of the values contained in the Total Length field of each packet as specified in IETF RFC 791[39].
If the packet is IPv6, the sum of all observed packet sizes is the sum of the values contained in the Payload Length field for each packet as specified in IETF RFC 2460 [40].
If no packets were detected for the duration of the Summary Timer, then the Packet Data Summary Report shall not be sent.
Up

12.4.3.18  HSS subscriber record change |R13|Word‑p. 151
This event will be only used to report when there is a change of association between IMSI, MSISDN or IMEI of the target. It is induced mainly by Subscriber Profile management by the HSS or the CSP administration tools through the HSS.
Such events could be mainly triggered by Diameter messages such as:
  • Through SWx interface, -Push-Profile-Request (PPR) in case of command of HSS to 3GPP AAA Server: see clause A of TS 29.273.
The elements of table 12.4.3.18 will be delivered to DF2, if available.
Information Element

New observed MSISDN
New observed IMSI
New Observed IMEI (if available)
Old observed MSISDN
Old observed IMSI
Old observed IMEI (if available)
Event Type
Event Time
Event Date
Network Element Identifier (HSS id...)
Change Type (MSISDN, IMSI or IMEI)
Other update: carrier specific.

Up

12.4.3.19  Registration Termination |R13|Word‑p. 152
This event "Registration Termination" will be used to report to DF2 when HSS send to 3GPP AAA Server It is the equivalent of cancel location or purge to serving system in CS domain. This kind of event is induced by the registration of the target. The event will be triggered by the following Diameter messages:
  • Through SWx interface, Server-Assignment-Request indicating deregistration from 3GPP AAA Server to HSS: see clause A of TS 29.273;
  • Through SWx interface, Registration-Termination- Request from HSS to 3GPP AAA Server: see clause A of TS 29.273.
The elements of table 12.4.3.19 will be delivered to DF2.
Information Element

Observed MSISDN
Observed IMSI
Event Type
Event Time
Event Date
Network Element Identifier (HSS Id...)
Previous serving system identifier (if available)

Up

12.4.3.20  Location Information request |R13|

This event will be used to report any location information request on the target by a node to HSS, when the target is connected to trusted non-3GPP IP access. A location information request could be generated by an IP-SM-GW AS (as an SMS Centre) or GMSC or SGSN or MME from another Network through a diameter request transmitted by either an AS or the I CSCF of the home network to the HSS of the target. The event will be triggered by the following Diameter messages:
  • Through Sh interface, User Data Request with content related to update location from AS to HSS, see clause A.2 of TS 29.328 and TS 29.329;
  • Through Cx interface, Location Info Request from I CSCF to HSS; see clause A.2 of TS 29.228.
The elements, observed IMSI, MSISDN, the identifier of the requesting node type and network, of table 12.4.3.20 will be delivered to DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Requesting network identifier such as PLMN Id (country identifier included),
Requesting node type (IP-SM-GW AS, GMSC, SGSN, MME, GMLC)
Event Type
Event Time
Event Date
Network Element Identifier (HSS id...)

Up


Up   Top   ToC