Probe Cell RAT Handover v1.0

Probe Cell RAT Handover v1.
Introduction
OTARIE probe uses some information carried by the network to be able to provide detailed traffic classification. In this document, we focus on level of
information OTARIE probe can provide about RadioAccessType and Cell identification.
This information is retrieved from RADIUS accounting tickets when OTARIE probe is deployed over Gi and from GTP-C messages when OTARIE probe is
deployed over Gn.
According to protocol and GGSN/SGSN configuration, OTARIE may see all messages/packets (start/intermediate, stop) all along a session so as a
consequence, level of information provided by OTARIE probe is directly linked to the messages OTARIE probes receives and so processes.
OTARIE Probe in Gi Mode

In Gi mode, OTARIE probe uses RADIUS accounting tickets and is able to retrieve
Radio Access Type information : allows to identify the mobile network (2G, 3G, …)
Location-Information : allows to identify the mobile network cell id
IMEI : allows to identify the Terminal identification
APN information
For each session, mandatory messages are START and STOP:
The classification is initiated and triggered only when a RADIUS accounting ticket is received with the "Acct-Status-Type" set to start.
The classification is stopped when a RADIUS accounting ticket is received with the "Acct-Status-Type" set to stop.
Some other optional messages may be sent.According to the configuration or Acct-Interim-Interval RADIUS attribute, a RADIUS accounting ticket with
"Acct-Status-Type" set to Interim-Update MAY BE sent. This sending is optional and may be triggered in different use cases:
Switch from one RAT to another one

Cell hand-over (switch from one cell to another one)
And so on
On a single 6 minutes steps, if X (greater than zero) INTERIM-UPDATE are received for one MSISDN , then X+1 lines will be generated for this specific
customer in NewCust file including retrieved information (RAT, Loc-Info) from the involved INTERIM-UPDATE message. (see Note2 about current
Dashotarie implementation)
Conclusion: If INTERIM-UPDATE messages are not sent and so are not processed by OTARIE probe then information of Cell Identification and/or Radio
Access Type is not updated so initial information is kept and generated in probe flat files meaning that statistics all along a session are based on initial cell
id and/or initial radio access type.
OTARIE Probe in Gn Mode

OTARIE needs to see GTP-C packets to provide detailed traffic classification.
Based on GTP-C, OTARIE is able to retrieve :
Radio Access Type information : allows to identify the mobile network (2G, 3G, …)
Location-Information : allows to identify the mobile network cell id
IMEI : allows to identify the Terminal identification
APN information
For each session, mandatory messages are :
The classification is initiated and triggered only when a CREATE PDP CONTEXT is received.
The classification is stopped when a DELETE PDP CONTEXT is received.
In Gn Mode, Update PDP Context Request messages are mandatory and should be provided at each RAT modifications during one specific session but
are not mandatory for cells handover.
On a single 6 minutes steps, if X (greater than zero) Update PDP Context Request messages are received for one MSISDN , then X+1 lines will be
generated for this specific customer in NewCust file including retrieved information (RAT, Loc-Info) from the involved Update PDP Context Request
message . (see Note2 about current Dashotarie implementation)
Note1 -29.060 3GPP standard specification : An Update PDP Context Request message shall be sent from an SGSN to a GGSN as part of the GPRS
inter-SGSN Routeing Area Update procedure, the PDP Context Modification procedure, to redistribute contexts due to load sharing or as part of the inter-
system intraSGSN update procedure i.e. UE transitioning between UTRAN and GERAN A/Gb mode (and vice versa) on the same SGSN and if the SGSN
decides to enable a direct GTP-U tunnel between the GGSN and the RNC. It shall be used to change the QoS and the path. For the inter-SGSN Routeing
Area Update procedure the message shall be sent by the new SGSN. The Update PDP Context Request shall also be used as part of the Secondary PDP
Context Activation Procedure to indicate that RAN Procedures are ready and that the SGSN is ready to receive payload from the GGSN on the new PDP
Context.
Conclusion: If UPDATE PDP CONTEXT messages are not sent or are partially sent and so are not processed by OTARIE probe then information of Cell
Identification and/or Radio Access Type is not updated so initial information is kept and generated in probe flat files meaning that generated statistics all
along a session are based on initial cell id and/or initial radio access type.
Note2 - Dashotarie Implementation : INTERIM-UPDATE/UPDATE PDP CONTEXT management for RAT and Cell-Info processing
In current implementation (3.5.5), primary key, used to generate a new line in the statAppli table containing global aggregated data, does not include RAT
and Loc-Info so it means that in case there are several lines in NewCust for one specific MSISDN during one single 6 minutes step, then only the RAT and
Loc-Info information of the first line during the 6 minutes step is taken into account.
This may be improved in future release and has to be validated carefully as number of lines to be processed may increase.

Probe Cell RAT Handover v1.0

Uploaded by

Copyright:

Available Formats

Probe Cell RAT Handover v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Probe Cell RAT Handover v1.0

Uploaded by

Copyright:

Available Formats

Probe Cell RAT Handover v1.

OTARIE Probe in Gi Mode

For each session, mandatory messages are START and STOP:

Switch from one RAT to another one

OTARIE Probe in Gn Mode

For each session, mandatory messages are :

You might also like