Smartphone signaling

**banisha** · 2012-10-08, 08:59 PM

Hi all,

Evaluation of smartphone impact on network is needed.
Some advice please on which counters, and KPI to follow to best estimate this influence of smartphones on our 3G network.
Network vendor is NSN.

Ideas and advice are welcome.

Thanks!

**Finetopix** · 2012-10-08 08:59 PM

**vsousa** · 2012-10-09, 01:11 AM

Hi Banisha,

One of most crucial impacts of the smartphones on a 3G nw is Signalling on the RNC (cpu load), and the constant change of RRC states, usually caused by chatty apps, there is already very interesting reports about this done by several vendors and other company's, you can find it here in the forum, (e.g. Signals research (very good) , Huawei, ...)
Hope it helps

**RF engineer** · 2012-10-09, 02:22 AM

Dear

can you share some huawei document about this signalling

BR

**vsousa** · 2012-10-09, 06:29 AM

You can find in attach the Huawei doc about this

huawei - behaviour analysis of smarthphone.7z

Regards

if it helps give reps

**tyberry** · 2012-10-09, 01:30 PM

I'm extremely interested in this posts, I'm looking to understand device performance for Smartphones on 4G LTE networks, the networks are E******* 4G LTE and Alcatel Lucent 4G LTE. I'm interested in finding if anyone can share Tektronix IrisView traffic samples of NAS EMM/ESM Failure cause codes sample files. I need to find out which devices are experiencing which types of failure cause codes and why in the network, and then finally compare between E******* and Alcatel Lucent. The list of failure cause codes associated to procedures is as follows, if any one can send any LTE traffic captures and also any experience/case studies that would be extremely helpful?

In the coming weeks I will be putting some examples together for my specific customer but i need some ideas from other networks?

Response Code Protocol	Procedure	Response Code Category	Response Code ID	Response Code Name
S1MME NAS EMM	Attach	General Failure	70000	Timeout
S1MME NAS ESM	Bearer Resource Allocation		2	IMSI unknown in HSS
	Bearer Resource Modification		3	Illegal UE
	Combined Attach		6	Illegal ME
	Combined Tracking Area Update		7	EPS services not allowed
	Dedicated EPS Bearer Context Activation		8	EPS services and non-EPS services not allowed/Operator determined barring
	Default EPS Bearer Context Activation		9	UE identity cannot be derived by the network
	EMM Authentication		10	Implicitly detached
	EMM First Paging		11	PLMN not allowed
	EMM GUTI Reallocation		12	Tracking area not allowed
	EMM Identification		13	Roaming not allowed in this tracking area
	EMM Paging		14	EPS services not allowed in this PLMN
	EMM Security Mode Control		15	No suitable cells in tracking area
	EPS Bearer Context Deactivation		16	MSC temporarily not reachable
	EPS Bearer Context Modification		17	Network failure
	Extended Service Request - MO Call		18	CS domain not available
	Extended Service Request - MO Emergency Call		19	ESM failure
	Extended Service Request - MT Call		20	MAC failure
	Network Initiated Detach - IMSI Detach		21	Synch failure
	Network Initiated Detach - Re-attach Not Required		22	Congestion
	Network Initiated Detach - Re-attach Required		23	UE security capabilities mismatch
	Normal Tracking Area Update		24	Security mode rejected, unspecified
	Periodic Tracking Area Update		25	Not authorized for this CSG
	Service Request		26	Insufficient resources/Non-EPS authentication unacceptable
	UE Initiated Detach - Combined Detach		27	Unknown or missing access point name
	UE Initiated Detach - EPS Detach		28	Unknown PDN type
	UE Initiated Detach - IMSI Detach		29	User authentication failed
	UE Requested PDN Connectivity - Handover		30	Request rejected by Serving GW or PDN GW
	UE Requested PDN Connectivity - Initial Request		31	Request rejected, unspecified
	UE Requested PDN Disconnect		32	Service option not supported
			33	Requested service option not subscribed
			34	Service option temporarily out of order
			35	PTI already in use
			37	EPS QoS not accepted
			38	Network failure
			39	CS domain temporarily not available
			40	No EPS bearer context activated
			41	Semantic error in the TFT operation
			42	Syntactical error in the TFT operation
			43	Invalid EPS bearer identity
			44	Semantic errors in packet filter(s)
			45	Syntactical error in packet filter(s)
			46	EPS bearer context without TFT already activated
			47	PTI mismatch
			49	Last PDN disconnection not allowed
			50	PDN type IPv4 only allowed
			51	PDN type IPv6 only allowed
			52	Single address bearers only allowed
			53	ESM information not received
			54	PDN connection does not exist
			55	Multiple PDN connections for a given APN not allowed
			56	Collision with network initiated request
			59	Unsupported QCI value
			81	Invalid PTI value
			95	Semantically incorrect message
			96	Invalid mandatory information
			97	Message type non-existent or not implemented
			98	Message type not compatible with protocol state
			99	Information element non-existent or not implemented
			100	Conditional IE error
			101	Message not compatible with protocol state
			111	Protocol error, unspecified
			112	APN restriction value incompatible with active EPS bearer context

**tyberry** · 2012-10-09, 01:35 PM

One example I saw was E******* 4G network, they had enable a patch which improved the RRC drop rate nation wide, (change of a parameter on the Implicit Detach) the results were compared to all the devices and all had seen an improvement apart from the ******** droid model which was still experiencing a lot of problems.

