S1AP协议 - 管理信令整理

于 2024-11-04 16:01:52 发布
阅读量2.2k 收藏 42
点赞数 32
分类专栏： 3GPP 协议总结 文章标签： 网络协议 信息与通信
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_25636501/article/details/143479152
版权

功能概述

  • 重置功能（Reset）：确保S1接口能回到初始化状态。
  • 错误指示功能（Error Indication）：在没有定义失败消息的情况下，允许进行适当的错误报告和处理。
  • 过载功能（overload）：用于指示S1接口控制面的负载情况。
  • 负载均衡（Load Balancing）：确保MME池区域内的MME负载均衡。
  • S1设置功能（S1 Setup）：用于初始化S1接口设置以提供配置信息。
  • 配置更新功能：用于更新eNB和MME在S1接口上正确互操作所需要的应用级配置数据。

s1 setup

概述

S1 Setup 流程的目的是交换eNB和MME在S1接口上正确互操作所需要的应用级数据。此过程用是在传输网络层（TNL）关联变为可操作状态（即SCTP连接建立成功）后触发的第一个S1AP协议流程。该过程使用的信令为非UE关联信令。

这个过程会清除两个节点中任何现有的应用级配置数据，并用接收到的数据替换，同时在eNB结点清理MME过载状态信息。如果eNB和MME没有同意保留用户上下文，此过程还会像Reset流程那样重新初始化E-UTRAN S1AP UE相关的上下文，并清除两个结点中所有的相关信令连接。如果发起S1 Setup流程的eNB支持封闭用户组（CSG）小区，该流程应该上报所支持的封闭小区的ID。（CSG ID）

Elementary ProcedureInitiating MessageSuccessful Outcome/ Response messageUnsuccessful Outcome/ Response message
S1 setupS1 SETUP REQUESTS1 SETUP RESPONSES1 SETUP FAILURE

id-S1setup ------------------------------- ProcedureCode ::= 17

流程

成功场景

在这里插入图片描述

The eNB initiates the procedure by sending a S1 SETUP REQUEST message including the appropriate data to the MME. The MME responds with a S1 SETUP RESPONSE message including the appropriate data.
The exchanged data shall be stored in respective node and used for the duration of the TNL association. When this procedure is finished, the S1 interface is operational and other S1 messages can be exchanged.
If the eNB initiating the S1 SETUP procedure supports one (or more) CSG cell(s), the S1 SETUP REQUEST message shall contain the CSG ID(s) of the supported CSG(s).
If the S1 SETUP REQUEST message contains the eNB Name IE the MME may use this IE as a human readable name of the eNB.
If the S1 SETUP RESPONSE message contains the MME Name IE the eNB may use this IE as a human readable name of the MME.
If the MME Relay Support Indicator IE is included in the S1 SETUP RESPONSE message, the eNB shall consider this information when selecting an appropriate MME for the Relay Node.
If the UE Retention Information IE set to “ues-retained“ was included in the S1 SETUP REQUEST message, then the MME may accept the proposal to retain the existing UE related contexts and signalling connections by including the UE Retention Information IE set to “ues-retained“ in the S1 SETUP RESPONSE message.
If the NB-IoT Default Paging DRX IE is included in the S1 SETUP REQUEST message, the MME will take it into account as specified in TS36.300 [14].
If the Connected en-gNB List IE is included in the S1 SETUP REQUEST message, the MME shall take it into account as specified in TS 36.300 [14].
If the S1 SETUP RESPONSE message contains the ServedDCNs IE then the eNB shall, if supported, use it as defined in TS 23.401 [11].

失败场景

在这里插入图片描述

If the MME cannot accept the setup, it should respond with a S1 SETUP FAILURE and appropriate cause value.
If the S1 SETUP FAILURE message includes the Time To Wait IE, the eNB shall wait at least for the indicated time before reinitiating the S1 setup towards the same MME.

异常情况

If the eNB initiates the procedure by sending a S1 SETUP REQUEST message including the PLMN Identity IEs and none of the PLMNs provided by the eNB is identified by the MME, then the MME shall reject the eNB S1 Setup Request procedure with the appropriate cause value, e.g., “Unknown PLMN”.

信元

S1 SETUP REQUEST

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
Global eNB IDMYESreject
eNB NameOYESignore
Supported TAs1…256Supported TAs in the eNBGLOBALreject
#TACMBroadcast TAC-
#Broadcast PLMNs Type1…6Broadcast PLMNs-
##PLMN IdentityM
#RAT-TypeORAT-Type associated with the TAC of the indicated PLMN(s).YESreject
Default Paging DRXMYESignore
CSG Id List0…1GLOBALreject
#CSG Id1…256
UE Retention InformationOYESignore
NB-IoT Default Paging DRXOYESignore
Connected en-gNB List0…256GLOBALignore
#en-gNB IDMBIT STRING(SIZE(22.32))
#Supported TAs1…256-
##Configured TACMTAC-
##Broadcast PLMNs1…6Broadcast PLMNs-
###PLMN IdentityM
-- **************************************************************
--
-- S1 Setup Request
--
-- **************************************************************

S1SetupRequest ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {S1SetupRequestIEs} },
    ...
}

S1SetupRequestIEs S1AP-PROTOCOL-IES ::= {
    { ID id-Global-ENB-ID               CRITICALITY reject  TYPE Global-ENB-ID              PRESENCE mandatory}|
    { ID id-eNBname                     CRITICALITY ignore  TYPE ENBname                    PRESENCE optional}|
    { ID id-SupportedTAs                CRITICALITY reject  TYPE SupportedTAs               PRESENCE mandatory}|
    { ID id-DefaultPagingDRX            CRITICALITY ignore  TYPE PagingDRX                  PRESENCE mandatory}|
    { ID id-CSG-IdList                  CRITICALITY reject  TYPE CSG-IdList                 PRESENCE optional}|
    { ID id-UE-RetentionInformation     CRITICALITY ignore  TYPE UE-RetentionInformation    PRESENCE optional}|
    { ID id-NB-IoT-DefaultPagingDRX     CRITICALITY ignore  TYPE NB-IoT-DefaultPagingDRX    PRESENCE optional}|
    { ID id-ConnectedengNBList          CRITICALITY ignore  TYPE ConnectedengNBList         PRESENCE optional},
    ...
}

