 |
善于提问，勤于回答，你也是专家
|
 |
问题已开启
(普通问题)
提问者:
• TD-LTE中信令HANDOVerfailure分析原因附图 2015-01-04
• 请问atu 测试信令 HANDOVer start in TDD Mode怎么理解 2013-07-13
• 在越局切换中,新MSC 向旧MSC 发送的切换信令Prepare HANDOVer 中可能包含以下哪些信 2013-07-09
• 切换过程中 MS收到 HANDOVer commAND 但一直没有发送 HO access 然后切换失败 这是啥原因 2011-08-25
• HANDOVer failure layer2 failure 2011-08-22
• HANDOVer commAND里的Threshold 1、2、3和Hysteresis 1、2、3是什么意思 2011-08-16
• GSM中网络，“HANDOVer margin=5”---边缘切换=5什么意思？ 2011-06-18
• 请问atu 测试信令 HANDOVer start in TDD Mode怎么理解 2013-07-13
• 在越局切换中,新MSC 向旧MSC 发送的切换信令Prepare HANDOVer 中可能包含以下哪些信 2013-07-09
• 切换过程中 MS收到 HANDOVer commAND 但一直没有发送 HO access 然后切换失败 这是啥原因 2011-08-25
• HANDOVer failure layer2 failure 2011-08-22
• HANDOVer commAND里的Threshold 1、2、3和Hysteresis 1、2、3是什么意思 2011-08-16
• GSM中网络，“HANDOVer margin=5”---边缘切换=5什么意思？ 2011-06-18
问题答案
( 2 )
handover request
handover require
handover require
回答者：
ebrain68
回答时间：2014-07-30 09:09
7
6
HANDOVER REQUIRED
This message is sent by the source eNB to the MME to request the preparation of resources at the target.Direction: eNB ® MME.
|
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
|
9.2.1.1 |
|
YES |
reject |
|
MME UE S1AP ID |
M |
|
9.2.3.3 |
|
YES |
reject |
|
eNB UE S1AP ID |
M |
|
9.2.3.4 |
|
YES |
reject |
|
Handover Type |
M |
|
9.2.1.13 |
|
YES |
reject |
|
Cause |
M |
|
9.2.1.3 |
|
YES |
ignore |
|
Target ID |
M |
|
9.2.1.6 |
|
YES |
reject |
|
Direct Forwarding Path Availability |
O |
|
9.2.3.15 |
|
YES |
ignore |
|
SRVCC HO Indication |
O |
|
9.2.1.59 |
|
YES |
reject |
|
Source to Target Transparent Container |
M |
|
9.2.1.56 |
|
YES |
reject |
|
Source to Target Transparent Container Secondary |
O |
|
Source to Target Transparent Container 9.2.1.56 |
|
YES |
reject |
|
MS Classmark 2 |
C- ifSRVCCtoGERAN |
|
9.2.1.64 |
|
YES |
reject |
|
MS Classmark 3 |
C- ifSRVCCtoGERAN |
|
9.2.1.65 |
|
YES |
ignore |
|
CSG Id |
O |
|
9.2.1.62 |
|
YES |
reject |
|
Cell Access Mode |
O |
|
9.2.1.74 |
|
YES |
reject |
|
PS Service Not Available |
O |
|
9.2.1.77 |
|
YES |
ignore |
ebrain68 2014-07-30 09:15
HANDOVER REQUEST
This message is sent by the source eNB to the target eNB to request the preparation of resources for a handover.Direction: source eNB ® target eNB.
|
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
|
9.2.13 |
|
YES |
reject |
|
Old eNB UE X2AP ID |
M |
|
eNB UE X2AP ID 9.2.24 |
Allocated at the source eNB |
YES |
reject |
|
Cause |
M |
|
9.2.6 |
|
YES |
ignore |
|
Target Cell ID |
M |
|
ECGI 9.2.14 |
|
YES |
reject |
|
GUMMEI |
M |
|
9.2.16 |
|
YES |
reject |
|
UE Context Information |
|
1 |
|
|
YES |
reject |
|
>MME UE S1AP ID |
M |
|
INTEGER (0..232 -1) |
MME UE S1AP ID allocated at the MME |
– |
– |
|
>UE Security Capabilities |
M |
|
9.2.29 |
|
– |
– |
|
>AS Security Information |
M |
|
9.2.30 |
|
– |
– |
|
>UE Aggregate Maximum Bit Rate |
M |
|
9.2.12 |
|
– |
– |
|
>Subscriber Profile ID for RAT/Frequency priority |
O |
|
9.2.25 |
|
– |
– |
|
>E-RABs To Be Setup List |
|
1 |
|
|
– |
– |
|
>>E-RABs To Be Setup Item |
|
1 .. <maxnoof Bearers> |
|
|
EACH |
ignore |
|
>>>E-RAB ID |
M |
|
9.2.23 |
|
– |
– |
|
>>>E-RAB Level QoS Parameters |
M |
|
9.2.9 |
Includes necessary QoS parameters |
– |
– |
|
>>>DL Forwarding |
O |
|
9.2.5 |
|
– |
– |
|
>>>UL GTP Tunnel Endpoint |
M |
|
GTP Tunnel Endpoint 9.2.1 |
SGW endpoint of the S1 transport bearer. For delivery of UL PDUs. |
– |
– |
|
>RRC Context |
M |
|
OCTET STRING |
Includes the RRC Handover Preparation Information message as defined in subclause 10.2.2 of TS 36.331 [9]. |
– |
– |
|
>Handover Restriction List |
O |
|
9.2.3 |
|
– |
– |
|
>Location Reporting Information |
O |
|
9.2.21 |
Includes the necessary parameters for location reporting |
– |
– |
|
>Management Based MDT Allowed |
O |
|
9.2.59 |
|
YES |
ignore |
|
UE History Information |
M |
|
9.2.38 |
Same definition as in TS 36.413 [4]. |
YES |
ignore |
|
Trace Activation |
O |
|
9.2.2 |
|
YES |
ignore |
|
SRVCC Operation Possible |
O |
|
9.2.33 |
|
YES |
ignore |
|
CSG |
O |
|
9.2.52 |
|
YES |
reject |
ebrain68 2014-07-30 09:17
麻烦具体点，我的是tems测试 的log，之前在层3信令中找未找到
还有百度说是应该找HANDOVER CAUSE这条信令，但也没有找到，
求指教
还有百度说是应该找HANDOVER CAUSE这条信令，但也没有找到，
求指教
Mrtamos 2014-07-30 10:15
空口消息不会包含cause的，空口的实质切换流程基本只有3个：
1.ue上报测量报告
2.source enodeb发送rrcconnectionreconfig（HO cmd）给UE
3.ue发送rrcconnectionreconfig给目标enodeb
因为切换判决都在enodeb网络测，也只有enodeb知道切换的具体情况，手机只是被动的按照测量控制消息配置给它的测量参量进行测量并上报相应报告而已。
1.ue上报测量报告
2.source enodeb发送rrcconnectionreconfig（HO cmd）给UE
3.ue发送rrcconnectionreconfig给目标enodeb
因为切换判决都在enodeb网络测，也只有enodeb知道切换的具体情况，手机只是被动的按照测量控制消息配置给它的测量参量进行测量并上报相应报告而已。
ebrain68 2014-07-30 11:37
这个前台看不到 你可以查看后台切换参数 pbgt和 层级切换门限以及持续时间统计时间 你要是不想切可以吧持续时间改长 要是还不行就把切换门限该大
回答者：
wayter
回答时间：2014-07-31 17:26
18
18
| 联系我们 - 问通信专家 | Powered by MSCBSC 移动通信网 © 2006 - |