关于身份认证和鉴权过程

关于身份认证和鉴权过程开机信令流程开机信令流程一个典型的开机信令流程中包含接入层RRC的信令和非接入层EMM,ESM的信令。在第一部分RRC连接建立和UE能力上报(可选流程)后进入NAS层的信令交互。NAS信令交互顺序如下:身份认证(identity request<->identity response)这一步为可选流程,只有在attach request中提供的UE...
摘要由CSDN通过智能技术生成

开机信令流程

在这里插入图片描述
一个典型的开机信令流程中包含接入层RRC的信令和非接入层EMM,ESM的信令。
在第一部分RRC连接建立和UE能力上报(可选流程)后进入NAS层的信令交互。
NAS信令交互顺序如下:

  1. 身份认证(identity request<->identity response)
    这一步为可选流程,只有在attach request中提供的UE身份标识无法被网络识别时,网络才会触发这一流程。当然,在其他需要UE身份认证的情景下也会触发这一流程。
  2. 鉴权
    这个过程中利用usim中的K值和算法完成与网络测K值和算法的认证计算过程并生成后续加密和完整性保护锁需要的秘钥。
  3. NAS层的安全命令流程
    这一步负责协商NAS加密和完整性保护的算法
  4. ESM信息请求流程
    这一步根据PDN request中的esm info trans flag是否设置而触发,非必选
  5. RRC安全命令流程
    这一步负责协商AS(PDCP)所用的加密算法
  6. 注册接收,EPS承载请求
  7. EPS承载接收,连接建立完成

总结:

身份认证流程应该在鉴权流程之前,鉴权在安全命令流程之前,因为他们之间有依赖关系

重要消息内容举例

LTE NAS EMM Plain OTA Outgoing Message – Attach request Msg(含PDN request)