id-Global-ENB-ID ProtocolIE-ID ::= 59
id-eNBname ProtocolIE-ID ::= 60
id-SupportedTAs ProtocolIE-ID ::= 64
id-DefaultPagingDRX ProtocolIE-ID ::= 137
id-CSG-IdList ProtocolIE-ID ::= 128
id-UE-RetentionInformation ProtocolIE-ID ::= 228
id-NB-IoT-DefaultPagingDRX ProtocolIE-ID ::= 234
id-ConnectedengNBList ProtocolIE-ID ::= 291

Global-ENB-ID
IE/Group NamePRangeSemantics description
PLMN IdentityM
CHOICE eNB IDM
#Macro eNB ID
##Macri eNB IDMEqual to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE of each cell served by the eNB.
#Home eNB ID
##Home enb IDMEqual to the Cell Identity IE contained in the E-UTRAN CGI IE of the cell served by the eNB.
#Short Macro eNB ID
##Short Macro eNB IDMEqual to the 18 leftmost bits of the Cell Identity IE (see subclause 9.2.1.38) of each cell served by the eNB.
#Long Macro eNB ID
##Long Macro eNB IDMEqual to the 21 leftmost bits of the Cell Identity IE (see subclause 9.2.1.38) of each cell served by the eNB.
Global-ENB-ID ::= SEQUENCE {
	pLMNidentity			PLMNidentity,
	eNB-ID					ENB-ID,
	iE-Extensions			ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} }		OPTIONAL,
	...
}

PLMNidentity 				::= TBCD-STRING 

ENB-ID ::= CHOICE {
	macroENB-ID			BIT STRING (SIZE(20)),
	homeENB-ID			BIT STRING (SIZE(28)),
	... ,
	short-macroENB-ID 	BIT STRING (SIZE(18)),
	long-macroENB-ID		BIT STRING (SIZE(21))
}

备注：PLMN Identity：3字节长度。
编码方式：数字 0 到 9, 编码为 0000 to 1001,1111用作填充数字, 每个字节两位数字,

  • 第n个字节的第4到第1位对数字2n-1进行编码；
  • 第n个字节的第8到第5位对数字2n进行编码；

The PLMN identity consists of 3 digits from MCC followed by either
PLMN标识由MCC的三位数字以及MNC的2个数字或者MNC的3个数字组成
因此编码例子如下

MCC 460 MNC 30
01100100 11110000 00000011 ->64f003
MCC 461 MNC 123
01100100 0001000100110010 ->641132

eNB Name
ENBname ::= PrintableString (SIZE (1..150,...))
SupportedTAs
SupportedTAs ::= SEQUENCE (SIZE(1.. maxnoofTACs)) OF SupportedTAs-Item

maxnoofTACs                             INTEGER ::= 256

SupportedTAs-Item ::=	SEQUENCE  {
	tAC					TAC,
	broadcastPLMNs		BPLMNs,
	iE-Extensions		ProtocolExtensionContainer { {SupportedTAs-Item-ExtIEs} } OPTIONAL,
	...
}

SupportedTAs-Item-ExtIEs S1AP-PROTOCOL-EXTENSION ::= {
	-- Extension for Release 13 to transfer RAT-Type per TAC --
	{ID id-RAT-Type		CRITICALITY reject	EXTENSION RAT-Type		PRESENCE optional},
	...
}

TAC ::= OCTET STRING (SIZE (2))

BPLMNs ::= SEQUENCE (SIZE(1.. maxnoofBPLMNs)) OF PLMNidentity

PLMNidentity 				::= TBCD-STRING

maxnoofBPLMNs							INTEGER ::= 6

RAT-Type ::= ENUMERATED {
	nbiot,
	...
}
DefaultPagingDRX
PagingDRX ::= ENUMERATED {
	v32,
	v64,
	v128,
	v256,
	...
	}

S1 Setup Response

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
MME NameOYESignore
Served GUMMEIs1…8GLOBALreject
#Served PLMNs1…32-
##PLMN IdentityM-
#Served GroupIDs1…65535-
##MME Group IDM-
#Served MMECs1…256-
##MME CodeM-
Relative MME CapacityMYESignore
MME Relay Support IndicatorOYESignore
Criticality DiagnosticsOYESignore
UE Retention InformationOYESignore
Served DCNs0…32GLOBALignore
#Served DCNs ItemsM-
-- **************************************************************
--
-- S1 Setup Response
--
-- **************************************************************

S1SetupResponse ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {S1SetupResponseIEs} },
    ...
}

S1SetupResponseIEs S1AP-PROTOCOL-IES ::= {
    { ID id-MMEname                     CRITICALITY ignore  TYPE MMEname                    PRESENCE optional}|
    { ID id-ServedGUMMEIs               CRITICALITY reject  TYPE ServedGUMMEIs              PRESENCE mandatory}|
    { ID id-RelativeMMECapacity         CRITICALITY ignore  TYPE RelativeMMECapacity        PRESENCE mandatory}|
    { ID id-MMERelaySupportIndicator    CRITICALITY ignore  TYPE MMERelaySupportIndicator   PRESENCE optional}|
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional}|
    { ID id-UE-RetentionInformation     CRITICALITY ignore  TYPE UE-RetentionInformation    PRESENCE optional}|
    { ID id-ServedDCNs                  CRITICALITY ignore  TYPE ServedDCNs                 PRESENCE optional},
    ...
}

id-MMEname ProtocolIE-ID ::= 61
id-ServedGUMMEIs ProtocolIE-ID ::= 105
id-RelativeMMECapacity ProtocolIE-ID ::= 87
id-MMERelaySupportIndicator ProtocolIE-ID ::= 163
id-CriticalityDiagnostics ProtocolIE-ID ::= 58
id-UE-RetentionInformation ProtocolIE-ID ::= 228
id-ServedDCNs ProtocolIE-ID ::= 247