Such are examples that I'm looking for? plus any 4G traffic captures from Tek/JDSU/Anritsu...anyone basically?

**banisha** · 2012-10-09, 05:48 PM

Originally Posted by vsousa

Hi Banisha,

One of most crucial impacts of the smartphones on a 3G nw is Signalling on the RNC (cpu load), and the constant change of RRC states, usually caused by chatty apps, there is already very interesting reports about this done by several vendors and other company's, you can find it here in the forum, (e.g. Signals research (very good) , Huawei, ...)
Hope it helps

Hi,

These are the documents that I already read. I am now interested in specific counters and KPI that can be followed on NSN vendor.
The goal is to make smartphone report that can be later compared to another network with different equipment vendor and compare smartphone impact.

BR

**vsousa** · 2012-10-24, 07:20 PM

Originally Posted by tyberry

I'm extremely interested in this posts, I'm looking to understand device performance for Smartphones on 4G LTE networks, the networks are E******* 4G LTE and Alcatel Lucent 4G LTE. I'm interested in finding if anyone can share Tektronix IrisView traffic samples of NAS EMM/ESM Failure cause codes sample files. I need to find out which devices are experiencing which types of failure cause codes and why in the network, and then finally compare between E******* and Alcatel Lucent. The list of failure cause codes associated to procedures is as follows, if any one can send any LTE traffic captures and also any experience/case studies that would be extremely helpful?

In the coming weeks I will be putting some examples together for my specific customer but i need some ideas from other networks?

Response Code Protocol	Procedure	Response Code Category	Response Code ID	Response Code Name
S1MME NAS EMM	Attach	General Failure	70000	Timeout
S1MME NAS ESM	Bearer Resource Allocation		2	IMSI unknown in HSS
	Bearer Resource Modification		3	Illegal UE
	Combined Attach		6	Illegal ME
	Combined Tracking Area Update		7	EPS services not allowed
	Dedicated EPS Bearer Context Activation		8	EPS services and non-EPS services not allowed/Operator determined barring
	Default EPS Bearer Context Activation		9	UE identity cannot be derived by the network
	EMM Authentication		10	Implicitly detached
	EMM First Paging		11	PLMN not allowed
	EMM GUTI Reallocation		12	Tracking area not allowed
	EMM Identification		13	Roaming not allowed in this tracking area
	EMM Paging		14	EPS services not allowed in this PLMN
	EMM Security Mode Control		15	No suitable cells in tracking area
	EPS Bearer Context Deactivation		16	MSC temporarily not reachable
	EPS Bearer Context Modification		17	Network failure
	Extended Service Request - MO Call		18	CS domain not available
	Extended Service Request - MO Emergency Call		19	ESM failure
	Extended Service Request - MT Call		20	MAC failure
	Network Initiated Detach - IMSI Detach		21	Synch failure
	Network Initiated Detach - Re-attach Not Required		22	Congestion
	Network Initiated Detach - Re-attach Required		23	UE security capabilities mismatch
	Normal Tracking Area Update		24	Security mode rejected, unspecified
	Periodic Tracking Area Update		25	Not authorized for this CSG
	Service Request		26	Insufficient resources/Non-EPS authentication unacceptable
	UE Initiated Detach - Combined Detach		27	Unknown or missing access point name
	UE Initiated Detach - EPS Detach		28	Unknown PDN type
	UE Initiated Detach - IMSI Detach		29	User authentication failed
	UE Requested PDN Connectivity - Handover		30	Request rejected by Serving GW or PDN GW
	UE Requested PDN Connectivity - Initial Request		31	Request rejected, unspecified
	UE Requested PDN Disconnect		32	Service option not supported
			33	Requested service option not subscribed
			34	Service option temporarily out of order
			35	PTI already in use
			37	EPS QoS not accepted
			38	Network failure
			39	CS domain temporarily not available
			40	No EPS bearer context activated
			41	Semantic error in the TFT operation
			42	Syntactical error in the TFT operation
			43	Invalid EPS bearer identity
			44	Semantic errors in packet filter(s)
			45	Syntactical error in packet filter(s)
			46	EPS bearer context without TFT already activated
			47	PTI mismatch
			49	Last PDN disconnection not allowed
			50	PDN type IPv4 only allowed
			51	PDN type IPv6 only allowed
			52	Single address bearers only allowed
			53	ESM information not received
			54	PDN connection does not exist
			55	Multiple PDN connections for a given APN not allowed
			56	Collision with network initiated request
			59	Unsupported QCI value
			81	Invalid PTI value
			95	Semantically incorrect message
			96	Invalid mandatory information
			97	Message type non-existent or not implemented
			98	Message type not compatible with protocol state
			99	Information element non-existent or not implemented
			100	Conditional IE error
			101	Message not compatible with protocol state
			111	Protocol error, unspecified
			112	APN restriction value incompatible with active EPS bearer context

Hi Tyberry,

any evolution regarding 4G smartphones signaling issues?

I'm trying to focus more less on the same thing, what should be the impact of the chatty apps in a 4g environment, and what should be the best approach (what link should be monitored, S1 mme? , Sgi ? ) the load caused by this kind of apps will be mainly signalling? lot´s of questions

anyone would like to comment
thanks