80 likes | 161 Views
Title: Access Overload Class for M2M. Source: Contact : yfang@zteusa.com , lu.ting , yu.yuanfang , zhao.xiaowu@zte.com.cn. Abstract: This contribution is to update C22 -20120313-003. Recommendation: Review and Adopt. Background. This contribution is to update C22 -20120313-003.
E N D
Title: Access Overload Class for M2M Source: Contact : yfang@zteusa.com, lu.ting, yu.yuanfang, zhao.xiaowu@zte.com.cn Abstract:This contribution is to update C22-20120313-003. Recommendation:Review and Adopt
Background • This contribution is to update C22-20120313-003
Proposal • Separate ACCOLC between M2M and non-M2M • ACCOLCs for M2M and ACCOLCp for non-M2M • If M2M_TYPEs,p= 1, the MS shall set ACCOLCs as follows
Proposal • Separate Persistence between M2M and non-M2M • If M2M_TYPEs,p = 1, the device shall follow the M2M_PSIST values in the GAPMif they are included. • Otherwise, the device shall follow the existing persistence values in APM for access channel attempt control and values in EAPM for enhanced access channel attempt control.
Proposal • Persistence in GAPM
Proposal • Separate Redirection between M2M and non_M2M • In the redirection messages (GSRDM, EGSRDM), add a new field of REDIRECT_M2M_ACCOLC. • For the device with M2M_TYPEs,p = 1,it shall refer the new REDIRECT_M2M_ACCOLC field if it is included. • Otherwise, it shall refer the existing REDIRECT_ACCOLC field.
Proposal • ACCOLC for M2M in GSRDM
Proposal • ACCOLC for M2M in EGSRDM