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.2  Functional requirements for LI in case of E-UTRAN access and GTP based S5/S8.Word‑p. 116

12.2.0  General |R12|

The target identities for interception at the MME, HSS, S-GW , PDN-GW and LI LCS Client are IMSI, MSISDN and ME (Mobile Equipment) Identity.
Details about information included in the ME Identity and the relationship with IMEI needs to be considered. The term Mobile Equipment Identity is used in this text according to TS 23.401 so as to indicate that the EPC should support multiple equipment identity formats (e.g. those from 3GPP2, WiMAX, etc) as well as the IMEISV.
As the MME only handles control plane, interception of Content of Communication is applicable only at the S-GW and PDN-GW. As the HSS only handles signaling, interception of Content of Communication is not applicable at this node.
LI in the PDN-GW is a national option.
For the delivery of the CC and IRI the S-GW and/or, per national option 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 EPS bearer.
The correlation number shall be generated by using existing parameters related to the EPS bearer.
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.
Editor's note: Location Dependent Interception for EPC is FFS.
Up

12.2.1  Provision of Intercept Related InformationWord‑p. 117

12.2.1.0  General |R12|

Intercept Related Information (Events) shall be sent at the Mobile Entity Attach, Mobile Entity Detach, Tracking Area/EPS Location Update, LALS Location Report, Bearer activation (valid for both Default and Dedicated bearer), Start of Intercept with bearer active, Start of Interception with E-UTRAN attached UE, Bearer Modification, Bearer Deactivation, Serving Evolved Packet System (applicable to the HSS), UE requested PDN connectivity, UE requested PDN disconnection, and UE requested bearer resource modification.
Serving Evolved Packet System and HSS related events event reporting are national options.
Up

12.2.1.1  X2-interface

The following information needs to be transferred from the EPS nodes or the HSS to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI, MSISDN, ME identity);
  • events and associated parameters as defined in clauses 12.2.1.2 and 12.2.3 may be provided;
  • the target location (if available) or the IAs in case of location dependent interception;
  • 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.
For HeNB interception, the MME shall provide in addition the following:
  • HeNB Identity;
  • HeNB location.
    HeNB location information needs to be transferred from the HeNB location verifying node to the DF2 in order to allow the DF2 to perform its functionality.
The EPS nodes detect packets containing packet header information in the communications path but the information needed for Packet Header Information Reporting may need to be transferred from the EPS nodes 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.2.1.2  Structure of the events

There are several different events in which the information is sent to the DF2 if this is required. Details are described in the following clause. The events for interception are configurable (if they are sent to DF2) in the EPC nodes or the HSS and can be suppressed in the DF2. The network procedures for which the events are generated are defined in TS 23.401.
The following events are applicable to the MME:
  • Attach;
  • Detach;
  • Tracking Area/EPS Location Update;
  • UE requested PDN connectivity;
  • UE Requested PDN disconnection;
  • Start of interception with E-UTRAN attached UE.
The following events are applicable to the Serving GW and PDN GW:
  • Bearer activation (valid for both Default and Dedicated bearer);
  • Start of intercept with bearer active;
  • Bearer modification;
  • Bearer deactivation;
  • UE Requested Bearer Resource Modification;
  • Packet Data Header Information.
The following events are applicable to the HSS:
  • Serving Evolved Packet System.
  • HSS subscriber record change;
  • Cancel location
  • Register location;
  • Location information request.
The following LALS Reports are applicable to the EPS (see Clause 19):
  • Report for LALS Target Positioning;
  • Report for LALS Enhanced Location for IRI.
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. 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.
A number of elements shown below can be also associated with the LALS reports. The transmission of the information from the LI LCS Client to DF2 is triggered by an LCS Server/GMLC response to the LI LCS Client request.
Element
Description

