首页 博客 程序员学院 下载 论坛 问答 代码 直播 电子书 搜CSDN 登录/注册 会员中心 收藏 消息 创作中心

NG Toolset开发笔记--5GNR Resource Grid（3）

zhenggao2 2018-05-26 21:56:26 7877 收藏 5 版权

分类专栏： 4G/5G 文章标签： 5G New Radio 5GNR

5/26号完成如下需求分析：

（3）CRB, Point A, BWP （refer to 38.211/38.213/38.104/38.331)

**Per carrier configurations:

FrequencyInfoDL and FrequencyInfoUL (FreqInfoUL only for FDD/SUL)

l absoluteFrequencySSB defines the center frequency of SSB (sc#0 of #prb10 of SSB, SSB occupies 20prbs in frequency domain)

l absoluteFrequencyPointA in freqInfoDL defines Point-A in DL, which is sc#0 of CRB#0

l absoluteFrequencyPointA in freqInfoUL defines Point-A in UL(for FDD/SUL only), which is sc#0 of CRB#0

However, the actual NR carrier is defined in scs-SpecificCarrier:

l offsetToCarrier defines the actual usable BW w.r.t. the carrier’s Point-A, which is the CRB as defined in 38.211 4.4.2.

l subcarrierSpacing defines scs of the carrier, which is parameter--nrScs in Section 1.3.1

l carrierBandwidth defines N_RB of the carrier, which is parameter---nrBw in Section 1.3.1, which is also the as defined in 38.211 4.4.2.

offsetToCarrier shall have no impact to Resource Grid implementation. Let offsetToCarrier = 0?

Rational as below:

k_SSB is the sc offset from sc#0/crb#0(Point-A) sc#0 of CRB N_SSB_CRB to sc#0 of ssb. Max value of k_SSB is 31.

Is it a valid configuration if offsetTocarrier * 12 * subcarrierSpacing > 32*15K + 12*15*N_SSB_CRB(for type ASSB) or 32*MIB.subCarrierSpacingCommon + 12*60*N_SSB_CRB (for type B SSB)? That’s, SSB lies
outside of the actual usable carrier BW.

2018/6/9 comment: note that, N_SSB_CRB can be configured (Note: It’s NOT the absoluteFrequencyPointA in frequencyInfoDL IE),means that it may not be CRB0.

From one aspect, SSB is carrier level configuration, while BWP is per UE configuration. SSB applies when UE trying to do initial access. After that, UE shall apply BWP setting for all other channels/signals except SSB.

SIB1 is the same as SSB, which is carrier level configuration. After receiving SIB1, UE may be configured a UL BWP, which can be used to send Msg3/Msg5 (I am not very sure about that).

DL BWP is not configured until RrcReconfiguration?(RrcReconfiguration----CellGroupConfig---ServingCellConfigCommon---initialDownlinkBWP). It’s for EN-DC only, I think this issue will be solved in upcoming 2018-
06 specs.

As defined in 38.211 4.4.2, resource grid is given w.r.t. Combination of (antenna port p, scs u, tx direction(UL/DL)).

For simplicity, 5GNR resource grid is defined w.r.t combination of only (antenna port p, tx direction(UL/DL)). The reference scs, refScs, is fixed to 15K for FR1 and 60K for FR2, so that nrScs >= refScs, and actual CRB-
nrScs may occupy multiple CRB-refScs.

Point-A definition in 38.211 4.4.4.2 is a bit confusing. The point is that:

(1) CRB and Point-A(sc#0 of crb#0) is defined w.r.t. a NR carrier.

(2) Point-A is separately defined for UL/DL in case of FDD/SUL, otherwise, Point-A is the same in case of TDD.

(3) Center frequency of SSB is defined separately so that UE can perform initial access.

(4) PRB and VRB is defined w.r.t. a NR BWP(bandwidth part).

**Per BWP configurations:

Definition of BWP in 38.331:

Note: “code points” here simply means available combinations of n bits. For example, certain DCI field is 2bits, so four “code points” in total: 00/01/10/11.

All the important configurations in NR UL/DL are defined either in BWP-DownlinkCommon/BWP-UplinkCommon or BWP-DownlinkDedicated/BWP-UplinkDedicated.

BWP generic parameters:

l locationAndBandwidth defines and by table-lookup. However the table is not specified yet.

l subcarrierSpacing is defined for this BWP, which may be different from the scs of NR carrier

l cyclicPrefix, which is the parameter---nrCp in section 1.3.2

For simplicity, only one BWP (with bwp-index=0) shall be configured.

**SCS summary for initial access:

Ssb scs: blindly decoded by UE?

One exception is NR n41:

15k with case A, and 30k with case C are both supported. However, according to 38.213 4.1, 1st symbol indexs of SSB for both case A and case C are the same.

So basically, UE can’t determine whether scs-ssb is 15k or 30k. It doesn’t affect UE’s behavior since 38.211 7.4.3.1 stats that there are two types of SSB: type A and type B:
举报

点赞1 评论 分享 收藏5 打赏 举报 关注 一键三连

Type A SSB covers both 15k and 30k scs-ssb.

Question: eventually, UE had to determine scs-ssb, since UE need scs-ssb and scs-pdcch to determine type-0 CSS, as specified in 38.213 13. How to determine scs-ssb for NR n41?

2018/6/9 comment: one possible solution is that the detected BW of ssbis different for 15k and 30k.

**Time/Frequency Synchronization during initial access

In general, time synchronization is realized as below:

*UE detects a valid SSB(with its 1st symbol) and determines its ssb-index1 (through dmrs for pbch, and possible payload of pbch--- as specified in 38.212 7.1.1)

*UE detects next valid SSB(with its 1st symbol) and determines its ssb-index2

*from ssb-index1 and ssb-index2, UE can determine the half-frame timing.

Contents of MIB(from PBCH):

And frequency synchronization is realized as below:

*from MIB(PBCH), UE determine k_SSB (k_SSB is the #scs between sc#0 of ssb and point-A sc#0 of CRB N_SSB_CRB, so UE can determine Point-A).

*from k_SSB, UE determine type-0 CSS(common search space)

*UE receive SIB1 (for EN-DC, there is no SIB1, contents of the missed SIB1 are sent to UE via RrcReconfiguration via MCG-LTE RRC signalling)

*when SIB1 is received, UE can determine Point-A, GSCN of SSB, and N_SSB_CRB accordingly. (2018/6/10 comment)

Scs of SIB1/msg2/msg4 is determined from subCarrierSpacingCommon from MIB

**Conclusions:

(1) SIB1 will not be simulated, and will be updated according to upcoming 3GPP specs in 2018-06.

(2) Additional carrier specific parameters:

Carrier specific parameters shall separate UL/DL in case of FDD

l nrCcOpBand: operating band of NR carrier

l nrCcGridStart: as defined by offsetToCarrier of SCS-specificCarrier, value range is: [0, 2199] in PRB

l nrCcGridSize: as defined by carrierBandwidth of SCS-specificCarrier

l nrCcGridScs: as defined by subcarrierSpacing of SCS-specificCarrier

l nrCcSsbScs: subcarrier spacing of SSB, 15K/30K for FR1 and 120K/240K for FR2; should be configured in UI, and determined by UE in live network

(3) Additional BWP specific configurations :

Separate settings for UL/DL in case of FDD

l nrBwpStart: starting position of BWP in PRB

l nrBwpSize: size of BWP in PRB

l nrBwpScs: subcarrier spacing of BWP, 15K/30K/60K for FR1 and 60K/120K for FR2

l nrBwpMu: u of BWP, 0/1/2 for FR1 and 2/3 for FR2

l nrBwpCp: cyclic prefix of BWP

l All other parameters listed in previous‘Frame Structure’ section

(4) SSB specific configurations:

l nrNSsbCrb: the N_SSB_CRB

l nrKSsb: k_SSB, value range is [0,31] for FR1 and [0,15] for FR2

l nrMibScsCommon: as defined by subCarrierSpacingCommon in MIB, 15K/30K for FR1 and 60K/120K for FR2

l nrMibRmsiPdcch: as defined by pdcch-ConfigSIB1 in MIB, value range is [0, 255]

NR: BWP简介1 hzgdiyer的专栏 4091

BWP定义 38.211 4.4.5 中BWP定义： A bandwidth part is a subset of contiguous common resource blocks defined in subclause 4.4.4.3 for a given numerology μ in bandwidth part i on a given carrier. BWP就是CRB其中的连续...

NG Toolset开发笔记--5GNR Resource Grid（10） 2284

PUCCH Requirement Analysis Part IIPUCCH资源确定：如果UE没有dedicatedPUCCH资源配置，则使用SIB1---PUCCH-Resource-Common指示的PUCCH资源来反馈HARQ-ACK。UE最多反馈1bit ACK（只能用format0/1），PUCCH使用frequen…

优质评论可以帮助作者获得更高权重 评论

NG Toolset开发笔记--5GNR Resource Grid（13） 1735

6/27号完成PRACH需求分析Part 1: (refer to 38.211 and TDocs)PRACH支持long sequence（ ）和short sequence（ ）。以下为PRACH设计中的要点：l long PRACH支持Format 0~3，其中NR Format 0复用LTE的Format 0，NR Format...

NG Toolset开发笔记--5GNR Resource Grid（38） 1011

Procedures to parse/make RIV（resource indication value）: def parseRiv(self, riv, N_BWP_Size): div = riv // N_BWP_Size rem = riv % N_BWP_Size L_RBs = [div + 1, N_BWP_...

NG Toolset开发笔记--5GNR Resource Grid(4)_zhenggao2... 10-29

PRACH的OFDM baseband signal generation待后续分析。 OFDM baseband signal generation shall have no impact to 5GNR resource grid。

NG Toolset开发笔记--5GNR Resource Grid(6)_zhenggao2... 10-31

NG Toolset开发笔记--5GNR Resource Grid(6) PUSCH Requirement Analysis Part II 第五步:Precoding 注意这里 是一个1 x 的矩阵,

NG Toolset开发笔记--5GNR Resource Grid（7） 1473

PUSCH Requirement Analysis Part IIIPUSCH频域调度信息：参见38.214，对于RA type0/type1的描述：RA type0仅支持 OFDM-based PUSCH（即pusch-tp=disabled），而RA type1支持pusch-tp=enabled/disabled两种情况。DCI 0_0对应RA typ…

NG Toolset开发笔记--5GNR Resource Grid（5） 1084

6/4～6/7号基本完成PUSCH需求分析，篇幅很长（refer to 38.211/38.212/38.213/38.214/38/331）：PUSCH Requirement Analysis Part IPUSCH/DMRS/PTRS端口号starting with 0SRS端口号starting with 1000PUCCH/DMRS端口号starting with 20…

NG Toolset开发笔记--5GNR Resource Grid(14)_zhenggao... 10-29

NG Toolset开发笔记--5GNR Resource Grid(14) 7/10号完成PRACH需求分析Part II:(refer to 38.211/38.213/38.214/38.331) PRACH资源映射:...

NG Toolset开发笔记--5GNR Resource Grid(9)_zhenggao2... 12-16

PUCCH支持5种Format:Format 0/1/2/3/4。 Format0/1/3/4支持组跳频和循环移位跳频(group/sequence/cyclic shift hopping)。 group/sequence hopping由高层参数puc...

NG Toolset开发笔记--5GNR Resource Grid（8） 3276

6/8完成type 0 CSS需求分析：（refer to 38.211/38.213/38.331）38.2134.1节：如果k_SSB<=23 (FR1)或者k_SSB <= 11(FR2)，则type0 CSS存在。否则，type0 CSS不存在。MIB中的pdcch-ConfigSIB1用于确定type 0CSS的时频域位置：l 4 …

NG Toolset开发笔记--5GNR Resource Grid（2） 2829

5-25号完成需求分析（continue）：（2）Frame Structure（refer to 38.211/38.212/38.213/38.331）**TS38.331 also specified: only 15/30K is supported for FR1 and only 60/120K is supported for FR2. It shall have no impact...

NG Toolset开发笔记--5GNR Resource Grid(50)_zhenggao... 12-16

NG Toolset开发笔记--5GNR Resource Grid(50) ngapp_build20190320放出后,陆续收到反馈:app总是报错,不容易找到valid configuraiton能让工具顺利导出excel。

NG Toolset开发笔记--5GNR Resource Grid(32)_zhenggao... 10-29

inttimeAssignField;//can be 0~15, the value of ‘Msg3 PUSCHTime domain resource assignment’ or ‘Time domain resource assignment’ field ...

NG Toolset开发笔记--5GNR Resource Grid（24） 887

series #23---continued （三）DMRS for PDCCH需求分析 PDCCH DMRS序列生成： PDCCH DMRS资源映射： Proposed parameters as below： *nrCoresetPrecoderGranularity: can be {‘sameAsREG-bundle’, ‘allContiguousRBs’} （...

NG Toolset开发笔记--5GNR Resource Grid（1） 2795

5GNR Resource Grid的开发目前基于3GPP Rel-15（2018-03）规范文本。主要参考的标准文本有：38.104， 38.211/212/213/214，38.321，38.331。5-25号完成以下需求分析：（1）NR operating band和BW配置（refer to 38.104）**FR1和FR2…

©2020 CSDN 皮肤主题: 编程工作室 设计师:CSDN官方博客 返回首页

关于我们 招贤纳士 广告服务 开发助手 400-660-0108 kefu@csdn.net 在线客服 工作时间 8:30-22:00

公安备案号11010502030143 京ICP备19004658号 京网文〔2020〕1039-165号 经营性网站备案信息 北京互联网违法和不良信息举报中心
网络110报警服务 中国互联网举报中心 家长监护 Chrome商店下载 ©1999-2020北京创新乐知网络技术有限公司 版权与免责声明 版权申诉

zhenggao2
码龄16年 暂无认证

134 2万+ 3万+ 9万+

原创 周排名 总排名 访问 等级

2341 209 25 101 77

积分 粉丝 获赞 评论 收藏

私信 关注

搜博主文章

热门文章

NG Toolset开发笔记--5GNR Resource Grid

（3） 7872

NG Toolset开发笔记--5GNR Resource Grid

（8） 3267

NG Toolset开发笔记--5GNR Resource Grid

（14） 2854

NG Toolset开发笔记--5GNR Resource Grid

（2） 2821

NG Toolset开发笔记--5GNR Resource Grid

（1） 2794

分类专栏

Go 21篇

Dev 89篇

举报
Life 2篇

Debian/Linux 2篇

4G/5G 104篇
点赞1 评论 分享 收藏5 打赏 举报 关注 一键三连