ATTACH、服务请求值及错误码介绍

2023-11-23 20:20

本文主要是介绍ATTACH、服务请求值及错误码介绍,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

#**1、ATTACH附着相关取值

##1)ATTACH REQUEST消息中“EPS attach type”
8 7 6 5 4 3 2 1
EPS attach type IEI 0
Spare EPS attach type value octet 1

EPS attach type value (octet 1)
Bits
3 2 1
0 0 1 1:EPS attach
0 1 0 2:combined EPS/IMSI attach
0 1 1 3:EPS RLOS attach (NOTE)
1 1 0 6:EPS emergency attach
1 1 1 7:reserved

1代表EPS 附着、2代表联合附着。。。

##2)ATTACH ACCEPT消息中EPS attach result value的取值
EPS attach result value (octet 1)
Bits
3 2 1
0 0 1 EPS only
0 1 0 combined EPS/IMSI attach

All other values are reserved.

Bit 4 of octet 1 is spare and shall be coded as zero.

##3)EMM的具体原因值的编码规则
Cause value (octet 2)

Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 1 0 IMSI unknown in HSS
0 0 0 0 0 0 1 1 Illegal UE
0 0 0 0 0 1 0 1 IMEI not accepted
0 0 0 0 0 1 1 0 Illegal ME
0 0 0 0 0 1 1 1 EPS services not allowed
0 0 0 0 1 0 0 0 EPS services and non-EPS services not allowed
0 0 0 0 1 0 0 1 UE identity cannot be derived by the network
0 0 0 0 1 0 1 0 Implicitly detached
0 0 0 0 1 0 1 1 PLMN not allowed
0 0 0 0 1 1 0 0 Tracking Area not allowed
0 0 0 0 1 1 0 1 Roaming not allowed in this tracking area
0 0 0 0 1 1 1 0 EPS services not allowed in this PLMN
0 0 0 0 1 1 1 1 No Suitable Cells In tracking area
0 0 0 1 0 0 0 0 MSC temporarily not reachable
0 0 0 1 0 0 0 1 Network failure
0 0 0 1 0 0 1 0 CS domain not available
0 0 0 1 0 0 1 1 ESM failure
0 0 0 1 0 1 0 0 MAC failure
0 0 0 1 0 1 0 1 Synch failure
0 0 0 1 0 1 1 0 Congestion
0 0 0 1 0 1 1 1 UE security capabilities mismatch
0 0 0 1 1 0 0 0 Security mode rejected, unspecified
0 0 0 1 1 0 0 1 Not authorized for this CSG
0 0 0 1 1 0 1 0 Non-EPS authentication unacceptable
0 0 0 1 1 1 1 1 Redirection to 5GCN required
0 0 1 0 0 0 1 1 Requested service option not authorized in this PLMN
0 0 1 0 0 1 1 1 CS service temporarily not available
0 0 1 0 1 0 0 0 No EPS bearer context activated
0 0 1 0 1 0 1 0 Severe network failure
0 1 0 0 1 1 1 0 PLMN not allowed to operate at the present UE location
0 1 0 1 1 1 1 1 Semantically incorrect message
0 1 1 0 0 0 0 0 Invalid mandatory information
0 1 1 0 0 0 0 1 Message type non-existent or not implemented
0 1 1 0 0 0 1 0 Message type not compatible with the protocol state
0 1 1 0 0 0 1 1 Information element non-existent or not implemented
0 1 1 0 0 1 0 0 Conditional IE error
0 1 1 0 0 1 0 1 Message not compatible with the protocol state
0 1 1 0 1 1 1 1 Protocol error, unspecified

##4)ESM的具体原因值的编码规则
Cause value (octet 2)