MME Name
MMEname ::= PrintableString (SIZE (1..150,...))
ServedGUMMEIs
ServedGUMMEIs ::= SEQUENCE (SIZE (1.. maxnoofRATs)) OF ServedGUMMEIsItem
maxnoofRATs								INTEGER ::= 8

ServedGUMMEIsItem ::= SEQUENCE {
	servedPLMNs				ServedPLMNs,
	servedGroupIDs			ServedGroupIDs,
	servedMMECs				ServedMMECs,
	iE-Extensions			ProtocolExtensionContainer { {ServedGUMMEIsItem-ExtIEs} }	OPTIONAL,
	...
}

ServedGUMMEIsItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= {
	...
}

ServedGroupIDs ::= SEQUENCE (SIZE(1.. maxnoofGroupIDs)) OF MME-Group-ID
maxnoofGroupIDs							INTEGER ::= 65535
MME-Group-ID	::= OCTET STRING (SIZE (2))

ServedMMECs ::= SEQUENCE (SIZE(1.. maxnoofMMECs)) OF MME-Code
maxnoofMMECs							INTEGER ::= 256
MME-Code		::= OCTET STRING (SIZE (1))

ServedPLMNs ::= SEQUENCE (SIZE(1.. maxnoofPLMNsPerMME)) OF PLMNidentity
maxnoofPLMNsPerMME						INTEGER ::= 32
PLMNidentity 				::= TBCD-STRING
RelativeMMECapacity
RelativeMMECapacity				::= INTEGER (0..255)

S1 Setup Failure

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
CauseMYESignore
Time to WaitOYESignore
Criticality DiagnosticOYESignore
-- **************************************************************
--
-- S1 Setup Failure
--
-- **************************************************************

S1SetupFailure ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container       { {S1SetupFailureIEs} },
	...
}

S1SetupFailureIEs S1AP-PROTOCOL-IES ::= {
	{ ID id-Cause						CRITICALITY ignore	TYPE Cause						PRESENCE mandatory	}|
	{ ID id-TimeToWait					CRITICALITY ignore	TYPE TimeToWait					PRESENCE optional	}|
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore	TYPE CriticalityDiagnostics		PRESENCE optional	},
	...
}

Cause ::= CHOICE {
	radioNetwork		CauseRadioNetwork,
	transport			CauseTransport,
	nas					CauseNas,
	protocol			CauseProtocol,
	misc				CauseMisc,
	...
}

CauseRadioNetwork ::= ENUMERATED {
	unspecified,
	tx2relocoverall-expiry,
	successful-handover,
	release-due-to-eutran-generated-reason,
	handover-cancelled,	
	partial-handover,	
	ho-failure-in-target-EPC-eNB-or-target-system,
	ho-target-not-allowed,
	tS1relocoverall-expiry,
	tS1relocprep-expiry,
	cell-not-available,
	unknown-targetID,
	no-radio-resources-available-in-target-cell,
	unknown-mme-ue-s1ap-id,
	unknown-enb-ue-s1ap-id,
	unknown-pair-ue-s1ap-id,
	handover-desirable-for-radio-reason,
	time-critical-handover,
	resource-optimisation-handover,
	reduce-load-in-serving-cell,
	user-inactivity,
	radio-connection-with-ue-lost,
	load-balancing-tau-required,
	cs-fallback-triggered,
	ue-not-available-for-ps-service,
	radio-resources-not-available,
	failure-in-radio-interface-procedure,
	invalid-qos-combination,
	interrat-redirection,
	interaction-with-other-procedure,
	unknown-E-RAB-ID,
	multiple-E-RAB-ID-instances,
	encryption-and-or-integrity-protection-algorithms-not-supported,
	s1-intra-system-handover-triggered,
	s1-inter-system-handover-triggered,
	x2-handover-triggered,
	...,
	redirection-towards-1xRTT,
	not-supported-QCI-value,
	invalid-CSG-Id,
	release-due-to-pre-emption,
	n26-interface-not-available

}

CauseTransport ::= ENUMERATED {
	transport-resource-unavailable,
	unspecified,
	...
}

CauseNas ::= ENUMERATED {
	normal-release,
	authentication-failure,
	detach,
	unspecified,
	...,
	csg-subscription-expiry
}

CauseProtocol ::= ENUMERATED {
	transfer-syntax-error,
	abstract-syntax-error-reject,
	abstract-syntax-error-ignore-and-notify,
	message-not-compatible-with-receiver-state,
	semantic-error,
	abstract-syntax-error-falsely-constructed-message,
	unspecified,
	...
}

CauseMisc ::= ENUMERATED {
	control-processing-overload,
	not-enough-user-plane-processing-resources,
	hardware-failure,
	om-intervention,
	unspecified,
	unknown-PLMN,
...
}

id-Cause ProtocolIE-ID ::= 2
id-TimeToWait ProtocolIE-ID ::= 65
id-CriticalityDiagnostics ProtocolIE-ID ::= 58

eNB Configuration Update

概述

eNB配置更新流程的目的是更新 eNB 和 MME 在 S1 接口上正确互操作所需的应用层配置数据。该流程不影响已存在的用户上下文。

Elementary ProcedureInitiating MessageSuccessful Outcome/ Response messageUnsuccessful Outcome/ Response message
eNB Configuration UpdateENB CONFIGURATION UPDATEENB CONFIGURATION UPDATE ACKNOWLEDGEENB CONFIGURATION UPDATE FAILURE

id-ENBConfigurationUpdate ProcedureCode ::= 29

流程

成功场景

在这里插入图片描述

