登录
首页 » Others » 5G网络技术架构

5G网络技术架构

于 2020-12-05 发布
0 506
下载积分: 1 下载次数: 7

代码说明:

主要讲述当前网络挑战与发展趋势,以及网络总体设计和5G网络的功能特是哪个,和关键技术 。最后总结和展望未来AT-2◇21MT202056/推进组5G无线技术架构白皮书引言在过去的三十年里,移动通信经历了从语音多址技术之外,大规模天线、超密集组网和全频业务到移动宽带数据业务的飞跃式发展,不仅深谱接入都被认为是5G的关键使能技术。此外,新刻地改变了人们的生活方式,也极大地促进了社型多载波、灵活双工、新型调制编码、终端直通会和经济的飞速发展。移动互联网和物联网作为(2)、全双工(又称同时同频全双工)等也未来移动通信发展的两大上要驱动力,为第五代是潜在的5G无线关键技术。5G系统将会构建在以移动通信(5G)提供了广阔旳应用前景。面向新型多址、大规模天线、超密集组网、全频谱接2020年及未来,数据流量的千倍增长,千亿设备入为核心的技术体系之上,全面满足面向2020年连接和多样化的业务需求都将对5G系统设计提出及未来的5G技术需求。严峻挑战。与4G相比,5G将支持更加多样化的当前,5G愿景与需求已基明确,概念与技场景,融合多种无线接入方式,并充分利用低频术路线逐步清晰,国际标准制定工作即将启动。和髙频等频谱资源。同时,5G还将满足网络灵为此,迫切需要尽快细化5G技术路线,整合各种活部署和高效运营维护的需求,大幅提升频谱效无线关键技术,形成5G无线技术框架并推动达成率、能源效率和成本效率,实现移动通信网络的产业共识,以指导5G国际标准及后续产业发展。可持续发展传统的移动通信升级换代都是以多址接入技术为主线,5G的无线技术创新来源将更加丰富。除了稀疏码分多址(SCMA)、图样分割多址(PDMA)、多用户共享接入(MUSA)等新型AT-292◇MT2020(5G)推进组5G无线技术架构白皮书场景与技术需求与以往移动通信系统相比,5G需要满足更加低功耗大连接场景主要面向环境监测、智多样化的场景和极致的性能挑战。归纳未来移动能农业等以传感和数据采集为目标的应用互联网和物联网主要场景和业务需求特征,可提场景,具有小数据包、低功耗、低成本炼出连续广域覆盖、热点高容量、低时延高可靠海量连接的特点,要求支持百万/平方公里和低功耗大连接四个5G主要技术场景。连接数密度。·连续广域覆盖玚景是移动通信最基本的覆总之,5G的技术挑战主要包括盖方式,在保证用户移动性和业务连续性0.1-1GbDs的用广体验速率,数十Gbps的的前提下,无论在静止还是高速移动,覆峰值速率,数十Tbυs/km的流量密度,1盖中心还是覆盖边缘,用户都能够随时随百万/平方公里的连接数密度,毫秒级的地获100Mbps以上的体验速率。端到端时延,以及百倍以上能效提升和单热点高容量场景:要面向室内外局部热点位比特成本降低。区域,为用户提供极高的数据传输速率,满足网络极高的流量密度需求。要技术挑战包括 1Gbps用户休验速率、数|Gbps峰值速率和数十Tbps/km的流量密度低时延高可靠场景主要面向车联网、工业控制等物联网及垂直行业的特殊应用需求,为用户提供亳秒级的端到端时延和或接近100%的业务可靠性保证。AT-2◇2M-2020(56推进组5G无线技术架构白皮书5G无线技术路线面对5G场景和技术需求,需要选择合适的5G将通过工作在较低频段的新空口来满足无线技术路线,以指导5G标進化及产业发展。大覆盖、高移动性场景下的用户体验和海量设综合考虑需求、技术发展趋势以及网络平滑演备连接。同时,需要利用高频段丰富的频谱资进等因素,5G空口技术路线可由5G新空口(含源,来满足热点区域极高的用户体验速率和系低频空口与高频空口)和4G演进两部分组成。统容量需求。综合考虑国际频谱规划及频段传LTE/LTE一 Advanced技术作为事实上的播特性,5G应当包含工作在6GHz以下频段的统一4G标准,已在全球范围内大规模部署。为低频新空口以及工作在6GHz以上频段的高频了持续提升4G用户体验并支持网络平滑演进新空口。需要对4G技术进一步增强。在保证后向兼容的5G低频新空口将采用全新的空口设计,前提下,4G演进将以LE/LTE- advanced技引入大规模天线、新型多址、新波形等先进技术梹架为基础,在传统移动通信频段引入增强术,攴持更短的帧结构,更精简的信令流程,技术,进一步提升4G系统的速率、容量、连接更灵活的双工方式,有效满足广覆盖、大连接数、时延等空口性能指标,在一定程度上满足及髙速等多数场景下的体验速率、时延、连接5G技术需求。数以及能效等指标要求。在系统设计时应当构受现有4G技术框架的约東,大规模天线建统一的技术方案,通过灵活配置技术模块及超密集组阏等增強技术的潜力难以完仝发挥,参数来淸足不同场景差异化的技术需求。全频谱接入、部分新型多址等先进技术难以在5G高频新空口需要考虑高频信道和射频器现有技术框架下采用,4G演进路线无法满足5G件的影响,并针对波形、调制编码、天线技术极致的性能需求。因此,5G需要突破后向兼容等进行相应的优化。同时,高频频段跨度大的限制,设计全新的空口,充分挖掘各种先进候选频段多,从标准、成本及运维角度考虑,技术的潜力,以全面满足5G性能和效率指标要应当尽可能采用统一的空口技术方案,通过参求,新空口将是5G主要的演进方向,4G演进将数调整来适配不同信道及器件的特性。是有效补充。髙频段覆盖能力弱,难以实现全网覆盖,需要与低频段联合组网。由低频段形成有效的3AT-22MT2020(5G)推进组5G无线技术架构白皮书网络覆盖,对用户进行控制、管理,并保证基本的数据传输能力;高频段作为低频段的有效补充,在信道条件较好情况下,为热点区域用户提供高速数据传输。5G无线技术路线主要场景连续广域覆盖6-100GHZ5G高频新空口冷热点高容量5G低频新空口低时延高可靠

下载说明:请别用迅雷下载,失败请重下,重下不扣分!

发表评论

0 个回复

  • 机器学习算法源码及讲义.zip
    七月在线-邹博 机器学习源码及讲义(SVM, XGBoost, em算法,LDA, HMM等等)
    2019-09-07下载
    积分:1
  • 报刊订阅管理系统
    报刊订阅管理系统的完整代码,含任务说明,代码实现
    2020-11-30下载
    积分:1
  • UDS诊断序,整车网络测试应用序(PCAN-UDS API – User Manual.pdf)
    UDS_PCAN_APIA应用程序,整车网络诊断应用程序,超值!(PEAK CAN UDS Application Programming InterfaceUser Manual.pdf)PCAN-UDS APi- User ManualContents1 PCAN-UDS API Documentation2 Introduction2.1 Understanding PCAN-UDS2.2 Using PCAN-UDS2.3 Features7888992.4 System Requi rements2.5 Scope of supply3 DLL API Reference3.1 Namespaces103.1.1 Peak Can uds3.2 Units3.21 PuDs Unit3.3 Classes3.3.1 UDSApi3.3.2 TUDSApi3. 4 structures1022334553.4.1 TPUDSMsg3.4.2 TPUDSSessionInfo3.43 TPUDSNetAddrinfo3.5 Types213.5.1 TPUDSCANHand]e223.5.2 TPUDSstatus233.5.3 TPUDSBaudrate253.5.4 TPUDSHWType283.5.5 TPUDSResult303.5.6 TPUDSParameter313.5.7 TPUDSService393.5.8 TPUDSAddress423.5.9 TPUDSCanId443.5.10 TPUDSProtoco l463.5.11 TPUDSAddressingType483.5.12 TPUDSMessageType493.5.13 TPUDSSVCParamDSC503.5.14 TPUDSSVCParamER513.5.15 TPUDSSVCParamcc533.5.16 TPUDSSVCParamTP543.5.17 TPUDSSVCParamcdTCS543.5.18 TPUDSSvCParamROE553.5.19 TPUDSSvCParamROERe commendedserviceID573.5.20 TPUDSSVCParamLC583.5.21 TPUDSSvcParamLCBaudrateidentifier593.5.22 TPUDSSVCParamDI603.5.23 TPUDSSVCParamRDBPI643.5.24 TPUDSSVCParamDDDI653,525 TPUDSSyCParamRDTCI66PCAN-UDS APi- User Manual3.5.26 TPUDSSVCParamRDTCI DTCSVM6935.27 TPUDSSYCParamIOCBI703.5.28 TPUDSSvCParamRC3.5.29 TPUDSSVCParaMRC RID723.6 Methods733.6.1 Initialize753.6.2 Initialize(TpudsCanhandle, tpudsbaudrate)3.6.3 Initialize(TPUdsCANhandle, TPUdSBaudrate, TPudSHWType, UInt32,UInt16)83.6.4 Uninitialize813.6.5 Setvalue843.6.6 Setvalue (TPUdsCanhandle, tpudsparameter, UInt32, uint32)843.6Setvalue (TPUdSCaNHandle, TPUDSParameter, stringBufferUint32)873.6.8 Setvalue (TPUDSANHandle, TPUDSParameter, Byte[], Uint32)883.6.9 Setvalue(Tpudscanhand le, tpudsparameter, IntPtr, UInt32)3.6.10 Getvalue933.6.11 Getvalue (TPUDSCANHandle, TPUDSParameter, StringBufferUint32)933.6. 12 Getvalue (TPUDSCANHandle, tpudsparameter, uint32, Uint32)963.6.13 Getvalue (TPUDsCaNHandle, TPUDSParameter, Byte l], UInt32)993.6. 14 Getvalue (TPUdSCAnhandle, tpudSParameter, Intptr, UInt32)1013.6.15 Getstatus1043.6.16Read1073.6.17 Write3.6.18 Reset1143.6.19 WaitForsing lemessage1163. 6.20 WaitFormultiplemessage1203.6.21 Waitforseryice1263.6.22 WaitForservicefunctional1303.6.23 ProcessResponse1333.6. 24 SvCDiagnosticsessioncontro l1383.6.25 SVCECUReset1413.6.26 SvcSecuri tyAccess1453.6.27 SvCCommunicationControl1483.6.28 SvcTesterpresent1523.6.29 SvcsecuredDataTransmission1553.6.30 SvcControlDTCSetting1583.6.31 SvcResponseonEvent1623.6.32 SVCLinkcontrol1663.6.33 SVCReaddatabyidentifier1703.6. 34 SvcReadMemory ByAddress1733.6.35 SvcReadscal ingdatabyidentifier1773.6. 36 SvcReadDataByperiodicIdentifier1803.6.37 SvcDynamicallydefinedataIdentifierDBID1843.6.38 SvcDynamicall ydefineDataIdentifierDBMA1883.6. 39 SvcDynamical lyDefineDataIdentifierCDDDI1933.6.40 SvcWri teDataByidentifier1973.6. 41 Svcwri teMemory byaddress2003.6.42 SvcClearDi agnosticInformation2053. 6. 43 SVCReadDTCInformation2083.6.44 SvCReadDTCInformationRDTCSSBDTC2113. 6. 45 SvCReaddTCInformationRDTCSSBRN215PCAN-UDS APi- User Manual3. 6.46 SVcReadDTCInformationReportExtended2183.6. 47 SvcReadDTCInformationReportseverity2213,648 SvcReaddTCInformationrsIodtc2253. 6.49 SvCReadDTCInformationNoParam2283.6.50 SvcInputout put contro byidentifier2323. 6.51 SyCRoutineControl2363.6.52 SvCReques tOwn load2393.6.53 SvcRequestUp load2433. 6.54 SVCTransferData2483.6.55 SvCRequestTransferExit2513.7 Functions2563.7.1 UDS Initialize2583.7.2 UDs Uninitialize2593.7.3 UDs Setvalue2603.7.4 UDs Getvalue2613.7.5 UDS Getstatus2623.7.6 UDS Read2643.7.7 UDs Write2653.7.8 UDs Reset2663.7.9 UDS_WaitForsinglemessage2673.7.10 UDS_waitForMultipleMessage2693.7.11 UDs Wai ce2723.7.12 UDS WaitForserviceFunctional2733.7.13 UDS_ Processresponse2753.7.14 UDS_SvcDiagnosticSessionControl2773.7.15 UDS SVCECUReset2783.7.16 DS_SVCSecuri tyAccess2803.7.17 UDS SVCCommunicationcontrol2813.7.18 UDs SvCTesterpresent2833719 UDS SvCSecuredDatatransmission2843.7.20 UDS_SvCControlDTCSetting2863.7.21 UDS_SVCResponseonEvent2873,7.22 UDs SVCLinkcontrol2893.7.23 UDS_SvcReaddatabyidentifier2913.7.24 UDS_SvcReadMemory byAddress2923.7.25 uDs_ SvcReadscalingdatabyidentifier2943.7.26 UDS_SvCReadDataBy Periodi iDentifier2953.7. 27 UDS_SVcDynamical l yDefineDataIdentifierDBID2973.7.28 UDS_SvcDynami call ydefinedataIdentifierDBMa2993.7.29 UDS_SvcDynami cal l yDefineDataIdentifierCDDDI3013. 7.30 UDS_SvcWriteDataByIdentifier3023,7.31 UDs SvcWri teMemorybyaddress3033.7. UDS_SvcClearDiagnosticInformation3053.7.33 UDS SVCReadDTCInformation3073.7. UDs SyCReadDTCInformationRdtCSSBDTC3093.7.35 uDs SvCReadDTCInformationRdtcssbrn3103.7.36 UDS_ SvCReadDTCInformationReportExtended3113.7.37 UDS_SvcReadDTCInformationReportseverity3133.7.38 UDS SVCReadDTCInformationRSIODTC3153,739 UDS SVCReadDTCInformationNoParam3163. 7.40 UDS_SvcInputoutput contro l byIdentifier3,7. 41 UDs SyCRoutinecontrol319PCAN-UDS APi- User Manual3.7.42 UDS_SvcRequestDown load3213.7.43 UDS_ SVCRequestupload32337.44 UDS SyCTransferData3253.7.45 UDS_SVCRequestTransferExit3263.8 Definitions3293.8.1 PCAN-UDS Handle Definitions3293.8.2 Parameter value defintions3313.8.3 TPUDSMsg Member value Definitions3323.8.4 PCAN-UDs Service parameter Definitions3334 Additional Information3354.1 PCAn Fundamentals33542 PCAN-Basic3364.3 UDS and ISO-TP Network Addressing Information3384.3.1 ISO-TP network addressing format3384.4 USing Events3405 License Information3426PCAN-UDS APi- User Manual1 PCAn-UDS APi DocumentationWelcome to the documentation of PCan-UD APl, a PEAK CAN API that implements ISo 15765-3, UDS in CANan international standard that allows a diagnostic tester(client) to control diagnostic functions in an on-vehicleElectronic Control Unit(ECU or serveIn the following chapters you will find all the information needed to take advantage of this aPlIntroduction on page 8DLL API Reference on page 10Additional Information on page 335PCAN-UDS APi- User Manual2 IntroductionPCAN-UDS is a simple programming interface intended to support windows automotive applications that usePEAK-Hardware to communicate with Electronic Control Units(ECU) connected to the bus systems of a car, formaintenance purpose2.1 Understanding PCAN-UDSUDS stands for Unified Diagnostic Services and is a communication protocol of the automotive industry. thisprotocol is described in the norm iSo 14229-1The UDS protocol is the result of 3 other standardized diagnostic communication protocolsIS0 14230-3, as known as Keyword 2000 Protocol(KWP2000L IS0 15765-3, as known as diagnostic on CANISo 15765-2, as known as ISo-TPThe idea of this protocol is to contact all electronic data units installed andCAN OBDninterconnected in a car, in order to provide maintenance, as checking for errors,actualizing of firmware, etcUDS is a Client/Server oriented protocol. In a UDS session(diagnostic session ),aprogram application on a computer constitutes the client(within UDS, it is calledPCAN-UDSTester), the server is the ecu being tested and the diagnostic requests from client toserver are called services. The client always starts with a request and this ends with apositive or negative response from the server(ECuSince the transport protocol of UDS is done using ISo-TP, an international standardPCAN ISOTPfor sending data packets over a CAN Bus, the maximum data length that can betransmitted in a single data-block is 4095 bytes.PCAN-UDS API is an implementation of the Uds on CAN standard the physicalcommunication is carried out by PCAN-Hardware (PCAN-USB, PCAN-PCI etc )throughPCAN-Basithe pCAN-ISo-TP and PCAN-Basic API (free CAN APls from PEAK-System). Because ofthis it is necessary to have also the pCAN-1S0-tP and PCAN-Basic APls(PCAN-ISO-TP. dll and PCAN Basic. dll) present on the working computer where UdS is intended tobe used. PCAN-UDS, PCAN-ISO-TP and PCan-Basic apis are free and available for allFigure 1: Relationship of thepeople that acquire a pCAn-hardware2.2 Using PCAN-UDSSince PCAN-UDS API is built on top of the PCAN-1So-TP API and PCAN-Basic APls, it shares similar functions. Itoffers the possibility to use several PCAn-UDS (PUds) channels within the same application in an easy way. Thecommunication process is divided in 3 phases: initialization interaction and finalization of a puds-channelInitialization In order to do UDS on CAN communication using a channel, it is necessary to initialize it first. Thisis done by making a call to the function UDS_ Initialize (class- method: InitializePCAN-UDS APi- User ManualInteraction: After a successful initialization a channel is ready to communicate with the connected can bus.Further configuration is not needed the 24 functions starting with UDS Svc(class-methods: starting with Svccan be used to transmit UdS requests and the utility functions starting with Uds WaitFor(class- methodsstarting with WaitFor) are used to retrieve the results of a previous request. the Uds read and UDS Write(class-methods: Read and Write are lower level functions to read and write UDs messages from scratch. Ifdesired, extra configuration can be made to improve a communication session, like service request timeouts orISo-TP parametersFinalization: When the communication is finished, the function UDS_ Uninitialize(class-method: Uninitializeshould be called in order to release the puds-channel and the resources allocated for it. In this way thechannel is marked as free"and can be used from other applications23 FeaturesI mplementation of the UDS protocol(iSo 14229-1)for the communication with control unitsWindows DLLs for the development of 32-bit and 64-bit applicationsPhysical communication via Can using a Can interface of the pcan seriesUses the pcan-Basic programming interface to access the can hardware in the computerUses the pCAn-ISo-TP programming interface(iso 15765-2)for the transfer of data packages up to 4095bytes via the can bus2.4 System Requi rementsL- Windows 10, 8.1, 7(32/64-bitAt least 512 Mb ram and 1 GHz CPUPC CAN interface from peak-SystemPCAN-Basic APlL PCAN-SO-TP API2.5 Scope of supplyInterface DLL, examples, and header files for all common programming languagesDocumentation in pdf formatDocumentation in HTML Help formatPCAN-UDS APi- User Manual3 DLL API ReferenceThis section contains information about the data types (classes, structures, types, defines enumerations)andAPI functions which are contained in the pcan-uds api3.1 NamespacesPEAK offers the implementation of some specific programming interfaces as namespaces for the. NEtFramework programming environment. The following namespaces are available:NamespacesNameDescription}PeakContains all namespaces that are part of the managed programming environment fromPEAK-SystemPeak CanContains types and classes for using the PCan aPi from PEAK-SystemPeak Can. LightContains types and classes for using the PCAn-Light API from PEAK-SystemPeak Can basicContains types and classes for using the pcan-Basic APl from PEAK-SystemPeak Can CcpContains types and classes for using the CCP API implementation from PEAK-SystemPeak Can XcpContains types and classes for using the XcP aPi implementation from PEAK-SystemPeak Can. Iso TpContains types and classes for using the pCAN-IS0-TP aPl implementation from PEAKSystelPeak Can, UdsContains types and classes for using the PCan-UDS API implementation from PEAK-SystemPeakCan.Obdll Contains types and classes for using the PCAN-OBDIll API implementation from PEAKSystemt}Peak. LinContains types and classes used to handle with lin devices from PEAK-Systemt}Peak. RP1210AContains types and classes used to handle with can devices from PEak-System through theTMC Recommended Practices 1210, version A, as known as RP1210(A3.1.1 Peak Can UdsThe peak Can. Uds namespace contains types and classes to use the pcan-UdS aPi within the. NET Frameworkprogramming environment and handle pcan devices from peak-SystemRemarks: Under the delphi environment, these elements are enclosed in the puds-Unit. the functionality of allelements included here is just the same. the difference between this namespace and the delphi unit consists inthe fact that delphi accesses the Windows api directly it is not managed code)AliasesAliasDescriptionTPUDSCANHandle Represents a pCAn-UDS channel handleClassesClassDescription像曰UDSApiDefines a class which represents the PCAN-UDS API10
    2020-06-27下载
    积分:1
  • 深信服SCSA库试全套.zip
    深信服SCSA题库试题全套,一整套题库,下载考试必过。。。。
    2020-02-18下载
    积分:1
  • 电力系统分析-对称分量法matlab小
    Matlab对称分量法计算正序负序零序,绘制出向量图,采用MATLAB编写的M文件
    2020-12-02下载
    积分:1
  • 以太网控制器Verilog源码(含有MAC,MII接口)
    【实例简介】以太网控制器Verilog源码(含有MAC,MII接口)
    2021-11-01 00:34:28下载
    积分:1
  • 雷达技术丛书 雷达成像技术
    保铮院士等人著的《雷达成像技术》属于雷达技术丛书系列。本书系统地阐述了星载合成孔径雷达(SAR)和逆合成孔径雷达(ISAR)二维成像的基本理论与技术、信号处理技术、系统总体技术、系统实现及应用,为进一步研究成像雷达奠定较坚实的基础。对初学者入门极具参考价值,推荐给大家
    2020-12-04下载
    积分:1
  • 高斯过 回归
    关于 高斯过程 的全套代码。。里面也有详细说明 有需要请拿去关于 高斯过程 的全套代码。。里面也有详细说明 有需要请拿去
    2020-11-30下载
    积分:1
  • MCGS与三菱PLC通讯(交通灯)
    MCGS与三菱PLC通讯(交通灯).画面还行,里面有演示效果
    2020-11-28下载
    积分:1
  • SecureCRT 8.0 安装包及注册激活图文教
    SecureCRT 8.0,32位和64位操作系统下的英文原版的安装程序+注册机新版本比以前增加了不少功能,而且快捷使用,强力推荐使用。注册激活较图文教程,1)安装好SecureCRT软件,最好先不要运行CRT;2)若正在运行CRT请将其退出,务必保持SecureCRT软件关闭!3)务必用管理员权限运行注册机keygen.exe;4)输入Name、Company(也可以保持默认),点击Generate生成相应的注册信息;5)点击【Patch】按钮,会让你选择文件 ,选择安装目录下的SecureCRT.exe可执行文件,还会再提示一次选择一个LicenseHelper.exe。总之
    2021-05-06下载
    积分:1
  • 696516资源总数
  • 106554会员总数
  • 12今日下载