Bits
8 7 6 5 4 3 2 1
0 0 0 0 1 0 0 0 Operator Determined Barring
0 0 0 1 1 0 1 0 Insufficient resources
0 0 0 1 1 0 1 1 Missing or unknown APN
0 0 0 1 1 1 0 0 Unknown PDN type
0 0 0 1 1 1 0 1 User authentication or authorization failed
0 0 0 1 1 1 1 0 Request rejected by Serving GW or PDN GW
0 0 0 1 1 1 1 1 Request rejected, unspecified
0 0 1 0 0 0 0 0 Service option not supported
0 0 1 0 0 0 0 1 Requested service option not subscribed
0 0 1 0 0 0 1 0 Service option temporarily out of order
0 0 1 0 0 0 1 1 PTI already in use
0 0 1 0 0 1 0 0 Regular deactivation
0 0 1 0 0 1 0 1 EPS QoS not accepted
0 0 1 0 0 1 1 0 Network failure
0 0 1 0 0 1 1 1 Reactivation requested
0 0 1 0 1 0 0 1 Semantic error in the TFT operation
0 0 1 0 1 0 1 0 Syntactical error in the TFT operation
0 0 1 0 1 0 1 1 Invalid EPS bearer identity
0 0 1 0 1 1 0 0 Semantic errors in packet filter(s)
0 0 1 0 1 1 0 1 Syntactical errors in packet filter(s)
0 0 1 0 1 1 1 0 Unused (see NOTE 2)
0 0 1 0 1 1 1 1 PTI mismatch
0 0 1 1 0 0 0 1 Last PDN disconnection not allowed
0 0 1 1 0 0 1 0 PDN type IPv4 only allowed
0 0 1 1 0 0 1 1 PDN type IPv6 only allowed
0 0 1 1 0 1 0 0 Single address bearers only allowed
0 0 1 1 0 1 0 1 ESM information not received
0 0 1 1 0 1 1 0 PDN connection does not exist
0 0 1 1 0 1 1 1 Multiple PDN connections for a given APN not allowed
0 0 1 1 1 0 0 0 Collision with network initiated request
0 0 1 1 1 0 0 1 PDN type IPv4v6 only allowed
0 0 1 1 1 0 1 0 PDN type non IP only allowed
0 0 1 1 1 0 1 1 Unsupported QCI value
0 0 1 1 1 1 0 0 Bearer handling not supported
0 0 1 1 1 1 0 1 PDN type Ethernet only allowed
0 1 0 0 0 0 0 1 Maximum number of EPS bearers reached
0 1 0 0 0 0 1 0 Requested APN not supported in current RAT and PLMN combination
0 1 0 1 0 0 0 1 Invalid PTI value
0 1 0 1 1 1 1 1 Semantically incorrect message
0 1 1 0 0 0 0 0 Invalid mandatory information
0 1 1 0 0 0 0 1 Message type non-existent or not implemented
0 1 1 0 0 0 1 0 Message type not compatible with the protocol state
0 1 1 0 0 0 1 1 Information element non-existent or not implemented
0 1 1 0 0 1 0 0 Conditional IE error
0 1 1 0 0 1 0 1 Message not compatible with the protocol state
0 1 1 0 1 1 1 1 Protocol error, unspecified
0 1 1 1 0 0 0 0 APN restriction value incompatible with active EPS bearer context
0 1 1 1 0 0 0 1 Multiple accesses to a PDN connection not allowed

##5)S1AP错误码
在这里插入图片描述

#2、EXTENDED SERVICE REQUEST消息中Service type value的取值

8 7 6 5 4 3 2 1
Service type
IEI Service type value octet 1
Service type value (octet 1)

Service type value
Bits
4 3 2 1
0 0 0 0 mobile originating CS fallback or 1xCS fallback
0 0 0 1 mobile terminating CS fallback or 1xCS fallback
0 0 1 0 mobile originating CS fallback emergency call or 1xCS fallback emergency call
0 0 1 1 unused; shall be interpreted as “mobile originating CS fallback or 1xCS fallback”, if received by the network
0 1 0 0 unused; shall be interpreted as “mobile originating CS fallback or 1xCS fallback”, if received by the network
1 0 0 0 packet services via S1
1 0 0 1 unused; shall be interpreted as “packet services via S1”, if received by the network
1 0 1 0 unused; shall be interpreted as “packet services via S1”, if received by the network
1 0 1 1 unused; shall be interpreted as “packet services via S1”, if received by the network

#3、TRACKING AREA UPDATE REQUEST消息中“EPS update type取值
8 7 6 5 4 3 2 1
EPS update type
IEI “Active” flag EPS update type
Value octet 1

EPS update type value (octet 1, bit 1 to 3)

Bits

3 2 1
0 0 0 0:TA updating
0 0 1 1:combined TA/LA updating
0 1 0 2:combined TA/LA updating with IMSI attach
0 1 1 3:periodic updating
1 0 0 4:unused; shall be interpreted as “TA updating”, if received by the network.
1 0 1 5:unused; shall be interpreted as “TA updating”, if received by the network.

“Active” flag (octet 1, bit 4)
Bit
4
0 No bearer establishment requested
1 Bearer establishment requested

#4、DETACH REQUEST消息中DETACH REQUEST消息中Type of detach及Switch off的取值
Type of detach (octet 1)
UE>网络
Bits
3 2 1
0 0 1 EPS detach
0 1 0 IMSI detach
0 1 1 combined EPS/IMSI detach
1 1 0 reserved
1 1 1 reserved