The eNB initiates the procedure by sending an ENB CONFIGURATION UPDATE message to the MME including an appropriate set of updated configuration data that it has just taken into operational use. The MME responds with ENB CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If information element(s) is/are not included in the ENB CONFIGURATION UPDATE message, the MME shall interpret that the corresponding configuration data is/are not changed and shall continue to operate the S1 with the existing related configuration data.
If the supported TA(s) is/are to be updated, the whole list of supported TAs, including those that are not to be updated, shall be included in the Supported TAs IE. The MME shall overwrite the whole list of TAs.
If the supported CSG ID(s) is/are to be updated, the whole list of supported CSG IDs, including those that are not to be updated, shall be included in the CSG Id List IE. The MME shall overwrite the whole list of CSG Ids.
If the ENB CONFIGURATION UPDATE message contains the eNB Name IE, the MME may use this IE as a human readable name of the eNB.
If the Default Paging DRX IE is included, the MME shall overwrite any previously stored default paging DRX value for the eNB.
If the NB-IoT Default Paging DRX IE is included in the ENB CONFIGURATION UPDATE message, the MME shall overwrite any previously stored NB-IoT default paging DRX value for the eNB.
If the Connected en-gNB to be Added List IE is included in the ENB CONFIGURATION UPDATE message, the MME shall replace, if applicable, any previously received information for the concerned en-gNBs and take it into account as specified in TS 36.300 [14].
If the Connected en-gNB to be Removed List IE is included in the ENB CONFIGURATION UPDATE message, the MME shall remove any stored information for the concerned en-gNBs.
The updated configuration data shall be stored in both the eNB and the MME and used for the duration of the TNL association or until any further update is triggered by the eNB.
The eNB may initiate a further eNB Configuration Update procedure only after a previous eNB Configuration Update procedure has been completed.

失败场景

在这里插入图片描述

If the MME cannot accept the update, it shall respond with an ENB CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the ENB CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the eNB shall wait at least for the indicated time before reinitiating the ENB Configuration Update procedure towards the same MME. Both nodes shall continue to operate the S1 with their respective configuration data.

异常情况

If the eNB after initiating eNB Configuration Update procedure receives neither an ENB CONFIGURATION UPDATE ACKOWLEDGE nor an ENB CONFIGURATION UPDATE FAILURE message, the eNB may reinitiate a further eNB Configuration Update procedure towards the same MME, provided that the content of the new ENB CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged ENB CONFIGURATION UPDATE message.

信元

ENB CONFIGURATION UPDATE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
eNB NameOYESignore
Supported TAs1…256Supported TAs in the eNBGLOBALreject
#TACMBroadcast TAC-
#Broadcast PLMNs Type1…6Broadcast PLMNs-
##PLMN IdentityM
#RAT-TypeORAT-Type associated with the TAC of the indicated PLMN(s).YESreject
Default Paging DRXMYESignore
CSG Id List0…1GLOBALreject
#CSG Id1…256
UE Retention InformationOYESignore
NB-IoT Default Paging DRXOYESignore
-- **************************************************************
--
-- ENB CONFIGURATION UPDATE ELEMENTARY PROCEDURE
--
-- **************************************************************

-- **************************************************************
--
-- eNB Configuration Update 
--
-- **************************************************************

ENBConfigurationUpdate ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {ENBConfigurationUpdateIEs} },
    ...
}

ENBConfigurationUpdateIEs S1AP-PROTOCOL-IES ::= {
    { ID id-eNBname                     CRITICALITY ignore  TYPE ENBname                    PRESENCE optional}|
    { ID id-SupportedTAs                CRITICALITY reject  TYPE SupportedTAs               PRESENCE optional}|
    { ID id-CSG-IdList                  CRITICALITY reject  TYPE CSG-IdList                 PRESENCE optional}|
    { ID id-DefaultPagingDRX            CRITICALITY ignore  TYPE PagingDRX                  PRESENCE optional}|
    { ID id-NB-IoT-DefaultPagingDRX     CRITICALITY ignore  TYPE NB-IoT-DefaultPagingDRX    PRESENCE optional}|
    { ID id-ConnectedengNBToAddList     CRITICALITY ignore  TYPE ConnectedengNBList         PRESENCE optional}|
    { ID id-ConnectedengNBToRemoveList  CRITICALITY ignore  TYPE ConnectedengNBList         PRESENCE optional},
    ...
}
IE 具体内容参考S1 Setup Request

id-eNBname ProtocolIE-ID ::= 60
id-SupportedTAs ProtocolIE-ID ::= 64
id-DefaultPagingDRX ProtocolIE-ID ::= 137
id-CSG-IdList ProtocolIE-ID ::= 128
id-UE-RetentionInformation ProtocolIE-ID ::= 228
id-NB-IoT-DefaultPagingDRX ProtocolIE-ID ::= 234
id-ConnectedengNBList ProtocolIE-ID ::= 291

ENB CONFIGURATION UPDATE ACKNOWLEDGE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
Criticality DiagnosticsOYESignore
-- **************************************************************
--
-- eNB Configuration Update Acknowledge
--
-- **************************************************************

ENBConfigurationUpdateAcknowledge ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {ENBConfigurationUpdateAcknowledgeIEs} },
    ...
}
ENBConfigurationUpdateAcknowledgeIEs S1AP-PROTOCOL-IES ::= {
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics PRESENCE optional   },
    ...
}

ENB CONFIGURATION UPDATE FAILURE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
CauseMYESignore
Time to WaitOYESignore
Criticality DiagnosticOYESignore
-- **************************************************************
--
-- eNB Configuration Update Failure
--
-- **************************************************************

ENBConfigurationUpdateFailure ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {ENBConfigurationUpdateFailureIEs} },
    ...
}

ENBConfigurationUpdateFailureIEs S1AP-PROTOCOL-IES ::= {
    { ID id-Cause                       CRITICALITY ignore  TYPE Cause                      PRESENCE mandatory  }|
    { ID id-TimeToWait                  CRITICALITY ignore  TYPE TimeToWait                 PRESENCE optional   }|
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional   },
...
}
IE具体内容参考S1 Setup Failure

MME Configuration Update

概述

MME 配置更新过程的目的是更新 eNB 和 MME 在 S1 接口上正确互操作所需的应用层配置数据。此过程不影响现有的与用户设备（UE）相关的上下文（如果有）。

Elementary ProcedureInitiating MessageSuccessful Outcome/ Response messageUnsuccessful Outcome/ Response message
MME Configuration UpdateMME CONFIGURATION UPDATEENB CONFIGURATION UPDATE ACKNOWLEDGEMME CONFIGURATION UPDATE FAILURE