Observed MSISDN
MSISDN of the target.
Observed IMSI
IMSI of the target.
Observed ME Id
ME Id of the target; when it coincides with the IMEI, it shall be checked for each activation over the radio interface.
Event type
Indicates which type of event is delivered: Attach, Detach, Tracking Area Update, UE requested PDN connectivity, UE Requested PDN disconnection, UE Requested Bearer Resource Modification, Bearer activation, Start of intercept with bearer active, Start of interception with E-UTRAN attached UE, Bearer deactivation, Bearer modification, Serving Evolved Packet System, Packet Data Header Information, HSS subscriber record change, Cancel location, Register location, Location information request. In case of LALS report the event type is absent.
Event date
Date of the event generation in the ICE.
Event time
Time of the event generation in the ICE. Timestamp shall be generated relative to ICE internal clock.
Change Type
This indicates what has been changed (MSISDN, A-MSISDN or IMSI) in the Subscriber Change Record
PDN Type
The parameter is applicable to the MME only and provides the IP version (IPv4, IPv4/IPv6, IPv6) requested by the UE.
PDN Address Allocation
The parameter is applicable to the S-GW and PDN-GW; it provides the IP version (IPv4, IPv4/IPv6, IPv6) and IP address(es) allocated for the UE.
Protocol Configuration Options
Are used to transfer parameters between the UE and the PDN-GW (e.g. Address Allocation Preference by DHCP).
Attach type
Indicates the type of attach (may carry indication of handover in case of mobility with non-3GPP access).
Location Information
Location Information is the Tracking Area Identity (TAI), TA List assigned to the UE, E-CGI and/or location area identity or the derived Location from the LI LCS Client that is present at the node at the time of event record production. In case of Tracking Area Update event, the last visited TAI of the UE may be applicable. Country and network IDs can be considered as location information, by some national regulations. If the information in the MME received over S1 (TS 36.413) includes one or more cell IDs, then all cell IDs shall be reported to the LEMF whenever location reporting is triggered at the MME.
Time of Location
Date/Time of location. The time when location was obtained by the location source node.
PDN address(es)
The UE IP address(es) for the PDN connection.
APN
When provided by the MME, the parameter carries the Access Point Name provided by the UE. When provided by the S-GW/PDN-GW, it is the Access Point Name used for the connection.
RAT type
The Radio Access Type
APN-AMBR
The Aggregate Maximum Bit Rate for the APN.
Handover indication
Provides information from the GTPv2 protocol that the procedure is triggered as part of a handover.
Procedure Transaction Identifier
Identifies a set of messages belonging to the same procedure; the parameter is dynamically allocated by the UE.
EPS bearer identity
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN. The EPS Bearer Identity is allocated by the MME.
Bearer activation/deactivation type
Indicates the type of bearer being activated/deactivated, i.e. default or dedicated.
Linked EPS bearer identity
Indicates, in case of dedicated bearer, the EPS bearer identity of the default bearer.
Initiator
The initiator of the procedure, either the network, HeNB, or the UE.
Switch off indicator
Indicates whether a detach procedure is due to a switch off situation or not.
Detach type
Parameter sent by the network to the UE to indicate the type of detach.
Traffic Flow Template (TFT)
The EPS bearer traffic flow template (TFT) is the collection of all packet filters associated with that EPS bearer.
Traffic Aggregate Description (TAD)
The TAD consists of the description of the packet filter(s) for the traffic flow aggregate.
Serving MME address
The address of the serving MME.
Old Location Information
Location Information of the subscriber before Tracking Area Update. If the information in the MME (TS 36.413) received over S1 includes one or more cell IDs, then all cell IDs shall be reported to the LEMF whenever location reporting is triggered at the MME.
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.
Failed attach reason
Reason for failed attach of the target.
Failed bearer activation reason
Reason for failed bearer activation for the target.
Failed Bearer Modification reason
The reason for failure of Bearer Modification.
IAs
The observed Interception Areas.
Bearer Deactivation cause
The cause of deactivation of the PDP context.
EPS Bearer QoS
This field indicates the Quality of Service associated with the Bearer procedure.
Request type
Indicates the type of request in an UE requested PDN connectivity, i.e. initial request or handover.
CSG Identity
Uniquely identifies a CSG within one PLMN. Note: Open HeNBs do not have associated CSGs.
CSG List
Identifies the membership of a given CSG (i.e., CSG Identities and associated expiration data for the UEs).
HeNB Identity
Uniquely identifies a HeNB (i.e., HeNB equipment ID and HeNB name).
HeNB IP Address
The public IP address of the HeNB provided to the HeNB location verifying node
HeNB Location
Reports the location of the HeNB used during location verification.
ISP Operator Identity
Identifies the ISP through which the HeNB is connected to the SeGW (e.g., IP address).
Security Gateway IP Address
The IP Address of the Security Gateway that terminates the tunnel from the HeNB.
Tunnel Protocol
The tunnel protocol used between the HeNB and the SeGW.
ULI Timestamp
Indicates the time when the User Location Information was acquired.
The parameter is specified in TS 29.274.
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.
UE Local IP Address
The UE local IP address (IP SEC terminal Point) reported over GTP based S2b interface TS 29.274 based on local policy for Fixed Broadband access network interworking.
UE UDP Port
Used in case of GTP based S2b interface TS 29.274 if NAT is detected and UE Local IP Address is present for Fixed Broadband access network interworking.
WLAN location information
Used in case of GTP based S2b interface TS 29.274. Provides location information in form of TWAN Identifier, if available at ePDG/PDN-GW.
WLAN location timestamp
Used in case of GTP based S2b interface TS 29.274. Provides location information timestamp in form of TWAN Identifier Timestamp, if available at ePDG/PDN-GW.
ProSe Remote UE IDs
The identities of the ProSe remote UE connected to the Prose UE-to-NW Relay, see clause 17.3.
ProSe Remote UE IP info
The IP address(es) of the ProSe Remote UE connected to the ProSe UE-to-NW Relay, see clause 17.3.
location error code
LALS positioning error identification code
Secondary RAT Usage Indication
This is only reported by the S-GW.