网络>UE:
Bits
3 2 1
0 0 1 re-attach required
0 1 0 re-attach not required
0 1 1 IMSI detach
1 1 0 reserved
1 1 1 reserved

Switch off (octet 1)

UE>网络:
Bit
4
0 normal detach
1 switch off

这篇关于ATTACH、服务请求值及错误码介绍的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/420486

相关文章

Nginx中配置使用非默认80端口进行服务的完整指南

《Nginx中配置使用非默认80端口进行服务的完整指南》在实际生产环境中,我们经常需要将Nginx配置在其他端口上运行,本文将详细介绍如何在Nginx中配置使用非默认端口进行服务,希望对大家有所帮助... 目录一、为什么需要使用非默认端口二、配置Nginx使用非默认端口的基本方法2.1 修改listen指令

SysMain服务可以关吗? 解决SysMain服务导致的高CPU使用率问题

《SysMain服务可以关吗?解决SysMain服务导致的高CPU使用率问题》SysMain服务是超级预读取,该服务会记录您打开应用程序的模式,并预先将它们加载到内存中以节省时间,但它可能占用大量... 在使用电脑的过程中,CPU使用率居高不下是许多用户都遇到过的问题,其中名为SysMain的服务往往是罪魁

Springboot项目构建时各种依赖详细介绍与依赖关系说明详解

《Springboot项目构建时各种依赖详细介绍与依赖关系说明详解》SpringBoot通过spring-boot-dependencies统一依赖版本管理,spring-boot-starter-w... 目录一、spring-boot-dependencies1.简介2. 内容概览3.核心内容结构4.

解决若依微服务框架启动报错的问题

《解决若依微服务框架启动报错的问题》Invalidboundstatement错误通常由MyBatis映射文件未正确加载或Nacos配置未读取导致,需检查XML的namespace与方法ID是否匹配,... 目录ruoyi-system模块报错报错详情nacos文件目录总结ruoyi-systnGLNYpe

setsid 命令工作原理和使用案例介绍

《setsid命令工作原理和使用案例介绍》setsid命令在Linux中创建独立会话,使进程脱离终端运行,适用于守护进程和后台任务,通过重定向输出和确保权限,可有效管理长时间运行的进程,本文给大家介... 目录setsid 命令介绍和使用案例基本介绍基本语法主要特点命令参数使用案例1. 在后台运行命令2.

Nginx进行平滑升级的实战指南(不中断服务版本更新)

《Nginx进行平滑升级的实战指南(不中断服务版本更新)》Nginx的平滑升级(也称为热升级)是一种在不停止服务的情况下更新Nginx版本或添加模块的方法,这种升级方式确保了服务的高可用性,避免了因升... 目录一.下载并编译新版Nginx1.下载解压2.编译二.替换可执行文件,并平滑升级1.替换可执行文件

MySQL常用字符串函数示例和场景介绍

《MySQL常用字符串函数示例和场景介绍》MySQL提供了丰富的字符串函数帮助我们高效地对字符串进行处理、转换和分析,本文我将全面且深入地介绍MySQL常用的字符串函数,并结合具体示例和场景,帮你熟练... 目录一、字符串函数概述1.1 字符串函数的作用1.2 字符串函数分类二、字符串长度与统计函数2.1

python运用requests模拟浏览器发送请求过程

《python运用requests模拟浏览器发送请求过程》模拟浏览器请求可选用requests处理静态内容,selenium应对动态页面,playwright支持高级自动化,设置代理和超时参数,根据需... 目录使用requests库模拟浏览器请求使用selenium自动化浏览器操作使用playwright

SpringBoot监控API请求耗时的6中解决解决方案

《SpringBoot监控API请求耗时的6中解决解决方案》本文介绍SpringBoot中记录API请求耗时的6种方案,包括手动埋点、AOP切面、拦截器、Filter、事件监听、Micrometer+... 目录1. 简介2.实战案例2.1 手动记录2.2 自定义AOP记录2.3 拦截器技术2.4 使用Fi

Spring Boot 与微服务入门实战详细总结

《SpringBoot与微服务入门实战详细总结》本文讲解SpringBoot框架的核心特性如快速构建、自动配置、零XML与微服务架构的定义、演进及优缺点,涵盖开发环境准备和HelloWorld实战... 目录一、Spring Boot 核心概述二、微服务架构详解1. 微服务的定义与演进2. 微服务的优缺点三