id-MMEConfigurationUpdate ProcedureCode ::= 30

流程

成功场景

在这里插入图片描述

The MME initiates the procedure by sending an MME CONFIGURATION UPDATE message including the appropriate updated configuration data to the eNB. The eNB responds with an MME CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If information element(s) is/are not included in the MME CONFIGURATION UPDATE message, the eNB shall interpret that the corresponding configuration data is not changed and shall continue to operate the S1 with the existing related configuration data.
If the served PLMNs is/are to be updated, the eNB shall overwrite the whole list of PLMNs.
If the MME CONFIGURATION UPDATE message contains the MME Name IE, the eNB may use this IE as a human readable name of the MME.
The updated configuration data shall be stored in the respective node and used for the duration of the TNL association or until any further update is performed from the MME.
The MME may initiate a further MME Configuration Update procedure only after a previous MME Configuration Update procedure has been completed.
If the MME CONFIGURATION UPDATE message contains the ServedDCNs IE then the eNB shall, if supported, use it as defined in TS 23.401 [11].

失败场景

在这里插入图片描述

If the eNB cannot accept the update, it shall respond with an MME CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the MME CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE the MME shall wait at least for the indicated time before reinitiating the MME Configuration Update procedure towards the same eNB. Both nodes shall continue to operate the S1 with the existing configuration data.

异常情况

If the MME neither receives an MME CONFIGURATION UPDATE ACKOWLEDGE nor an MME CONFIGURATION UPDATE FAILURE message, the MME may reinitiate MME Configuration Update procedure towards the same eNB provided that the content of the new MME CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged MME CONFIGURATION UPDATE message.

信元

MME CONFIGURATION UPDATE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
MME NameOYESignore
Served GUMMEIs1…8GLOBALreject
#Served PLMNs1…32-
##PLMN IdentityM-
#Served GroupIDs1…65535-
##MME Group IDM-
#Served MMECs1…256-
##MME CodeM-
Relative MME CapacityMYESignore
Served DCNs0…32GLOBALignore
#Served DCNs ItemsM-
-- **************************************************************
--
-- MME CONFIGURATION UPDATE ELEMENTARY PROCEDURE
--
-- **************************************************************

-- **************************************************************
--
-- MME Configuration Update 
--
-- **************************************************************

MMEConfigurationUpdate ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {MMEConfigurationUpdateIEs} },
    ...
}

MMEConfigurationUpdateIEs S1AP-PROTOCOL-IES ::= {
    { ID id-MMEname                 CRITICALITY ignore  TYPE MMEname                PRESENCE optional   }|
    { ID id-ServedGUMMEIs           CRITICALITY reject  TYPE ServedGUMMEIs          PRESENCE optional   }|
    { ID id-RelativeMMECapacity     CRITICALITY reject  TYPE RelativeMMECapacity    PRESENCE optional   }|
    { ID id-ServedDCNs              CRITICALITY ignore  TYPE ServedDCNs             PRESENCE optional},
    ...
}
具体IE 参考S1 Setup Response

id-MMEname ProtocolIE-ID ::= 61
id-ServedGUMMEIs ProtocolIE-ID ::= 105
id-RelativeMMECapacity ProtocolIE-ID ::= 87
id-MMERelaySupportIndicator ProtocolIE-ID ::= 163
id-CriticalityDiagnostics ProtocolIE-ID ::= 58
id-UE-RetentionInformation ProtocolIE-ID ::= 228
id-ServedDCNs ProtocolIE-ID ::= 247

MME CONFIGURATION UPDATE ACKNOWLEDGE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
Criticality DiagnosticsOYESignore
-- **************************************************************
--
-- MME Configuration Update Acknowledge
--
-- **************************************************************

MMEConfigurationUpdateAcknowledge ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {MMEConfigurationUpdateAcknowledgeIEs} },
    ...
}


MMEConfigurationUpdateAcknowledgeIEs S1AP-PROTOCOL-IES ::= {
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics         PRESENCE optional   },
    ...
}

MME CONFIGURATION UPDATE FAILURE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
CauseMYESignore
Time to WaitOYESignore
Criticality DiagnosticOYESignore
-- **************************************************************
--
-- MME Configuration Update Failure
--
-- **************************************************************

MMEConfigurationUpdateFailure ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {MMEConfigurationUpdateFailureIEs} },
    ...
}

MMEConfigurationUpdateFailureIEs S1AP-PROTOCOL-IES ::= {
    { ID id-Cause                       CRITICALITY ignore  TYPE Cause                      PRESENCE mandatory  }|
    { ID id-TimeToWait                  CRITICALITY ignore  TYPE TimeToWait                 PRESENCE optional   }|
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional   },
    ...
}

Reset

概述

Reset 流程的目的是在 EPC（演进分组核心网）发生故障时初始化或重新初始化E-UTRAN或 E-UTRAN S1AP 与用户设备（UE）相关的部分上下文，反之亦然。此过程不影响例如在 S1 设置过程中交换的应用层配置数据。

Elementary ProcedureInitiating MessageSuccessful Outcome/ Response messageUnsuccessful Outcome/ Response message
ResetRESETRESET ACKNOWLEDGE

id-Reset ProcedureCode ::= 14

流程

reset from eNB

在这里插入图片描述

In the event of a failure at the eNB, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the MME.
At reception of the RESET message the MME shall release all allocated resources on S1 related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the S1AP ID for the indicated UE associations.
After the MME has released all assigned S1 resources and the UE S1AP IDs for all indicated UE associations which can be used for new UE-associated logical S1-connections over the S1 interface, the MME shall respond with the RESET ACKNOWLEDGE message.
If the RESET message contains the UE-associated logical S1-connection list IE, then:

  • The MME shall use the MME UE S1AP ID IE and/or the eNB UE S1AP ID IE to explicitly identify the UE association(s) to be reset.
  • The MME shall include in the RESET ACKNOWLEDGE message, for each UE association to be reset, the UE-associated logical S1-connection Item IE in the UE-associated logical S1-connection list IE. The UE-associated logical S1-connection Item IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical S1-connections. Empty UE-associated logical S1-connection Item IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message.
  • If the MME UE S1AP ID IE is included in the UE-associated logical S1-connection Item IE for a UE association, the MME shall include the MME UE S1AP ID IE in the corresponding UE-associated logical S1-connection Item IE in the RESET ACKNOWLEDGE message.
  • If the eNB UE S1AP ID IE is included in a UE-associated logical S1-connection Item IE for a UE association, the MME shall include the eNB UE S1AP ID IE in the corresponding UE-associated logical S1-connection Item IE in the RESET ACKNOWLEDGE message.