Up

12.2.2  X3-interfaceWord‑p. 121
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.2.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.2.3  EPS related eventsWord‑p. 122

12.2.3.1  Attach

When an attach activation is generated from the mobile an attach event is generated by the MME. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • Failed attach reason
  • IAs (if applicable)
  • PDN Type
  • APN
  • Protocol Configuration Options
  • Attach type
  • EPS bearer identity
  • CSG Identity (if closed/hybrid H(e)NB)*
  • CSG List (if closed/hybrid H(e)NB)*
  • HeNB Identity*
  • HeNB IP Address*
  • HeNB Location*
  • Security Gateway IP address*
  • Tunnel Protocol*
  • ISP Operator Identity*
* These elements are applicable for HeNB interception only.
Up

12.2.3.2  Detach

For detach a detach-event is generated. The following elements will be delivered by the MME to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Detach initiator
  • Switch off indicator
  • Detach type
  • CSG Identity (if closed or hybrid HeNB)*
  • HeNB Identity*
  • HeNB IP Address*
  • HeNB Location*
* These elements are applicable for HeNB interception only.

12.2.3.3  Bearer activationWord‑p. 123
When a bearer activation is generated a bearer activation-event is generated by the S-GW/PDN-GW. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • RAT type (note 1)
  • PDN address allocation (note 1)
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • APN (Access Point Name) (note 1)
  • Bearer activation Type (default, dedicated)
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • Failed bearer activation reason
  • IAs (if applicable)
  • EPS bearer QoS (note 2)
  • APN-AMBR (note 3)
  • EPS bearer id (NSAPI)
  • Protocol Configuration Options
  • Initiator
  • Procedure Transaction Identifier
  • Linked EPS bearer identity (note 2)
  • Traffic Flow Template(s) (TFT) ( note 4)
  • Handover indication
  • UE Local IP Address (note 5)
  • UE UDP Port (note 5)
  • WLAN location information (note 5)
  • WLAN location timestamp (note 5)
Up

12.2.3.4  Bearer deactivation

When a bearer deactivation is generated a bearer deactivation-event is generated by the S-GW/PDN-GW. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Bearer deactivation Type (default, dedicated)
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • EPS bearer id
  • Initiator
  • Procedure Transaction Identifier
  • Bearer deactivation Cause (note )
  • ULI Timestamp
  • UE Local IP Address
  • UE UDP Port
  • WLAN location information
  • WLAN location timestamp
In case all the bearers belonging to the same PDN connection are released at the same time, one event shall be sent for each bearer.
Up

12.2.3.5  Bearer modificationWord‑p. 124
When a bearer modification is detected, a bearer modification event shall be generated. These elements will be delivered by the S-GW/PDN-GW to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Initiator
  • EPS Bearer QoS (Note 1)
  • EPS bearer id
  • Procedure Transaction Identifier
  • RAT type
  • APN-AMBR (Note 2)
  • Traffic Flow Template(s) (TFT)
  • Handover indication
  • Failed Bearer Modification reason
  • UE Local IP Address
  • UE UDP Port
  • WLAN location information
  • WLAN location timestamp
  • Second RAT Usage Indication
The event may also be used by the PDN-GW to indicate a handover between different accesses. In this case, the RAT type indicates the new access after the handover.
Up

12.2.3.6  Start of interception with active bearerWord‑p. 125
This event will be generated if interception for a target is started and if the target has at least the default bearer active. If more then one bearer is active, for each of them an event record is generated. The parameters which are defined for bearer activation (see related section) will be sent, if available, by the S-GW/PDN-GW to the DF2.
As an option, in case the event is sent due to a change of the involved S-GW, the new S-GW may provide as additional parameter, the "old location information". However, the absence of this information does not imply that interception has not started in the old location S-GW for an active bearer.
Up

12.2.3.7  Tracking Area/EPS Location Update

For each TA/EPS Location Update an update-event with the elements about the new location is generated. The event shall be sent in case of Tracking Area Update, UE triggered Service Request, X2 based handover, S1 based handover, as specified in TS 23.401 , and when the MME receives location information over S1. In case of change of MME, the new MME shall send the event, and the old MME may optionally send the event as well. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information (only for the new MME)
  • Old Location Information (only for the old MME)
  • Time of Location
  • IAs (if applicable)
  • Failure reason
  • HeNB Identity (NOTE1)
  • HeNB IP Address (NOTE1)
  • HeNB Location (NOTE1)
  • ProSe Remote UE(s) IDs (NOTE 2)
  • ProSe Remote UE(s) IP Info (NOTE 2)
