Windows 10 上有什么值得推荐的软件？ - 知乎<strong class="NumberBoard-itemValue" title="3被浏览<strong class="NumberBoard-itemValue" title=",017,720分享邀请回答Capslock + E / D / S / F（上 / 下 / 左 / 右）
Capslock + I / K / J / L（上 / 下 / 左 / 右选中文字）
Capslock + W / R（向左 / 右删除文字）
Capslock + A / G（光标向左 / 右跳一个单词，对英文、代码特别有用）
Capslock + ; / P（移动光标至行首 / 行末）
Capslock + U / O（选中光标至行首 / 行末文字）
Capslock + Backspace（删除光标所在行所有文字）
Capslock + Enter（无论光标是否在行末都能新起一个换行而不截断原句子）
此外，Capslock+ 还能实现文本替换、音乐控制、文本翻译、重载程序、转义字符等更多功能，你可以参阅
的帮助文档和少数派之前的这篇文章：当然，AutoHotKey 还有更多好玩的应用，你可以自行搜索体验。如果你是 macOS 用户，也想提高自己的键盘输入效率，可以查阅少数派有关 Keyboard Maestro 的有关文章，相信对你会有帮助。2.3K86 条评论分享收藏感谢收起2.3K349 条评论分享收藏感谢收起3GPP NB-IoT物W技gl展FrY策 智通所魏嘉宏 博士魏嘉宏 Chia-Hung Wei2013/7 ~ now Y工I策M/智慧W通系y研究所/正工程Delegate of 3GPP RAN2 meeting Research Interest: Small cell related Transient performance analysis Random Access procedure2010/9 ~ 2013/1⑻晨萍即W 子工程系 博士 23GPP LTE-M, NB-IoT (R13)LTE-M ? An evolution of LTE optimized for IoT in 3GPP RAN. First released in Rel. 12 in Q4 2014 and further optimization will be included in Rel. 13 with specifications complete in Q1 2016 NB-IOT ? Narrowband operation with 180 kHz bandwidth (in-band, guard band, stand alone) ? DL: OFDMA, UL: FDMA with GMSK modulation and/or SC-FDMA ? Being discussed as part of RAN Rel. 13 standardization starting in Q4 2015 with specifications to be completed by Q2 2016QualComm3Comparison of 3GPP IoT Proposals? ? ? LTE-M, based on LTE evolution EC-GSM, a narrowband solution based on GSM evolution, and NB-LTE, a narrowband cellular IoT solution, also known as Clean Slate technologiesIn October 2015, the 3GPP RAN body mutually agreed to study the combination of the two different narrowband IoT technical solutions, EC-GSM and NB-LTE, for standardization as a single NB-IoT technology, which would support three modes of operation as follows: ? ‘Stand-alone operation’ utilizing, for example, the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, ? ‘Guard band operation’ utilizing the unused resource blocks within a LTE carrier’s guard-band, and ? ‘In-band operation’ utilizing resource blocks within a normal LTE carrier.4Proprietary LPWA and Cellular IoTSigFox and LoRa are both proprietary technologies deployed in the 8-900 MHz license exempt bands. Three separate tracks for licensed Cellular IoT technologies are being standardized in 3GPP5Releases of MTCWorking Item Study ItemR10Machine type communications RP-090991R11R12R13R14RAN technical enhancements for machine-type communications for UTRA and EUTRA. Radio resource allocation/Low mobility consideration/Power saving mechanisms/Ultra-low duty cycle RAN overload control for Machine-Type Communications RP-111373 RAN congestion due to the mass concurrent data and signaling Low Cost MTC for LTE RP-140522 Reduced DL channel BW of 1.4 MHz for data channel in baseband Further LTE Physical Layer Enhancements for MTC RP-150492 Narrowband IOT RP- kHz UE RF BW for DL/UL5G MTC15 dB Coverage improvement for FDD6Progress of NB-IoT in 3GPP until Feb,2016Estimated level of completion of the work/study itemCore part: RAN WG1: RAN WG2: RAN WG3: RAN WG4: 80% 70% 70% 55% 75 %per WG (mandatory to be provided) for Core part or SI:The Core part WI is planned to be 100% complete in:June 2016 September 2016 which is: RAN #72 which is: RAN #73The Performance part WI is planned to be 100% complete in:7Performance objectivesSupport of massive number of low throughput devices Reduced complexity Improved power efficiency Latency8Related Modifications for ProtocolData transfer mode HARQ Mobility UE Capabilities RLF RRC Procedure ? ? ? ? DRX Access Barring System Information Idle mode procedureC Cell Selection and Reselection9NOT supported in NB-IoTInter-rat mobility CSG Dual connectivity Emergency call and CS fallback Sidelink communication/discovery MDTPublic warning functions Interference avoidance for in-device coexistence NAICS Real-time services GBR Measurement reports Handover Relaying MBMS RAN assisted WLAN interworking10Carrier aggregationRadio Protocol AspectsRadio Bearers ROHC PDCP Security ... Security Security ... ROHC ... Security ... Security ROHC ...? ? ?The radio interface protocol architecture MAC, RLC, PDCP, and RRC protocols UE capabilitiesRLCSegm. Segm. ... ARQ etc ARQ etc DTCH DTCHSegm. ... ARQ etc DCCH Logical ChannelsSegm. ARQ etc DTCH...Segm. ARQ etc CCCH BCCH PCCH DCCHSegm.Segm.MCCHMTCHUnicast Scheduling / Priority HandlingMBMS SchedulingMACMultiplexing UE1...Multiplexing UEnMultiplexingHARQ Transport Channels DL-SCHHARQDL-SCHBCHPCHMCHLayer 2 Structure for DLCP Solution, no AS security on DCCH. CP Solution, only one dedicated logical channel per UE (i.e. no priority handling between logical channels of one UE).11Radio Protocol AspectsCP solution: SRB 0 SRB 1no AS security on DCCH (PDCP is not used)CCCH DTCH DTCH DCCH Logical ChannelsRadio Bearers ROHC PDCP Security Security Security ROHCRLCSegm. ARQ etc...Segm. ARQ etcSegm. ARQ etcScheduling / Priority HandlingMACMultiplexingHARQ Transport Channels UL-SCHUP solution: SRB 0 SRB 1 SRB 2 (no motivation) 1 DRBLayer 2 Structure for UL 12HARQBoth DL/UL1-process Stop-And-WaitUL: Asynchronous adaptive HARQDL ACK/NAKs in response to uplink (re)transmissions are sent on NBPDCCH, and uplink re-transimissions are always triggered according to Downlink ACK/NAK on the NB-PDCCH;PHICH NB-PDCCH PUSCH PUSCH NB-PUSCH NB-PUSCHDataACK/NACKreTx Data 13DataACK/NACKreTx DataMobilityKey usage: Stationary UE. Reduce UE complexity and UE power consumption. Not to consider some of the legacy LTE procedures: HO.14UE capability transferUEUE eNBS1-AP: INITIAL CONTEXT SETUP REQUEST &23.401: UE Security Capabilities + 36.331: UE Radio Capability: UERadioAccessCapabilityInformation& S1-AP: INITIAL CONTEXT SETUP RESPONSEEUTRANMMEUECapabilityEnquiryeNB decides if more capabilities are needed, e.g. based on - which other RATs the UE supports - if such neighbour cells are presentRRC: UECapabilityEnquiry &36.331: RAT-Type& RRC: UECapabilityInformation &36.331: RAT-Type + UE-CapabilityRATContainer&UECapabilityInformation&Ue-CapabilityRAT-ContainerList &ueCapabilityRAT-Container UE-NBIOT-Capability &UE-EUTRA-Capability &FeatureGroupIndicatorsFor E-UTRA: the encoding of UE capabilities is defined in IE UE-EUTRA-Capability. For UTRA: the octet string contains the INTER RAT HANDOVER INFO message defined in TS 25.331 [19]. For GERAN CS: the octet string contains the concatenated string of the Mobile Station Classmark 2 and Mobile Station Classmark 3.eNB keeps capabilities during RRC CONNECTED state and builds one UERadioAccessCapabilityInformation message consisting of all known capabilities excluding the UTRAN capabilityS1-AP: UE CAPABILITY INFO INDICATION &36.331: UE Radio Capability: UERadioAccessCapabilityInformation&TS 36.331 [1]MME keeps capabilities until DETACH or ATTACH (see 23.401, 5.11.2)Initial UE Capability Handling15CapabilitiesA new UE capability container in ASN.1 is defined for NB-IoT UEs. Potential fields for the new UE capabilityaccessStratumRelease (FFS if we have it already in Rel-13 or if we add it in a later release) ue-Category (FFS depending on RAN1)(single UE category applicable to DL/UL (i.e. not separate). rf-Parameters (to indicate supported frequency bands, for load balancing, FFS).Do not define or use Feature Group Indicators. Introduce capability For the purpose of MSG3 size determination we assume that we may need to signal a bit for single-tone/multi-tone capability indication, but otherwise (in all other aspects) we consider this FFS.16Data transfer modeRAN2 assumes that the NB-IoT UEs will not use / transfer data using solution 2 and solution 18 [2] at the same time, i.e. both will never be configured by the network at any point in time. The selection which solution to be used is done between UE and network on NAS level.17RLFRadio link monitoring and the associated radio link failure criterion shall be supported by NB-IOT UEs, assuming RAN 1 provides the means of measuring the DL quality. We assume we use the physical channel problem detection mechanism (i.e. N310, T310 and N311) as described in RRC (TS36.331) for NB-IOT (i.e. legacy LTE behaviour). Handle coverage level FFS. Radio link failure criterion (when UE is in connected mode) due to Random Access failure indication from MAC should also be supported. Radio link failure criterion due to maximum RLC retransmissions being reached should also be supported (similar to legacy). Solution 2reestablishment is not supported so the UE would released to Idle.Solution 18it would be possible to do reestablishment (it is FFS if at reestablishment failure the UE would be released to Idle, as for legacy LTE).It is FFS what are the cause values used at the RRC connection release 18RRC ProcedureThe LTE RRC Connection Release procedure to be supported. Other methods for RRC release is FFS. We assume that RRC Connection Reconfiguration is supported for UP solution, for aspects unique to the UP solution. Provision of system information (e.g. SystemInformationBlockType1) via dedicated signalling i.e., within an RRCConnectionReconfiguration message, is not supported in NB-IoT Use C-RNTI as a part of the resume ID. From RRC point of view there are two RRC states i.e. RRC_CONNECTED and RRC_IDLE and when NB-IoT UE is given suspend command the UE moves to RRC_IDLE and transitions to RRC_CONNECTED on resume. Suspend is performed by the RRC release procedure.19Connection control procedures applicableSub-clause 5.3.2 5.3.3 5.3.4 5.3.5 5.3.7 5.3.8 5.3.9 5.3.10 5.3.11 5.3.12 Procedures Paging RRC connection establishment RRC connection resume Initial security activation RRC connection reconfiguration RRC connection re-establishment RRC connection release RRC connection release requested by upper layers Radio resource configuration Radio link failure related actions UE actions upon leaving RRC_CONNECTED UE configured to use &Data transfer over NAS& X X X X X X X UE configured to use &AS context caching& X X X X X X X X X X X20Access BarringOne barring bitmap is used for both MO signaling and MO data. Do not introduce an additional separate flag for MO signaling. Update of AC information does not impact the SI value tag in MIB for general SI (FFS when AC SIB transmission is started / ended). Changes in SIB1 normally affects the SI value tag in MIB. SI for AC can be updated asynchronously to other SI updates When AC is enabled, UE that was barred should not retry, i.e. recheck the SI for AC, too often (for battery consumption reasons), FFS if this is implementation dependent (NAS handles such retries).21System InformationLegacy:MIB:BCCH→BCH 40ms period? NB-IoT:C MIB-nb:? BCCH→BCH ? 640ms period ? all information required to acquire SIB1nbSIBs:BCCH → BCH /DL-SCH (dynamically, SI-RNTI) SIB1: 80 ms period Other SIBs scheduled by SIB1C SIBs:? BCCH → BCH (?) ? SIB1-nb: TBD ms period ? Other SIBs scheduled by SIB1-nbFor NB-IoT, the UE is not required to detect SIB changes when in RRC_CONNECTED, and the network may release the NB-IoT UE to RRC_IDLE if it wants the NB-IoT UE to acquire changed SIB(s).2220 SIBs → 7 SIBsSystem information for NB-IoT is divided into the MasterInformationBlock Cnb (MIB-nb) and a number of SystemInformationBlocks Cnb (SIBs-nb):MasterInformationBlock-nb defines the most essential information of the cell required to receive furthe SystemInformationBlockType1-nb cell access/selection, other SIB SystemInformationBlockType2-nb radio resource confi SystemInformationBlockType3-nb cell re-selection information for intrafrequency, inter- SystemInformationBlockType4-nb neighboring cell related information relevant for intra-frequency cell re- SystemInformationBlockType5-nb neighboring cell related information relevant for inter-frequency cell re- SystemInformationBlockType14- SystemInformationBlockType16-nb GPS time and UTC info.23RRC IdleThis specification is applicable to NB-IoT, except for the following functionality which is not applicable to NB-IoT:Acceptable cell Accessibility measurements Access Control based on ACDC categories (FFS) Camped on Any cell state CSG, including support for manual CSG selection and CSG or Hybrid cell related functionality in PLMN selection, Cell selection and Cell reselection. Emergency call E-UTRA inter-frequency redistribution (FFS) Inter-RAT Cell Reselection Limited service Logged measurements MBMS, including support for MBMS frequency prioritization Mobility History Information Mobility states of a UE Priority based reselection Public warning system including CMAS, ETWS, PWS. RAN-assisted WLAN interworking RSRQ measurements (FFS) Sidelink operation24Cell Selection Criterion SThe UE shall perform ranking of all cells that fulfil the cell selection criterion S Srxlev & 0 AND Squal & 0 is True Candidate CellSrxlev = Qrxlevmeas C (Qrxlevmin + Qrxlevminoffset) C Pcompensation - Qoffsettemp Squal = Qqualmeas C (Qqualmin + Qqualminoffset) - QoffsettempSrxlev Squal Qoffsettemp Qrxlevmeas Qqualmeas Qrxlevmin Qqualmin Qrxlevminoffset Cell selection RX level value (dB) Cell selection quality value (dB) Offset temporarily applied to a cell as specified in [3] (dB) Measured cell RX level value (RSRP) Measured cell quality value (RSRQ) Minimum required RX level in the cell (dBm) Minimum required quality level in the cell (dB) Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMNSIntra SNonIntraintra-frequency measurementswhile camped normally in a VPLMN [5] Qqualminoffset Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]Srxlev & SIntraSearchP and Squal & SIntraSearchQ Srxlev & SnonIntraSearchP and Squal & SnonIntraSearchQinter-frequency measurementsPcompensationIf the UE supports the additionalPmax in the NS-PmaxList, if present, in SIB1, SIB3 and SIB5:max(PEMAX1 CPPowerClass, 0) C (min(PEMAX2, PPowerClass) C min(PEMAX1,PPowerClass)) (dB); else: max(PEMAX1 CPPowerClass, 0) (dB); PEMAX1, PEMAX2 Maximum TX power level an UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in [TS 36.101]. PEMAX1 and PEMAX2 are obtained from the p-Max and the NS-PmaxList respectively in SIB1, SIB3 and SIB5 as specified in TS 36.331 [3]. PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as defined in [TS 36.101]25Cell Selection and Reselectiongo here whenever a new PLMN is selectedgo here whenever a new PLMN is selectedcell information stored for the PLMN1no cell information stored for the PLMNcell information stored for the PLMN1no cell information stored for the PLMNStored information Cell Selection no suitable cell foundno suitable cell foundInitial Cell SelectionStored information Cell Selection no suitable cell foundno suitable cell foundInitial Cell Selectionsuitable cell found2suitable cell found no suitable cell foundsuitable cell found2suitable cell found no suitable cell foundCell Selection when leaving connected modesuitable cell foundCamped normallyNAS indicates that registration on selected PLMN is rejected (except with cause #12, #14 , #15 or #25 [5][16])Cell Selection when leaving connected modesuitable cell foundCamped normallyreturn to idle modeleave idle modetrigger suitable cell foundreturn to idle mode leave idle mode trigger suitable cell foundNAS indicates that registration on selected PLMN is rejected (except with cause #12, #14 , #15 or #25 [5][16])Connected modeCell Reselection Evaluation Processno suitable cell found go here when no USIM in the UEConnected modeCell Reselection Evaluation Processno suitable cell found go here when no USIM in the UEno acceptable cell foundAny Cell SelectionUSIM inserted acceptable cell found2Suitable cell foundAny Cell SelectionUSIM inserted11Cell Selection when leaving connected modeacceptable cell foundCamped on any cellsuitable cell found2[3] TS 36.304return to idle modeleave idle modetrigger acceptable cell foundConnected mode (Emergency calls only)Cell Reselection Evaluation Processno acceptable cell found26RLC SublayerRLC UM is not supported NO Reordering of RLC data PDUs27Channel mappingThe MCH, SL-BCH, SL-DCH and SL-SCH transport channels are not supported and concepts of other transport channels in LTE can be reused as a baseline. The MCCH and SBCCH logical channels are not supported. The MTCH and STCH logical channels are not supported, and the DTCH logical channel is only supported for user plan solution.28Channel MappingMapping between logical channels and transport channelsUplinkCCCHDCCHDTCHUplink Logical channelsCCCHDCCHDTCHUplink Logical channelsRACHUL-SCHUplink Transport channelsRACH UL-SCHUplink Transport channelsLegacyNB-IoT29Channel MappingMapping between logical channels and transport channelsPCCHBCCHCCCHDCCHDTCHMCCHMTCHPCCHBCCHCCCHDCCHDTCHDownlink Logical channelsDownlink Logical channelsPCHBCHDL-SCHMCHDownlink Transport channelsPCHBCHDL-SCHDownlink Transport channelsLegacyNB-IoT30Random AccessUE eNB1Random Access PreamblePerform on anchor PRB; In the procedure to resume the RRC connection:2Random Access ResponseConveys identifier(s) to resume the RRC connection. Note: the identifier(s) is/are FFS.3Scheduled TransmissionIn the procedure to setup the RRC connection:4Contention ResolutionAn indication of the amount of data for subsequent transmission(s) on SRB or DRB can be indicated.31Random AccessA set of PRACH resources (e.g. time, frequency, and preamble sequences) is provided for each coverage level, e.g. a number of preamble sequences for each level. The PRACH resources per coverage level are configurable by System Information. The UE selects PRACH resources based on coverage level given by a UE DL measurement, e.g. RSRP. Do not support contention free RACH / dedicated preambles for Handover or other reconfigurations in this release. The need for contention free RACH in the future or for other purposes, e.g. PDCCH order is FFS. In the SI signalling support it shall be possible to indicate that only a subset of RACH resources are available for contention RACH. FFS the behavior at contention resolution failure (need to check). Global PREAMBLE_TRANSMISSION_COUNTER and per coverage level PREAMBLE_TRANSMISSION_COUNTER_CE are used for NB-IoT Global PREAMBLE_TRANSMISSION_COUNTER is used to achieve power ramping for the received target preamble power 32Random Access ProcedureDL measurement, e.g. RSRPDetermine CE levelPerform RA with CE specific PRACH resourcesFail in preamble transmissionLevel up CE level 33Random AccessMAC contention resolution timer for NB-IoT is configured perCEL [4]. The MAC will reattempt at a higher coverage level if it does not receive RAR after the allowed number of attempts of a certain level. If the Contention Resolution is considered not successful the UE should continue in the same PRACH CE level to proceed to the transmission of preamble. NB-IoT supports only cross-subframe scheduling and no samesubframe scheduling The transmission duration in number of sub-frames for the NBPDCCH, the NB-PDSCH and the NB-PUSCH is variable34DRXWe confirm that at least the legacy parameters drxStartOffset, longDRX-Cycle and OnDurationTimer are re-used as is for connected mode DRX with value ranges suitable for NB-IoT Connected mode DRX configuration parameters for NB-IoT can be included as part of RRC message in MSG 4. The LTE legacy DRX (timers, triggering conditions, etc.) is reused as baseline. Maximum value of the DRX cycleLegacy: longDRX-Cycle sf radio frameeMTC/eDRX: 2621.44 seconds (43.69 minutes). NB-IoT: 10485.76 seconds (2.91 hours).35DRXRunning CR for TS 36.300X.4.2.4 DRX in connected mode DRX in connected mode is supported, but only one DRX cycle, i.e. &long DRX& is supported. Further signalling optimization is not precluded. It is beneficial to enable DRX also for short connections, as early as possible.Parameters in legacy LTE and eMTC (excluding the short DRX parameters):onDurationTimer drxStartOffset (signaled as longDRX-CycleStartOffset in 36.331) longDRX-Cycle (signaled as longDRX-CycleStartOffset in 36.331) drx-InactivityTimer HARQ-RTT-Timer drx-RetransmissionTimer36DRX???*Timer drx-InactivityTimer DCI-1 SRB/ DRBHARQ-RTT-TimerDLNBNBPDCCH PDSCH NBNBPUSCH RACHDCI-1SRB/ DRBNo NB-PDDCH =& DRX sleep NACK ACKULLegacy LTE DRX behavior for one DL HARQ re-transmission [5] ???*Timer drx-InactivityTimer DCI-0 DCI-0/ NACK No NB-PDDCH =& DRX sleepDLNBNBPDCCH PDSCH NBNBPUSCH RACHHARQ-RTT-Timer*HARQ-RTT-Timer*drx-RetransmissionTimer*ULSRB/ DRBSRB/ DRB*not used in legacy as HARQ is synchronousLegacy LTE DRX timers applied for one UL HARQ re-transmission [5] 37Multi-carrier operationIn-band, guardband and standalone are supported. RRC_IDLECamps on the carrier on which it has received NPSS/NSSS, NPBCH and SIB transmissions.RRC_CONNECTEDcan be configured, via UE-specific RRC signaling, to a PRB, for all unicast transmissions, different than the NB-IoT carrier on which the UE has received NPSS/NSSS, NPBCH and SIB transmissions.If the different PRB is not configured for the UE, all transmissions occur on the NB-IoT carrier on which the UE has received NPSS, NSSS, NPBCH and SIB transmissions. The UE is not expected to receive NPBCH, and NPSS/NSSS and any transmissions other than unicast transmissions in the configured PRB.Note: Receives paging on an anchor carrier. 38SchedulingScheduling information for downlink data is transmitted on a downlink physical control channel denoted NBPDCCH. The scheduled downlink data is transmitted on shared data channels denoted NB-PDSCH; Only cross-subframe scheduling is supported. The transmission duration in number of sub-frames for the NBPDCCH and the NB-PDSCH The transmission duration in number of sub-frames is semi-static for the NB-PDCCH and is indicated for the NBPDSCH as part of the scheduling information transmitted on the NB-PDCCH; The start time of the NB-PDSCH relative to the NBPDCCH is signaled as part of the scheduling message.39Cell ReselectionBased on cell reselection criteria which involve measurements of the serving and neighbor cells as follows:Intra-frequency reselection is based on ranking of cells Inter-frequency reselection is based on raking of frequenciesBlind redirection supported for load balancing.403GPP Rel. 14Further Enhancements LTE Device to Device, UE to Network Relays for IoT and WearablesRP-160677 New SI proposal on Further Enhancements LTE Device to Device, UE to Network Relays for IoT and Wearables41References[1] 3GPP R2-.331 Running CR to capture agreements on NB-IoT [2] 3GPP TR 23.720 Architecture enhancements for Cellular Internet of Things [3] 3GPP TS 36.304 User Equipment (UE) procedures in idle mode [4] 3GPP R2-.321 running CR to capture agreements on NB-IoT [5] 3GPP R2-160471 Connected Mode DRX for NB-IoT42Appendix43Control Plane SolutionCIoT MO small data transmissionUE CIoT-BS C-SGNRoaming ScenariosCIoT MT small data transmissionUE CIoT-BS C-SGNRoaming ScenariosP-GWP-GW0. Attach0. Attach 1. Small Data Packet1. RRC Connection Establishment with NAS PDU transmission & Ack/Rsp Ind2c. Service RequestChecks integrity protection, decrypts data 3. Small Data Packet4. Small Data PacketIntegrity protection, encrypts data5. Small Data Packet6. Small Data Delivery, RRC connection release44User Plane SolutionLegacy idle to connected transition connection setup45RRC Suspension procedure for solution 18UE eNB UL data DL data MME SGW1: eNB decides to Suspend the RRC Connection 2: S1-AP UE Ctxt Deactive 3: Release Access Bearer Req 4: Release Access Bearer Resp 5: S1-AP UE Ctxt Deactive Ack 6: MME enters &#39;ECM-IDLE&#39; 7: RRC Connection Suspend (Resume Id) 8: UE enters &#39;RRC-IDLE&#39; and &#39;ECM-IDLE&#39;http://msc-generator.sourceforge.net v4.546RRC Resumption procedure for solution 1847Resumption of a previously suspended RRC connection for MT case4849