Interactions with other procedures:
If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same S1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted.

reset from MME

在这里插入图片描述

In the event of a failure the MME, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the eNB.
At reception of the RESET message the eNB shall release all allocated resources on S1 and Uu releated to UE association(s) indicated explicitly or implicitly in the RESET message and remove the indicated UE contexts including S1AP ID.
After the eNB has released all assigned S1 resources and the UE S1AP IDs for all indicated UE associations which can be used for new UE-associated logical S1-connections over the S1 interface, the eNB shall respond with the RESET ACKNOWLEDGE message. The eNB does not need to wait for the release of radio resources to be completed before returning the RESET ACKNOWLEDGE message.
If the RESET message contains the UE-associated logical S1-connection list IE, then:

  • The eNB shall use the MME UE S1AP ID IE and/or the eNB UE S1AP ID IE to explicitly identify the UE association(s) to be reset.
  • The eNB shall include in the RESET ACKNOWLEDGE message, for each UE association to be reset, the UE-associated logical S1-connection Item IE in the UE-associated logical S1-connection list IE. The UE-associated logical S1-connection Item IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical S1-connections. Empty UE-associated logical S1-connection Item IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message.
  • If the MME UE S1AP ID IE is included in the UE-associated logical S1-connection Item IE for a UE association, the eNB shall include the MME UE S1AP ID IE in the corresponding UE-associated logical S1-connection Item IE in the RESET ACKNOWLEDGE message.
  • If the eNB UE S1AP ID IE is included in the UE-associated logical S1-connection Item IE for a UE association, the eNB shall include the eNB UE S1AP ID IE in the corresponding UE-associated logical S1-connection Item IE in the RESET ACKNOWLEDGE message.

Interactions with other procedures:
If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same S1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted.

异常情况

At EPC

If the RESET message includes the UE-associated logical S1-connection list IE, but neither the MME UE S1AP ID IE nor the eNB UE S1AP ID IE is present for a UE-associated logical S1-connection Item IE, then the MME shall ignore the UE-associated logical S1-connection Item IE. The MME may return the empty UE-associated logical S1-connection Item IE in the UE-associated logical S1-connection list IE in the RESET ACKNOWLEDGE message.

At eNB

If the RESET message includes the UE-associated logical S1-connection list IE, but neither the MME UE S1AP ID IE nor the eNB UE S1AP ID IE is present for a UE-associated logical S1-connection Item IE, then the eNB shall ignore the UE-associated logical S1-connection Item IE. The eNB may return the empty UE-associated logical S1-connection Item IE in the UE-associated logical S1-connection list IE in the RESET ACKNOWLEDGE message.

Crossing of Reset Message

If a Reset procedure is ongoing in the eNB and the eNB receives a RESET message from the peer entity on the same S1 interface related to one or several UE associations previously requested to be reset, indicated explicitly or implicitly in the received RESET message, the eNB shall respond with the RESET ACKNOWLEDGE message.
If a Reset procedure is ongoing in the MME and the MME receives a RESET message from the peer entity on the same S1 interface related to one or several UE associations previously requested to be reset, indicated explicitly or implicitly in the received RESET message, the MME shall respond with the RESET ACKNOWLEDGE message.

信元

RESET

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
CauseMYESignore
CHOICE Reset TypeMYESreject
#S1 interface
##Reset AllM-
#Part of S1 interface
##UE-associated logical S1-connection list1-
###UE-associated logical S1-connection Item1…256EACHreject
####MME UE S1AP IDO-
###eNB UE S1AP IDO-
-- RESET ELEMENTARY PROCEDURE
--
-- **************************************************************

-- **************************************************************
--
-- Reset
--
-- **************************************************************

Reset ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       { {ResetIEs} },
    ...
}

ResetIEs S1AP-PROTOCOL-IES ::= {
    { ID id-Cause                       CRITICALITY ignore  TYPE Cause                      PRESENCE mandatory  }|
    { ID id-ResetType                   CRITICALITY reject  TYPE ResetType                  PRESENCE mandatory  },
    ...
}

id-Cause ProtocolIE-ID ::= 2
id-ResetType ProtocolIE-ID ::= 92
id-UE-associatedLogicalS1-ConnectionItem ProtocolIE-ID ::= 91

Reset Type
ResetType ::= CHOICE {
    s1-Interface                    ResetAll,
    partOfS1-Interface              UE-associatedLogicalS1-ConnectionListRes,
    ...
}

ResetAll ::= ENUMERATED {
    reset-all,
    ...
}

UE-associatedLogicalS1-ConnectionListRes ::= SEQUENCE (SIZE(1.. maxnoofIndividualS1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE-associatedLogicalS1-ConnectionItemRes } }
maxnoofIndividualS1ConnectionsToReset	INTEGER ::= 256

UE-associatedLogicalS1-ConnectionItemRes S1AP-PROTOCOL-IES ::= {
    { ID id-UE-associatedLogicalS1-ConnectionItem   CRITICALITY reject  TYPE UE-associatedLogicalS1-ConnectionItem  PRESENCE mandatory},
    ...
}

UE-associatedLogicalS1-ConnectionItem ::= SEQUENCE {
	mME-UE-S1AP-ID		MME-UE-S1AP-ID OPTIONAL,
	eNB-UE-S1AP-ID		ENB-UE-S1AP-ID OPTIONAL,
	iE-Extensions		ProtocolExtensionContainer { { UE-associatedLogicalS1-ConnectionItemExtIEs} } OPTIONAL,
	...
}