Subscription ID = 1
pkt_version = 1 (0x1)
rel_number = 9 (0x9)
rel_version_major = 5 (0x5)
rel_version_minor = 0 (0x0)
security_header_or_skip_ind = 0 (0x0)
prot_disc = 7 (0x7) (EPS mobility management messages)
msg_type = 65 (0x41) (Attach request)
lte_emm_msg
emm_attach_request
tsc = 0 (0x0) (cached sec context)
nas_key_set_id = 3 (0x3)
att_type = 2 (0x2) (combined EPS/IMSI attach)
eps_mob_id
id_type = 6 (0x6) (GUTI)
odd_even_ind = 0 (0x0)
Guti_1111 = 15 (0xf)
mcc_1 = 2 (0x2)
mcc_2 = 2 (0x2)
mcc_3 = 8 (0x8)
mnc_3 = 15 (0xf)
mnc_1 = 0 (0x0)
mnc_2 = 2 (0x2)
MME_group_id = 32770 (0x8002)
MME_code = 24 (0x18)
m_tmsi = 3254548600 (0xc1fc7878)
ue_netwk_cap
EEA0 = 1 (0x1)
EEA1_128 = 1 (0x1)
EEA2_128 = 1 (0x1)
EEA3_128 = 1 (0x1)
EEA4 = 0 (0x0)
EEA5 = 0 (0x0)
EEA6 = 0 (0x0)
EEA7 = 0 (0x0)
EIA0 = 0 (0x0)
EIA1_128 = 1 (0x1)
EIA2_128 = 1 (0x1)
EIA3_128 = 1 (0x1)
EIA4 = 0 (0x0)
EIA5 = 0 (0x0)
EIA6 = 0 (0x0)
EIA7 = 0 (0x0)
oct5_incl = 1 (0x1)
UEA0 = 1 (0x1)
UEA1 = 1 (0x1)
UEA2 = 0 (0x0)
UEA3 = 0 (0x0)
UEA4 = 0 (0x0)
UEA5 = 0 (0x0)
UEA6 = 0 (0x0)
UEA7 = 0 (0x0)
oct6_incl = 1 (0x1)
UCS2 = 0 (0x0)
UIA1 = 1 (0x1)
UIA2 = 0 (0x0)
UIA3 = 0 (0x0)
UIA4 = 0 (0x0)
UIA5 = 0 (0x0)
UIA6 = 0 (0x0)
UIA7 = 0 (0x0)
oct7_incl = 1 (0x1)
ProSedd = 0 (0x0)
ProSe = 0 (0x0)
H_245_ASH = 0 (0x0)
ACC_CSFB = 1 (0x1)
LPP = 1 (0x1)
LCS = 0 (0x0)
vcc_1xsr = 0 (0x0)
NF = 1 (0x1)
oct8_incl = 1 (0x1)
ePCO = 0 (0x0)
HC_CPCIoT = 0 (0x0)
ERwoPDN = 0 (0x0)
S1_Udata = 0 (0x0)
UPCIoT = 0 (0x0)
CPCIoT = 0 (0x0)
Prose_Relay = 0 (0x0)
Prose_dc = 0 (0x0)
oct9_incl = 1 (0x1)
bearers = 0 (0x0)
SGC = 0 (0x0)
N1Mode = 0 (0x0)
DCNR = 1 (0x1)
Cp_Backoff = 0 (0x0)
Restric_IEC = 0 (0x0)
V2X_PCS = 0 (0x0)
multiDRB = 0 (0x0)
oct10_incl = 0 (0x0)
oct11_incl = 0 (0x0)
oct12_incl = 0 (0x0)
oct13_incl = 0 (0x0)
oct14_incl = 0 (0x0)
oct15_incl = 0 (0x0)
esm_msg_container
eps_bearer_id_or_skip_id = 0 (0x0)
prot_disc = 2 (0x2) (EPS session management messages)
trans_id = 13 (0xd)
msg_type = 208 (0xd0) (PDN connectivity request)
lte_esm_msg
pdn_connectivity_req
pdn_type = 3 (0x3) (Ipv4v6)
req_type = 1 (0x1) (initial request)
info_trans_flag_incl = 1 (0x1)
esm_info_trans_flag = 1 (0x1)
access_pt_name_incl = 0 (0x0)
prot_config_incl = 1 (0x1)
prot_config
ext = 1 (0x1)
conf_prot = 0 (0x0)
num_recs = 5 (0x5)
sm_prot[0]
protocol_id = 32801 (0x8021) (IPCP)
prot_len = 16 (0x10)
ipcp_prot
ipcp_prot_id = 1 (0x1) (CONF_REQ)
identifier = 0 (0x0)
rfc1332_conf_req
num_options = 2 (0x2)
conf_options[0]
type = 129 (0x81)
rfc1877_primary_dns_server_add
length = 6 (0x6)
ip_addr = 0 (0x0) (0.0.0.0)
conf_options[1]
type = 131 (0x83)
rfc1877_sec_dns_server_add
length = 6 (0x6)
ip_addr = 0 (0x0) (0.0.0.0)
sm_prot[1]
protocol_id = 13 (0xd) (DNS Server IPv4 Address Requestt)
prot_len = 0 (0x0)
sm_prot[2]
protocol_id = 3 (0x3) (DNS Server IPv6 Addr Req)
prot_len = 0 (0x0)
sm_prot[3]
protocol_id = 10 (0xa) (IP address allocation via NAS signalling)
prot_len = 0 (0x0)
sm_prot[4]
protocol_id = 5 (0x5) (NWK Req Bearer Control indicator)
prot_len = 0 (0x0)
num_recs2 = 2 (0x2)
sm_container[0]
container_id = 16 (0x10) (Ipv4 Link MTU Request)
container_len = 0 (0x0)
sm_container[1]
container_id = 17 (0x11) (MS support of Local address in TFT indicator)
container_len = 0 (0x0)
dev_properties_incl = 0 (0x0)
nbifom_incl = 0 (0x0)
header_compression_config_inclu = 0 (0x0)
ext_prot_config_incl = 0 (0x0)
p_tmsi_sig_incl = 0 (0x0)
add_guti_incl = 0 (0x0)
reg_tai_incl = 1 (0x1)
tracking_area_id
mcc_mnc
mcc_1 = 2 (0x2)
mcc_2 = 2 (0x2)
mcc_3 = 8 (0x8)
mnc_3 = 15 (0xf)
mnc_1 = 0 (0x0)
mnc_2 = 2 (0x2)
tracking_area_id = 40000 (0x9c40)
drx_params_incl = 1 (0x1)
drx_params
split_pg_cycle_code = 10 (0xa)
cycle_len_coeff = 0 (0x0)
split_on_ccch = 0 (0x0)
non_drx_timer = 0 (0x0)
ms_netwk_cap_incl = 1 (0x1)
ms_netwk_cap
length = 4 (0x4)
r99 = 1 (0x1)
GEA1 bits
GEA/1 = 1 (0x1)
SM capabilities via dedicated channels = 1 (0x1)
SM capabilities via GPRS channels = 1 (0x1)
UCS2 support = 0 (0x0)
SS Screening Indicator = 1 (0x1)
SoLSA Capability = 0 (0x0)
Revision level indicator = 1 (0x1)
PFC feature mode = 1 (0x1)
Extended GEA bits
GEA/2 = 1 (0x1)
GEA/3 = 1 (0x1)
GEA/4 = 0 (0x0)
GEA/5 = 0 (0x0)
GEA/6 = 0 (0x0)
GEA/7 = 0 (0x0)
LCS VA capability = 0 (0x0)
PS inter-RAT HO from GERAN to UTRAN Iu mode capability = 0 (0x0)
PS inter-RAT HO from GERAN to E-UTRAN S1 mode capability = 0 (0x0)
EMM Combined procedures Capability = 1 (0x1)
ISR support = 1 (0x1)
SRVCC to GERAN/UTRAN capability = 1 (0x1)
EPC capability = 1 (0x1)
NF capability = 1 (0x1)
GERAN network sharing capability = 0 (0x0)
User plane integrity protection support = 0 (0x0)
GIA/4 = 0 (0x0)
GIA/5 = 0 (0x0)
GIA/6 = 0 (0x0)
GIA/7 = 0 (0x0)
ePCO IE indicator = 0 (0x0)
Restriction on use of enhanced coverage capability = 0 (0x0)
Dual connectivity of E-UTRA with NR capability = 1 (0x1)
spare_bits0_count = 0 (0x0)
old_loc_area_id_incl = 1 (0x1)
old_loc_area_id
mcc_1 = 2 (0x2)
mcc_2 = 2 (0x2)
mcc_3 = 8 (0x8)
mnc_3 = 15 (0xf)
mnc_1 = 0 (0x0)
mnc_2 = 2 (0x2)
loc_area_code = 20000 (0x4e20)
tmsi_stat

  • 1
    点赞
  • 35
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值