您所在位置： &
&nbsp&&nbsp&nbsp&&nbsp
3GPP+LTE上行随机接入与研究.pdf77页
本文档一共被下载：
次 ,您可免费全文在线阅读后下载本文档
文档加载中...广告还剩秒
需要金币：220 &&
优秀硕士毕业论文，完美PDF格式，可在线免费浏览全文和下载,支持复制编辑,可为大学生本专业本院系本科专科大专和研究生学士硕士相关类学生提供毕业论文范文范例指导,也可为要代写发表职称论文提供参考！！！
你可能关注的文档：
··········
··········
虫塞擅噩 中文摘要中又摘要
摘要：为满足人们对日益多样化的新型业务和更高终端速率的需求，第三代伙伴
为LTE系统中极为重要的一项关键技术，是移动通信系统中的一个至关重要的步
骤。随机接入是终端接入网络的必经之路，直接关系到整个系统性能的优劣。 论文针对LTE上行随机接入问题进行了详细的研究，其主要工作体现在： 1 分析了前导时域结构中CP和GT的作用及几种前导格式适用的场景、频域
结构和资源映射方式。在此基础上对随机接入前导序列的生成过程进行了研究，
尤其重点研究了限制集模式下循环移位的取值和基带信号的产生过程。 2 建立了随机接入发射端模型，并根据此模型给出传统的随机接入接收端设
计算法。通过对该算法的运算量进行分析，提出了两点改进以减小运算量。 3 利用MATLAB搭建链路仿真平台，对前导的发送过程、信道模型、接收
端的处理过程等进行编码。利用仿真平台验证改进后接收端算法的检测性能，结
果表明改进后随机接入接收端算法的性能在满足协议的要求的前提下，在一个运
算周期内其运算量可以减小至改进前的数十乃至数百分之一。由此可大幅度提高
运算效率。
关键词：LTE；随机接入技术；ZC序列；前导检测；降采样
分类号：TN929．5 △旦墨I丛￡工 ABSTRACT ABSTRACT：Inordertomeettheneedsofnewserviceandthe ofhi requirementsgh transmissionrateofmobile third terminal，thegenerationpartnershipproject 3GPP initialized
standardizationworknamed Term the technology Long endof2004．Random in access isa acommunication technologykeytechnology system， andrandomaccessisacritical accessisthe toaccessnetwork step．Random onlyway for its is relatedtothemeritsoftheentire termnals，and performancedirectly system． The studiedLTE rand
正在加载中，请稍后...Evaluation Files Format
This document define the files format of:
We use the simple text file format specified below to describe problem instances (Markov networks).
The format is a generalization of the Ergo file format initially developed by
We use the .uai suffix for the challenge benchmark network files.
A file in the UAI format consists of the following two parts, in that order:
&Preamble&
&Function tables&
The contents of each section (denoted &...& above) are described in the following:
Our description of the format will follow a simple Markov network with three variables and two functions. A sample preamble for such a network is:
The preamble starts with one line denoting the type of network. Generally, this can be either BAYES (if the network is a Bayesian network) or MARKOV (in case of a Markov network). However, note that this year all networks will be given in a Markov networks (i.e. Bayesian networks will be moralized).
The second line contains the number of variables.
The next line specifies the cardinalities of each variable, one at a time, separated by a whitespace (note that this implies an order on the variables which will be used throughout the file).
The fourth line contains only one integer, denoting the number of cliques in the problem.
Then, one clique per line, the scope of each clique is given as follows: The first integer in each line specifies the number of variables in the clique, followed by the actual indexes of the variables.
The order of this list is not restricted.
Note that the ordering of variables within a factor will follow the order provided here.
Referring to the example above, the first line denotes the Markov network, the second line tells us the problem consists of three variables, let's refer to them as X, Y, and Z.
Their cardinalities are
2, 2, and 3 respectively (from the third line).
Line four specifies that there are 2 cliques. The first clique is X,Y, while the second clique is Y,Z.
Note that variables are indexed starting with 0.
In this section each factor is specified by giving its full table (i.e, specifying value for each assignment).
The order of the factor is identical to the one in which they were introduced in the preamble, the first variable have the role of the 'most significant' digit.
For each factor table, first the number of entries is given (this should be equal to the product of the domain sizes of the variables in the scope).
Then, one by one, separated by whitespace, the values for each assignment to the variables in the function's scope are enumerated.
Tuples are implicitly assumed in ascending order, with the last variable in the scope as the 'least significant'.
To illustrate, we continue with our Markov network example from above, let's assume the following conditional probability tables:
The correspoding function tables in the file would then look like this:
0.436 0.564
0.128 0.872
0.920 0.080
0.210 0.333 0.457
0.811 0.000 0.189
(Note that line breaks and empty lines are effectively just a whitespace, exactly like plain spaces "&".
They are used here to improve readability.)
To sum up, a problem file consists of 2 sections: the preamble and the full the function tables, the names and the labels. For our Markov network example above, the full file will look like:
0.436 0.564
0.128 0.872
0.920 0.080
0.210 0.333 0.457
0.811 0.000 0.189
Evidence is specified in a separate file. This file has the same name as the original network file but with an added .evid suffix.
For instance, problem.uai will have evidence in problem.uai.evid.
The file starts with a line specifying the number of evidences samples.
The evidence in each sample, will be written in a new line.
Each line will begin with the number of observed variables in the sample, followed by pairs of variable and its observed value.
The indexes correspond to the ones implied by the original problem file.
If, for our above example, we want to provide a single sample where the variable Y has been observed as having its first value and Z with its second value, the file example.uai.evid would contain the following:
Note that although the format allows for multiple evidence, in the current competition
we will either have no evidence or a single evidence line.
The first line must contain only the task solved: PR|MPE|MAR|BEL.
The rest of the file will contain the solution for the task.
Solvers can write more then one solution by writing -BEGIN- at the head of the new solution.
We will only consider the last solution in the file.
In the example below the task we choose is PR.
We have two solutions.
The format of the &SOLUTION& part will be described below.
&SOLUTION&
&SOLUTION&
The first line in each solution will contain the number of evidence samples.
This will be the number of lines (not include this line) in the solution part.
Hence each line from here will contain the solution with a different sample of
evidence - ordered as in the evidence file.
If there is no evidence (the first line of the evidence file is 0), the output should include the results for the empty evidence scenario.
is regarded as a single-evidence case - one with the empty evidence.
Solvers that can bound their estimation are encouraged to specify if their solution is lower or upper bound. Doing so by adding at the end of the solution the letters L(for lower bound) or U (for upper bound).
The line format is as follows (according to the task):
Partition function, PR:
Line with the
value of the log10 of the partition function.
For example, an approximation log10 Pr(e) = -0.2008
which is known to be an upper bound
may have a solution line:
Most probable explanation, MPE: A space separated line that includes:
the number n of model variables, and
the MPE instantiation, a list of value indices for all n variables.
For example, an input model with 3 binary variables may have a solution line: 3 0 1 0
Marginals, MAR: A space separated line that includes:
The number of variables in the model.
A list of marginal approximations of all the variables. For each variable its cardinality is first stated, then the probability of each state is stated. The order of the variables is the same as in the model, all data is
space separated.
For example, a model with 3 variables, with cardinalities of 2, 2, 3 respectively. The solution might look like this:
3 2 0.1 0.9 2 0.3 0.7 3 0.2 0.2 0.6
Beliefs, BEL: A space separated line that includes:
The number n of model cliques, and
A list of belief approximations for all n cliques.
Each marginal approximation is specified by a list, starting with the number of entries of the factor, followed by the approximation Pr(x|e) for each value of x (where
is a vector of the clique variables).
For example, if an input model has 2 cliques the first with 2 binary variable and the second with 3.The solution line may look like:
2 4 0.25 0.25 0.4 0.1 8 0.1 0.05 0.05 0.2 0.1 0.01 0.04 0.45
The order of the entries is as in the .
Here is a complete example for a solution for the MPE task.
The evidence file contains one evidence samples.
If a solver does not produce a solution by the given time, it would be considered as having failed on the instance. This will be treated as equivalent to a naive solution (e.g. bit-wise singleton clique maximum for a MAP problem).
Some example problems and outputs are available .
2010 (C) , All rights reservedLTE网络中SIB2（系统消息2）信息详解
SIB2中包含公共的无线资源配置信息，如上行RACH、PUCCH、PUSCH、SRS的资源分配与调度，上行信道功率控制信息；下行BCCH、PDSCH、PCCH信道资源配置等，这些信息对理解当前系统上下行的资源使用及分析网络资源问题有很大帮助。系统消息2主要有三大部分，包括radioResourceConfigCommon（公共无线资源配置信息）、ue-TimersAndConstants（定时器与常量）、freqInfo（频率信息）。除此之外还包含小区接入禁止相关信息。下面结合现网参数设置介绍下相关参数含义。
第一部分：radioResourceConfigCommon（公共无线资源配置信息）
radioResourceConfigCommon：rach-ConfigCommon
............................preambleInfo
..............................numberOfRA-Preambles:n52
(12) 保留给竞争模式使用的随机接入探针个数,PRACH探针共有64。当前参数设置52，表示52个探针用于竞争模式随机接入
..............................preamblesGroupAConfig
................................sizeOfRA-PreamblesGroupA:n28
(6) 组A随机接入探针个数。基于竞争模式的随机接入探针共分2组，A组和B组。当前参数设置28，A组中有28个探针，B组中52-28=24个探针。
................................messageSizeGroupA:b56
(0) 表示随机接入过程中UE选择A组前导时判断msg3大小的门限值/bit。当前参数设置56，即msg3的消息小于56bit时，选择A组。
................................messagePowerOffsetGroupB:dB10
(4) 用于UE随机接入Preamble
B组的选择。默认为10dB。
............................powerRampingParameters
..............................powerRampingStep:dB2
(1) 随机接入过程探针功率攀升步长。当前参数设置dB2，即2dB
..............................preambleInitialReceivedTargetPower:dBm-104
(8) 探针初始接收功率目标.
当PRACH前导格式为0时，在满足前导检测性能时，eNodeB所期望的目标功率水平。当前参数设置-104
dBm，即期望的功率值，用于计算探针的初始发射功率。
............................ra-SupervisionInfo
..............................preambleTransMax:n10
(6) 随机接入探针最大重发次数。当前参数设置10，即最大重发10次
..............................ra-ResponseWindowSize:sf10
(7) 随机响应接收窗口。若在窗口期未收到RAR，则上行同步失败，当前参数设置sf10，即10个子帧长度。
..............................mac-ContentionResolutionTimer:sf64
(7) RA过程中UE等待接收Msg4的有效时长。当UE初传或重传Msg3时启动。在超时前UE收到Msg4或Msg3的NACK反馈，则定时器停止。定时器超时，则随机接入失败，UE重新进行RA。当前参数设置sf64，即64个子帧长度。
............................maxHARQ-Msg3Tx:0x5
(5) Msg3的HARQ最大传输次数.当前参数设置5，即5次。
radioResourceConfigCommon：bcch-Config
............................modificationPeriodCoeff:n2
(0) BCCH信道修改周期系数，该值乘以defaultPagingCycle为UE侦听SI是否修改的周期。但系统消息是否修改还与MIB中tag相关。当前参数设置n2，即系数为2。
radioResourceConfigCommon：pcch-Config
............................defaultPagingCycle:rf128
(2) Idle模式下DRX周期，用于计算寻呼时刻，可实现节电的目的。当前参数设置rf128，即128个无线帧长度。
............................nB:oneT
(2) 表示在一个寻呼周期内包含的寻呼时刻（子帧）的数量，也即寻呼组的数量。可获取N值，用于计算寻呼时刻。当前参数设置oneT，即1倍的寻呼周期。
radioResourceConfigCommon：prach-Config
............................rootSequenceIndex:0x7
(7) 用于生成Signature的逻辑Za-doff序列索引，每一个逻辑索引对应一个物理Zadoff-chu序列。该值一般是按网络规划配置设置的。当前参数设置为7，对应物理Zadoff-chu序列为629.见36.211
Table 5.7.2-4.
............................prach-ConfigInfo
..............................prach-ConfigIndex:0x6
(6) 该值与探针格式一同确定探针频域/时域资源。当前参数设置为6，对应探针格式0，可占用任意系统帧的第1或6子帧资源。见36.211
Table 5.7.1-2.
..............................highSpeedFlag:FALSE
高速移动小区指示。即是否是覆盖高速移动场景，当前参数设置为False，表示非覆盖高速移动场景。
..............................zeroCorrelationZoneConfig:0x2
(2) 零自相关区配置索引。随机接入探针是由具有CAZAC(恒幅零自相关)的Zadoff-chu序列生成的，通过逻辑根序列获取物理根序列，然后对物理根序列进行循环移位获得。零自相关区配置索引与Ncs的选择直接相关。取值范围0～15，当前参数设置为2，即对应Ncs=15（无限集）或Ncs=22（有限集），见36.211
Table 5.7.2-2.
..............................prach-FreqOffset:0x6
(6) &FDD小区的每个PRACH所占用的频域资源起始位置的偏置值。取值范围0=&
prach-FreqOffset ul-rb-6，当前参数设置为6，即在第6个PRB位置。
radioResourceConfigCommon：pdsch-ConfigCommon
............................referenceSignalPower:0xf
(15) 每逻辑天线(port)的小区参考信号的功率值。参数设置值为15，即RS信号功率为15dbm。
............................p-b:0x1
(1) 表示PDSCH上EPRE（Energy
Per Resource
Element）的功率因子比率指示，它和天线端口共同决定了功率因子比率的值，见36.213 Table
5.2-1。P-b实际表征的是有RS的PDSCH符号功率与没有RS的PDSCH符号的功率偏移量。
radioResourceConfigCommon：pusch-ConfigCommon
............................pusch-ConfigBasic
..............................n-SB:0x4
(4) 给定跳频模式下，用于跳频的PUSCH子带个数。该参数与跳频偏置决定了子带的大小，而子带大小与跳频偏置、Vrb数一起决定PUSCH信道PRB的分配。该参数设置为4，即子带数为4.
..............................hoppingMode:interSubFrame
(0) PUSCH跳频模式选择。该参数设置为interSubFrame，表示采用子帧间跳频模式。还有另一种模式为子帧内和间跳频。
..............................pusch-HoppingOffset:0x16
(22) &PUSCH信道的跳频偏置；与FDD/TDD模式、子帧配置、CP长度相关。参与决定PUSCH信道资源分配。
..............................enable64QAM:TRUE
上行PUSHC是否使用64QAM调制方式。CAT5类终端支持。当前参数设置为TRUE，表示上行支持64QAM使用。
radioResourceConfigCommon：ul-ReferenceSignalsPUSCH
..............................groupHoppingEnabled:FALSE
&PUSCH信道的分组跳频开关；Group
hopping作为UL
RS生成base序列组Planning的一种补充，有简化Planning及随机化UL
RS互相关干扰的作用，虽然现有的Group
hopping模式能够大大减小出现碰撞（即相邻小区在一个TTI内使用相同的base序列组）的概率，但却不能避免出现碰撞的情况。
..............................groupAssignmentPUSCH:0x0
(0) PUSCH信道的分组指派；一个eNodeB下所有小区的GroupAssignPUSCH取0时，这些的PUSCH上的UL
RS由不同的base序列组生成，每个小区在生成UL
RS时可以使用全部的CS（Cyclic
Shift）取值，可用的CS越多，能够支持配对的V-MIMO用户越多。
..............................sequenceHoppingEnabled:FALSE
&PUSCH信道的序列跳频开关；当不执行Group
hopping时，允许支持sequence hopping
..............................cyclicShift:0x0
(0) &PUSCH信道的循环移位；当一个eNodeB下的所有小区使用相同的base序列组生成PUSCH上的UL
RS时，为了保证在半静态调度时这些小区使用不同的CS（Cyclic
Shift）取值，需要为这些小区配置不同的CyclicShift取值；
..........................pucch-ConfigCommon
............................deltaPUCCH-Shift:ds1
(0) PUCCH信道的循环移位间隔。在组网时根据环境类型获得小区的平均时延扩展，然后根据小区的平均时延扩展得到PUCCH信道的循环移位间隔。与硬件处理能力相关.
............................nRB-CQI:0x1
(1) FDD小区的RRC层给CQI配置的RB总数。当PUCCH资源调整开关关闭时，CQI
RB个数才能够进行手动配置。参数设置为1，表示1个RB用于承载CQI.该参数定义与36.211
5.4章节描述不一致.规范中定义为不同PUCCH格式下一个Slot可用带宽，即RB数。
............................nCS-AN:0x0
(0) 使用混合PUCCH格式下，用于PUCCH格式1/1a/1B的循环移位数。是delta
PUCCH Shift的整数倍。
............................n1PUCCH-AN:0x12
(18) PUCCH占用RB数索引，表示PUCCH
使用的RB 个数.
radioResourceConfigCommon：soundingRS-UL-ConfigCommon
..............................srs-BandwidthConfig:bw3
(3) SRS带宽配置；见36.211 Table
5.5.3.2-1、Table 5.5.3.2-2、Table
..............................srs-SubframeConfig:sc3
(3) &SRS子帧配置索引；见36.211
Table 5.5.3.3-1、Table 5.5.3.3-2
..............................ackNackSRS-SimultaneousTransmission:TRUE
UE的Sounding
RS和PUCCH的ACK/NACK或SR时域冲突时，是否允许同时发送.
radioResourceConfigCommon：
uplinkPowerControlCommon
............................p0-NominalPUSCH:-0x43
(-67) PUSCH的标称P0值，应用于上行功控过程。与p0-NominalPUCCH含义一致。
............................alpha:al07
(4) 路径损耗补偿因子，应用于上行功控过程；
............................p0-NominalPUCCH:-0x69
(-105) 正常进行PUCCH解调，eNodeB所期望的PUCCH发射功率水平；P0NominalPUCCH设置的过高，会增加本小区的吞吐量，但是会降低整网的吞吐量；P0NominalPUCCH设置偏低，降低对邻区的干扰，导致本小区的吞吐量的降低，提高整网吞吐量。
............................deltaFList-PUCCH
..............................deltaF-PUCCH-Format1:deltaF0
(1) PUCCH格式1的Delta值；用于计算PUCCH信道功率，相当于对每种PUCCH格式补偿值。当前设置值deltaF0，表示0dB。
..............................deltaF-PUCCH-Format1b:deltaF3
(1) PUCCH格式1b的Delta值；当前设置值deltaF3，表示3dB。
..............................deltaF-PUCCH-Format2:deltaF1
(2) PUCCH格式2的Delta值；当前设置值deltaF1，表示1dB。
..............................deltaF-PUCCH-Format2a:deltaF2
(2) PUCCH格式2a的Delta值；当前设置值deltaF2，表示2dB。
..............................deltaF-PUCCH-Format2b:deltaF2
(2) PUCCH格式2b的Delta值；当前设置值deltaF2，表示2dB。
............................deltaPreambleMsg3:0x4
(4) 消息3的前导Delta值。步长为2；当PUSCH
承载Msg3 时，用于计算每个UE的PUSCH
发射功率。
..........................ul-CyclicPrefixLength:len1
(0) 小区的上行循环前缀长度，分为普通循环前缀和扩展循环前缀，扩展循环前缀主要用于一些较复杂的环境，如多径效应明显、时延严重等。当前参数设置为len1，即采用扩展循环前缀。
第二部分：ue-TimersAndConstants（定时器与常量）
........................ue-TimersAndConstants
..........................t300:ms200
(1) RRC连接建立定时器。开始于RRCConnectionRequest发送，在收到RRCConnectionSetup或RRCConnectionReject消息、cell
re-selection或连接放弃后停止，定时器超时后，UE直接进入RRC_IDLE态。参数设置值为200ms。
..........................t301:ms200
(1) RRC连接重建定时器。UE在发送RRCConnectionReestabilshmentRequest时启动该定时器。
定时器超时前，如果UE收到RRCConnectionReestablishment或者RRCConnectionReestablishmentReject或者被选择小区变成不适合小区(适合小区定义参见3GPP
36.331)，则停止该定时器。定时器超时后，UE进入RRC_IDLE态。参数设置为200ms。
..........................t310:ms1000
(5)无线链路失败定时器.在收到底层连续N310个失步指示后启动，若在定时器时间内收到连续N311个同步指示，无线链路恢复，否则定时器超时，即意味着无线链路失败。参数设置值为1000ms
..........................n310:n10
(6) 表示接收到底层的连续"失步"指示的最大数目。
..........................t311:ms10000
(3) 无线链路失败恢复定时器。在RLF后T311时间内进行RRC
connection re-establishment流程，若在定时器内若RRC重建失败，则进行小区重选或者TA更新，UE进入idle状态。
..........................n311:n1
(0) 接收到底层的连续"同步"指示的最大数目。
第一部分：freqInfo（频率信息）
........................freqInfo
..........................ul-Bandwidth:n100
(5) 小区上行带宽。以RB数计量。当前参数设置N100，即100个RB，对应20M带宽。
..........................additionalSpectrumEmission:0x1
(1)附加频率散射，限制UE功率在相应信道带宽内的水平。即用于计算ue的上行发射功率。这个参数对应一个Additional
Maximum Power Reduction (A-MPR)，该值可以计算对应频带的上行发射功率。该参数与Additional
Maximum Power Reduction (A-MPR)的对应关系，见 TS 36.101
Table6.2.4-1和TS 36.521 Table
6.2.4.3-1.当前参数设置值为1，对应NS_01，即A-MPR为NA。
........................timeAlignmentTimerCommon:sf1920
(3) 该参数表示UE上行时间对齐的定时器长度，该定时器超时，则认为UE上行失步。当前参数设置sf1920，即1920个子帧长度。
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。