MME-UE-S1AP-ID	::= INTEGER (0..4294967295)
ENB-UE-S1AP-ID	::= INTEGER (0..16777215)

RESET ACKNOWLEDGE

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESreject
UE-associated logical S1-connection list0…1YESignore
#UE-associated logical S1-connection Item1…256EACHignore
##MME UE S1AP IDO-
##eNB UE S1AP IDO-
ResetAcknowledgeIEs S1AP-PROTOCOL-IES ::= {
    { ID id-UE-associatedLogicalS1-ConnectionListResAck     CRITICALITY ignore  TYPE UE-associatedLogicalS1-ConnectionListResAck            PRESENCE optional   }|
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics         PRESENCE optional   },
    ...
}

UE-associatedLogicalS1-ConnectionListResAck ::= SEQUENCE (SIZE(1.. maxnoofIndividualS1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE-associatedLogicalS1-ConnectionItemResAck } }
maxnoofIndividualS1ConnectionsToReset   INTEGER ::= 256

UE-associatedLogicalS1-ConnectionItemResAck     S1AP-PROTOCOL-IES ::= {
    { ID id-UE-associatedLogicalS1-ConnectionItem    CRITICALITY ignore     TYPE UE-associatedLogicalS1-ConnectionItem      PRESENCE mandatory },
    ...
}

UE-associatedLogicalS1-ConnectionItem ::= SEQUENCE {
	mME-UE-S1AP-ID		MME-UE-S1AP-ID OPTIONAL,
	eNB-UE-S1AP-ID		ENB-UE-S1AP-ID OPTIONAL,
	iE-Extensions		ProtocolExtensionContainer { { UE-associatedLogicalS1-ConnectionItemExtIEs} } OPTIONAL,
	...
}

MME-UE-S1AP-ID	::= INTEGER (0..4294967295)
ENB-UE-S1AP-ID				::= INTEGER (0..16777215)

Error Indication

概述

Error Indication流程由一个节点发起，以便报告在一个传入消息中检测到的错误，前提是这些错误不能通过适当的失败消息进行报告。

如果错误情况是由于接收到使用与用户设备（UE）相关信令的消息而产生的，那么错误指示过程使用与 UE 相关的信令。否则，该过程使用与 UE 无关的信令。

Elementary ProcedureMessage
Error IndicationERROR INDICATION

id-ErrorIndication ProcedureCode ::= 15

流程

MME originated

在这里插入图片描述

eNB originated

在这里插入图片描述

When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node.
The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE. In case the Error Indication procedure is triggered by utilising UE associated signalling the MME UE S1AP ID IE and the eNB UE S1AP ID IE shall be included in the ERROR INDICATION message. If one or both of MME UE S1AP ID IE and the eNB UE S1AP ID IE are not correct, the cause shall be set to appropriate value, e.g., “Unknown or already allocated MME UE S1AP ID”, “Unknown or already allocated eNB UE S1AP ID” or “Unknown or inconsistent pair of UE S1AP ID”.

信元

ERROR INDICATION

IE/Group NamePRangeSemantics descriptionCriticalityAssigned Criticality
Message TypeMYESignore
MME UE S1AP IDOYESignore
eNB UE S1AP IDOYESignore
CauseOYESignore
-- **************************************************************
--
-- ERROR INDICATION ELEMENTARY PROCEDURE
--
-- **************************************************************

-- **************************************************************
--
-- Error Indication
--
-- **************************************************************

ErrorIndication ::= SEQUENCE {
    protocolIEs         ProtocolIE-Container       {{ErrorIndicationIEs}},
    ...
}

ErrorIndicationIEs S1AP-PROTOCOL-IES ::= {
    { ID id-MME-UE-S1AP-ID              CRITICALITY ignore  TYPE MME-UE-S1AP-ID             PRESENCE optional   }|
    { ID id-eNB-UE-S1AP-ID              CRITICALITY ignore  TYPE ENB-UE-S1AP-ID             PRESENCE optional   }|
    { ID id-Cause                       CRITICALITY ignore  TYPE Cause                      PRESENCE optional   }|
    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional   },
    ...
}
Cause

Radio Network Layer - (0)
Unknown or already allocated MME UE S1AP ID - (12)
Unknown or already allocated eNB UE S1AP ID - (13)
Unknown or inconsistent pair of UE S1AP ID - (14)

