LTE 信令流程log 之 Amarisoft MME
来源：互联网 发布：lols7鳄鱼技能数据 编辑：程序博客网 时间：2024/06/05 08:22
最近在研究SDR LTE系统之间的互联互通，成功调通了Amari MME + OAI eNB + srsUE。不知道这些SDR LTE平台的可以参见我的博客http://blog.csdn.net/jxwxg/article/details/53026659。
调通之后，抓取了MME，eNB和UE侧的信令流程log，流程包括了eNB与MME的连接，UE随机接入，UE鉴权等过程。由于Log内容较多，本博客只介绍Amari MME侧Log信息。OAI eNB的Log信息可以点击 http://blog.csdn.net/jxwxg/article/details/53999085 。 srsUE侧的信令流程Log信息可以点击 http://blog.csdn.net/jxwxg/article/details/53999163。
# ltemme version 2014-06-16 # Log file format:# time layer dir [enb_id|mme_ue_id] message22:02:30.149 [S1AP] - - New connection from 127.0.0.1:3641222:02:30.149 [S1AP] FROM 127.0.0.1:36412 S1 setup request initiatingMessage: { procedureCode id-S1Setup, criticality reject, value { protocolIEs { { id id-Global-ENB-ID, criticality reject, value { pLMNidentity '00F110'H, eNB-ID macroENB-ID: '00E00'H } }, { id id-eNBname, criticality ignore, value "eNB_Eurecom_LTEBox" }, { id id-SupportedTAs, criticality reject, value { { tAC '0001'H, broadcastPLMNs { '00F110'H } } } }, { id id-DefaultPagingDRX, criticality ignore, value v128 } } } }22:02:30.149 [S1AP] TO 127.0.0.1:36412 S1 setup response successfulOutcome: { procedureCode id-S1Setup, criticality reject, value { protocolIEs { { id id-ServedGUMMEIs, criticality reject, value { { servedPLMNs { '00F110'H }, servedGroupIDs { '8001'H }, servedMMECs { '01'H } } } }, { id id-RelativeMMECapacity, criticality ignore, value 50 } } } }22:02:45.812 [S1AP] FROM 127.0.0.1:36412 Initial UE message initiatingMessage: { procedureCode id-initialUEMessage, criticality reject, value { protocolIEs { { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '0741010809101010325476110280E000040201D011'H }, { id id-TAI, criticality reject, value { pLMNidentity '00F110'H, tAC '0001'H } }, { id id-EUTRAN-CGI, criticality ignore, value { pLMNidentity '00F110'H, cell-ID '00E0000'H } }, { id id-RRC-Establishment-Cause, criticality ignore, value mo-Signalling } } } }22:02:45.812 [NAS] UL 0064 EMM: Attach request Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x41 (Attach request) EPS attach type = 1 (EPS attach) NAS key set identifier: TSC = 0 NAS key set identifier = 0 Old GUTI or IMSI: IMSI = 001010123456711 UE network capability: Length = 2 Data = 80 e0 ESM message container: Protocol discriminator = 0x2 (EPS Session Management) EPS bearer identity = 0 Procedure transaction identity = 1 Message type = 0xd0 (PDN connectivity request) Request type = 1 PDN type = 1 (IPv4)22:02:45.812 [NAS] - 6692d EPS encryption caps=0x80 integrity caps=0xe022:02:45.812 [NAS] DL 0064 EMM: Authentication request Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x52 (Authentication request) Remaining bytes: 00 c6 db 21 b5 ee 2e fc f0 97 77 20 24 65 f5 62 ef 10 84 a2 c2 76 ed 4f 90 01 2a 6f 4b 02 cd fc 2d b022:02:45.812 [S1AP] TO 127.0.0.1:36412 Downlink nas transport initiatingMessage: { procedureCode id-downlinkNASTransport, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '075200C6DB21B5EE2EFCF09777202465F562EF1084A2C276ED4F90012A6F4B02CDFC2DB0'H } } } }22:02:45.822 [S1AP] FROM 127.0.0.1:36412 Uplink nas transport initiatingMessage: { procedureCode id-uplinkNASTransport, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '0753080244D55949F29C3C'H }, { id id-EUTRAN-CGI, criticality ignore, value { pLMNidentity '00F110'H, cell-ID '00E0000'H } }, { id id-TAI, criticality ignore, value { pLMNidentity '00F110'H, tAC '0001'H } } } } }22:02:45.823 [NAS] UL 0064 EMM: Authentication response Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x53 (Authentication response) Remaining bytes: 08 02 44 d5 59 49 f2 9c 3c22:02:45.823 [NAS] - 6692d UE auth OK22:02:45.823 [NAS] DL 0064 EMM: Security mode command Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x3 (Integrity protected with new EPS security context) Auth code = 0xd690e201 Sequence number = 0x00 Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x5d (Security mode command) Remaining bytes: 01 00 02 80 e0 c122:02:45.823 [S1AP] TO 127.0.0.1:36412 Downlink nas transport initiatingMessage: { procedureCode id-downlinkNASTransport, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '37D690E20100075D01000280E0C1'H } } } }22:02:45.832 [S1AP] FROM 127.0.0.1:36412 Uplink nas transport initiatingMessage: { procedureCode id-uplinkNASTransport, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '2754CB923B00075E23098396090782456156F3'H }, { id id-EUTRAN-CGI, criticality ignore, value { pLMNidentity '00F110'H, cell-ID '00E0000'H } }, { id id-TAI, criticality ignore, value { pLMNidentity '00F110'H, tAC '0001'H } } } } }22:02:45.832 [NAS] UL 0064 EMM: Security mode complete Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x2 (Integrity protected and ciphered) Auth code = 0x54cb923b Sequence number = 0x00 Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x5e (Security mode complete) Remaining bytes: 23 09 83 96 09 07 82 45 61 56 f322:02:45.832 [NAS] DL 0064 EMM: Attach accept Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x2 (Integrity protected and ciphered) Auth code = 0xe79dee7a Sequence number = 0x01 Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x42 (Attach accept) EPS attach result = 1 (EPS only) T3412 value: value = 0 unit = 7 (deactivated) TAI list: Length = 6 Data = 00 00 f1 10 00 01 ESM message container: Protocol discriminator = 0x2 (EPS Session Management) EPS bearer identity = 5 Procedure transaction identity = 1 Message type = 0xc1 (Activate default EPS bearer context request) EPS Qos: Length = 1 Data = 09 Access point name = "test123" PDN address: PDN type = 1 (IPv4) IPv4 = 192.168.3.10 Protocol configuration options: ext = 1 configuration protocol = 0 GUTI: MCC = 001 MNC = 01 MME Group ID = 32769 MME Code = 1 M-TMSI = 0x0000000322:02:45.832 [S1AP] TO 127.0.0.1:36412 Initial context setup request initiatingMessage: { procedureCode id-InitialContextSetup, criticality reject, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-uEaggregateMaximumBitrate, criticality reject, value { uEaggregateMaximumBitRateDL 100000000, uEaggregateMaximumBitRateUL 50000000 } }, { id id-E-RABToBeSetupListCtxtSUReq, criticality reject, value { { id id-E-RABToBeSetupItemCtxtSUReq, criticality reject, value { e-RAB-ID 5, e-RABlevelQoSParameters { qCI 9, allocationRetentionPriority { priorityLevel 15, pre-emptionCapability shall-not-trigger-pre-emption, pre-emptionVulnerability not-pre-emptable } }, transportLayerAddress '7F000164'H, gTP-TEID '0B4982E1'H, nAS-PDU '27E79DEE7A01074201E0060000F110000100175201C101090807746573743132330501C0A8030A270180500BF600F11080010100000003'H } } } }, { id id-UESecurityCapabilities, criticality reject, value { encryptionAlgorithms '0000'H, integrityProtectionAlgorithms 'C000'H } }, { id id-SecurityKey, criticality reject, value '36B5560C498778E22BDE83792DEF2D7A7CB4C02E261F57EB475060282CA7477A'H } } } }22:02:45.852 [S1AP] FROM 127.0.0.1:36412 UE capability info indication initiatingMessage: { procedureCode id-UECapabilityInfoIndication, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-UERadioCapability, criticality ignore, value '818000208313040B82E0BB1000800002'H } } } }22:02:46.050 [S1AP] FROM 127.0.0.1:36412 Initial context setup response successfulOutcome: { procedureCode id-InitialContextSetup, criticality reject, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality ignore, value 100 }, { id id-eNB-UE-S1AP-ID, criticality ignore, value 420141 }, { id id-E-RABSetupListCtxtSURes, criticality ignore, value { { id id-E-RABSetupItemCtxtSURes, criticality ignore, value { e-RAB-ID 5, transportLayerAddress '7F000001'H, gTP-TEID 'CA6FE0DD'H } } } } } } }22:02:46.050 [S1AP] FROM 127.0.0.1:36412 Uplink nas transport initiatingMessage: { procedureCode id-uplinkNASTransport, criticality ignore, value { protocolIEs { { id id-MME-UE-S1AP-ID, criticality reject, value 100 }, { id id-eNB-UE-S1AP-ID, criticality reject, value 420141 }, { id id-NAS-PDU, criticality reject, value '27B11182F601074300035200C2'H }, { id id-EUTRAN-CGI, criticality ignore, value { pLMNidentity '00F110'H, cell-ID '00E0000'H } }, { id id-TAI, criticality ignore, value { pLMNidentity '00F110'H, tAC '0001'H } } } } }22:02:46.050 [NAS] UL 0064 EMM: Attach complete Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x2 (Integrity protected and ciphered) Auth code = 0xb11182f6 Sequence number = 0x01 Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x0 (Plain NAS message, not security protected) Message type = 0x43 (Attach complete) ESM message container: Protocol discriminator = 0x2 (EPS Session Management) EPS bearer identity = 5 Procedure transaction identity = 0 Message type = 0xc2 (Activate default E 1 0
- LTE 信令流程log 之 Amarisoft MME
- LTE 信令流程log 之 srsUE
- LTE 信令流程Log 之 OAI eNB
- 【LTE基础知识】LTE信令流程之开机附着、去附着流程分析
- LTE语音解决方案和信令流程
- srsENB + srsUE + Amarisoft MME 测试
- LTE信令
- mme log
- 无线网络-LTE (07) 通信过程之 Detach procedure MME-initiated
- OAI eNB + srsUE + Amarisoft MME成功调通
- ＬＴＥ中的ＭＭＥ层概述
- WCDMA信令流程
- WCDMA信令流程
- 呼叫(主叫)信令流程
- evdo空口信令流程
- WCDMA 基本信令流程
- 呼叫(主叫)信令流程
- 切换的信令流程
- hpu 问题 H: KACA的杨辉计数
- 运算符重载里面程序运行细节
- 铁流：中国突破半导体新工艺研发
- Java并发机制底层——原子操作的实现原理
- iOS线程通信和进程通信的例子（NSMachPort和NSTask，NSPipe）
- LTE 信令流程log 之 Amarisoft MME
- leetcode及笔试面试题整理序言
- Rime协议学习笔记：（十）polite广播
- 手把手教你在Photoshop中使用色阶工具
- mysql5.7绿色版安装--windows
- 枚举学习
- PCL同时在一个窗口中显示两个（多个）点云
- Win10 VS2013编译Boost 1.62.0
- UIImagePickerController
