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

相关文章

Java中 instanceof 的用法详细介绍

《Java中instanceof的用法详细介绍》在Java中,instanceof是一个二元运算符(类型比较操作符),用于检查一个对象是否是某个特定类、接口的实例,或者是否是其子类的实例,这篇文章... 目录引言基本语法基本作用1. 检查对象是否是指定类的实例2. 检查对象是否是子类的实例3. 检查对象是否

Spring Boot Controller处理HTTP请求体的方法

《SpringBootController处理HTTP请求体的方法》SpringBoot提供了强大的机制来处理不同Content-Type​的HTTP请求体,这主要依赖于HttpMessageCo... 目录一、核心机制:HttpMessageConverter​二、按Content-Type​处理详解1.

一文详解如何在Vue3中封装API请求

《一文详解如何在Vue3中封装API请求》在现代前端开发中,API请求是不可避免的一部分,尤其是与后端交互时,下面我们来看看如何在Vue3项目中封装API请求,让你在实现功能时更加高效吧... 目录为什么要封装API请求1. vue 3项目结构2. 安装axIOS3. 创建API封装模块4. 封装API请求

什么是ReFS 文件系统? ntfs和refs的优缺点区别介绍

《什么是ReFS文件系统?ntfs和refs的优缺点区别介绍》最近有用户在Win11Insider的安装界面中发现,可以使用ReFS来格式化硬盘,这是不是意味着,ReFS有望在未来成为W... 数十年以来,Windows 系统一直将 NTFS 作为「内置硬盘」的默认文件系统。不过近些年来,微软还在研发一款名

C#使用StackExchange.Redis实现分布式锁的两种方式介绍

《C#使用StackExchange.Redis实现分布式锁的两种方式介绍》分布式锁在集群的架构中发挥着重要的作用,:本文主要介绍C#使用StackExchange.Redis实现分布式锁的... 目录自定义分布式锁获取锁释放锁自动续期StackExchange.Redis分布式锁获取锁释放锁自动续期分布式

SpringBoot请求参数接收控制指南分享

《SpringBoot请求参数接收控制指南分享》:本文主要介绍SpringBoot请求参数接收控制指南,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录Spring Boot 请求参数接收控制指南1. 概述2. 有注解时参数接收方式对比3. 无注解时接收参数默认位置

SpringBoot基于配置实现短信服务策略的动态切换

《SpringBoot基于配置实现短信服务策略的动态切换》这篇文章主要为大家详细介绍了SpringBoot在接入多个短信服务商(如阿里云、腾讯云、华为云)后,如何根据配置或环境切换使用不同的服务商,需... 目录目标功能示例配置(application.yml)配置类绑定短信发送策略接口示例:阿里云 & 腾

Spring 请求之传递 JSON 数据的操作方法

《Spring请求之传递JSON数据的操作方法》JSON就是一种数据格式,有自己的格式和语法,使用文本表示一个对象或数组的信息,因此JSON本质是字符串,主要负责在不同的语言中数据传递和交换,这... 目录jsON 概念JSON 语法JSON 的语法JSON 的两种结构JSON 字符串和 Java 对象互转

redis过期key的删除策略介绍

《redis过期key的删除策略介绍》:本文主要介绍redis过期key的删除策略,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录第一种策略:被动删除第二种策略:定期删除第三种策略:强制删除关于big key的清理UNLINK命令FLUSHALL/FLUSHDB命

springboot项目如何开启https服务

《springboot项目如何开启https服务》:本文主要介绍springboot项目如何开启https服务方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录springboot项目开启https服务1. 生成SSL证书密钥库使用keytool生成自签名证书将