UE上下文管理、S1-AP、X2-AP
weixin_42563968的博客
08-26 4225
UE上下文建立 ① 基站eNB首先向MME发送Initial Message消息，通知MME有终端需要建立上下文，同时建立了终端在S1-MME接口上的信令连接 ②MME鉴权，确认用户身份后，将Initial Context Setup Request消息发送给eNB ③基站eNB收到Initial Context Setup Request消息后，存储终端的上下文，向MME回复Initial Context Setup Response消息，完成终端上下文建立 建立终端上下文过程两个重要的任务： ①建立终
LTE L3 Procedure - RRC(S1AP, NAS)
喵喵的技术博客
10-16 4129
相比L1/2涉及底层接入与传输的相关流程，L3信令流程则起着统筹全局的功能，总体而言，L3信令流程负责： 1. 用于构建与释放基站和UE两侧RRC信令传输的SRB1和SRB2以及其下的L1/2配置，UE和基站各协议模块配置彼此对应。 2. 用于构建与释放基站和UE两侧IP数据包传输的default DRB和dedicated DRB以及其下的L1/2配置，UE和基站各协议模块配置彼此对应。 3. ...
LTE数字蜂窝移动通信网S1应用协议(S1AP)
09-05
LTE数字蜂窝移动通信网S1应用协议(S1AP)中文版，描述eNB与MME之间的消息结构
36413-930_S1AP协议规范.pdf（注意：这是英文的，旧版的，要中文和相对较新的，请找我另外一份资源）
01-13
在3GPP的官网上下载资源，有时超慢，现在把标准协议文档下载后分享给大家。。。。。。。。。。。。。。
TS36.413 S1AP协议 Release15 最新
04-18
TS36.413 S1AP协议 Release15 最新！ 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 15)
S1AP协议输出文档部分内容备份
08-30
自己输出文档的备份。用于后续的学习，是看S1AP原协议的一种总结。不建议下载。
S1AP基本信令流程
01-26
S1AP基本信令流程，实用性文档，欢迎下载
TD-LTE信令流程及信令解码.doc
06-08
S1AP协议是LTE系统中的信令协议，负责UE和eNB之间的控制信息交换。 本文对TD-LTE信令流程进行了详细分析，并对相关信令进行解码。通过对信令流程的分析，可以更好地理解TD-LTE系统的工作原理和实现机理。
S1接口得信令承载
dxm809的博客
05-14 1392
15:11:12.122 [S1AP] TO 127.0.1.100:36412 Initial UE message initiatingMessage: { procedureCode id-initialUEMessage, criticality ignore, value { protocolIEs { { id id-eNB-UE-S1.
s1ap pcap log
xrh003的博客
07-19 1100
一次正常的ue接入s1ap 抓包
关于通信网络中S1接口信令策略和性能测量相关知识
最新发布
weixin_42736657的博客
10-15 941
S1接口性能测量是LTE网络中一个重要的监控和优化手段，通过对控制面、用户面、切换和资源利用等多方面的性能指标进行监控和分析，可以全面了解网络的运行状态，及时发现和解决问题，确保网络的高效、稳定和可靠运行。S1接口是LTE（Long Term Evolution，长期演进）网络中eNodeB（演进型Node B，即基站）和EPC（Evolved Packet Core，演进型分组核心网）之间的接口。S1接口分为S1-U（用户面接口）和S1-MME（控制面接口）。
srsLTE源码学习：S1接口抓包s1ap_pcap.h，s1ap_pcap.cc
RToax
04-11 2278
Table of Contents 介绍 图例 代码 s1ap_pcap.h s1ap_pcap.cc s1ap_test.cc 介绍 S1接口是LTE eNodeB（基站）与 EPC（分组核心网）之间的通讯接口。 将LTE系统划分为无线接入网和核心网。 S1接口沿袭了承载和控制分离的思想，又分成两个接口，一个用于控制平面（S1-MME），一个用于用户平面（...
LTE常用协议
qwebaby2的博客
03-23 6599
LTE常用协议s1ap介绍功能SCTP介绍报文格式Diameter介绍报文格式GTP GPRS隧道协议GTPU报文格式GTPC报文格式 s1ap 介绍 1.S1接口是LTE **eNodeB（基站）**与 EPC（分组核心网）之间的通讯接口。 2.将LTE系统划分为无线接入网和核心网。 3.S1接口分成两个接口，一个用于控制平面（S1-MME），一个用于用户平面（S1-U）。 4.控制平面接口S1...
volte端到端问题分析(一)
qq_44390640的博客
08-09 2407
主被叫于15:10:06.174通话成功，通话1分钟后，被叫手机于15:11:42.014进行IMS_SIP重注册（被叫在10分钟前进行过一次IMS SIP注册，软件显示注册成功），在15:11:43.584手机上发Notify 200注册成功，与此同时主叫在15:11:43.494收到网络下发bye（Content = Reason: Q.850;该问题主要是由于被叫注册失败导致主叫接通不了而导致的掉话，而注册过程中，终端和网络需要核对鉴权向量，当终端和网络协商鉴权向量一致时，才能保证注册成功。
【LTE】LTE轻松进阶学习笔记-接口协议（4）
Blogs
03-23 4602
接口协议栈       接口是指不同网元之间的信息交互方式，用于信息交互双方的“语言”，就是接口协议，而接口协议的架构称为协议栈。       根据无线通信制式接口所处的物理位置，可以将接口分为空中接口和地面接口，相应的，接口协议分为空中接口协议和地面接口协议。其中，空中接口是无线制式最具个性的地方，不同的无线制式，其空口的物理层的技术实现差别巨大。       LTE无线侧的主要接口也分为空中接...
[转载]3GPP 36系列协议及LTE技术贯穿的思想_akala啦_新浪博客
qq_29468403的博客
04-09 332
原文地址：3GPP36系列协议及LTE技术贯穿的思想作者：过儿对LTE的体会，它无时无刻不灌输着这样一个思想：就是物理层和MAC层的处理因信道和信息而异：对于良好的信道，（频率选择性和时间选择性较弱）我们想用空分复用，高阶调制来让他传更多的东西；对于较差的信道，我们使用发射分集和更加稳健调制编码来提高他的可靠性。围绕着个问题，有很多相关的问题，比如信道估计啊，MAC调度啊之类的。 对于关...
[LTE] LTE系统中的ID
轻舞飞扬
12-08 3381
这篇文章介绍LTE系统中的ID，首先展示下从Netmanias 来的一幅图 这里写图片描述 在阐述每一个ID的作用之前，先将右图中繁杂的ID分个类， 与终端设备相关的： IMEI，IMSI，GUTI，S-TMSI，IP地址（PDN地址），C-RNTI，eNB UE S1AP ID，MME UE S1AP ID，Old UE X2AP ID，UE X2AP ID 与网络设备相关的：
Ubuntu中安装nginxError
fanxindong0620的博客
10-21 237
问题1：出现如下错误： ./configure: error: the HTTP rewrite module requires the PCRE library. You can either disable the module by using --without-http_rewrite_module option, or install the PCRE library into the...
Radio link failure 前因后果
热门推荐
知行合一
10-21 1万+
For your understanding, the definition of Radio Link Failure is simply "Physical Layer (especially low PHY) break" and in most case this failure is unintentional. Firstly the question is "How UE or
3GPP TS36.413: E-UTRAN S1AP协议规范
7. NAS（非接入层）信令传输：S1AP协议也负责将NAS层的信令在eNodeB和MME之间透明传输，如附着、分离、会话建立和更新等。 8. 故障检测和恢复：S1AP提供了心跳检测机制，用于检测S1接口的连通性，并在发现故障时...
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值