Up

12.2.3.8  Serving Evolved Packet SystemWord‑p. 126
The Serving Evolved Packet System report event is generated at the HSS, when the HSS has detected that the target has roamed. The elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Serving MME Address

12.2.3.9  UE requested PDN connectivity

When a PDN connectivity is requested from the mobile to allow multiple PDN connections (TS 23.401), an UE requested PDN connectivity event is generated by the MME. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • APN
  • Request type
  • PDN type
  • Failed reason
  • IAs (if applicable)
  • Protocol Configuration Options
  • EPS bearer identity
  • HeNB Identity*
  • HeNB IP Address*
  • HeNB Location*
* These elements are applicable for HeNB interception only.
Up

12.2.3.10  UE requested PDN disconnection

When a PDN disconnection is requested from the mobile to request for disconnection from one PDN (TS 23.401), an UE requested PDN disconnection event is generated by the MME. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Linked EPS bearer identity
  • HeNB Identity*
  • HeNB IP Address*
  • HeNB Location*
* These elements are applicable for HeNB interception only.
Up

12.2.3.11  UE requested Bearer Resource ModificationWord‑p. 127
When UE requested Bearer Resource Modification TS 23.401 is detected at the S-GW/PDN-GW, an UE requested Bearer Resource Modification event is generated. These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Linked EPS bearer identity
  • EPS bearer identity
  • Procedure Transaction Identifier
  • EPS bearer QoS
  • Traffic Aggregate Description
  • Failed Bearer Modification reason
  • Protocol Configuration Options
Up

12.2.3.12Void

12.2.3.13  Start of interception with E-UTRAN attached UE |R10|

This event will be generated if interception for a target is started and if the target is already E-UTRAN attached. If there are multiple PDN connections active for the target then for each them an event report is generated.
These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME id
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • APN
  • PDN type
  • IAs (if applicable)
  • EPS bearer identity of the default bearer
  • CGS Identity (if closed or hybrid HeNB)*
  • CSG List (if closed or hybrid HeNB)*
  • HeNB Identity*
  • HeNB IP Address*
  • HeNB Location *
  • Security Gateway IP address*
  • Tunnel Protocol*
  • ISP Operator Identity*
* These elements are applicable for HeNB interception only.
Up

12.2.3.14  Packet Data Header Information |R12|Word‑p. 128
12.2.3.14.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.2.3.14.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 DF2 or via another network entity, if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Initiator
  • EPS bearer id
  • Handover indication
  • PDN Address Allocation
  • PDN address(es)
  • APN
  • Source IP Address
  • Destination IP Address
  • Destination Port Number
  • Transport Protocol (e.g., TCP)
  • Packet Size
  • Flow Label (IPv6 only)
Up
12.2.3.14.2  Packet Data Summary ReportWord‑p. 129
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 DF2 or via a MF for each packet flow if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed ME Id
  • Event Type
  • Event Time
  • Event Date
  • Correlation number
  • Network Element Identifier
  • Logical Function Information
  • Location Information
  • Time of Location
  • IAs (if applicable)
  • Initiator
  • EPS bearer id
  • Handover indication
  • PDN Address Allocation
  • PDN address(es)
  • APN
  • Care of address
  • 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) \endnl
    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.2.3.15  HSS subscriber record change |R13|Word‑p. 130
This event will be used to report any change of association between IMSI or MSISDN of the target.
The following elements, such as old and new IMSI or MSISDN will be delivered to DF2, if available:
  • New observed MSISDN or A MSISDN
  • New observed IMSI
  • Old observed MSISDN or A MSISDN
  • Old observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Change Type (MSISDN, A-MSISDN or IMSI)
  • Network Element Identifier (HSS id...)
  • Other update: carrier specific

12.2.3.16  Cancel location |R13|Word‑p. 131
This event "Cancel Location" will be used to report to DF2 when HSS send to MME one cancel location or purge to serving system.
The following elements such as the old serving system of the target will be delivered to DF2:
  • Observed MSISDN
  • Observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier (HSS Id...)
  • Previous visited MME Identifier

12.2.3.17  Register location |R13|

This event will be used to report one update location to the HSS for a target. The elements of previous and current serving system id will be delivered to DF2, if available:
  • Observed MSISDN
  • Observed IMSI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier (HSS id...)
  • Previous visited MME Identifier
  • Current visited MME Identifier

12.2.3.18  Location information request |R13|

This event will be used to report any location information of the target request activity.
The elements, observed IMSI, MSISDN, the identifier of the requesting node type and network, will be delivered to DF2, if available:
  • Observed MSISDN
  • Observed IMSI
  • Requesting network identifier (country identifier included)
  • Requesting node type
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier (HSS id...)


Up   Top   ToC