3GPP规范-R15-TS38系列NR38331-f00

合集下载

3GPP标准

3GPP标准

AgilentE1963A W-CDMA Mobile Test ApplicationFor the E5515C (8960) Wireless Communications Test Set Technical OverviewSpeed UMTS test plan development and get your devices to market sooner, while ensuring compliance with TS34.121 test standards.The E1963A W-CDMA Mobile Test Application, when used with the Agilent GSM, GPRS, and EGPRS applications, is the industry standard for Universal Mobile Telecommunications (UMTS) mobile test. Agilent’s 8960 (E5515C) test set provides you with a single hardware platform that covers all the UMTS/3GPP (Third Generation Partnership Project) radio formats: W-CDMA, HSPA, GSM, GPRS, and EGPRS.Exceed your calibration test time goals with the E1999A-202 fast device tune measurement. Simultaneously calibrate your device’s transmitter (Tx) output power and receiver (Rx) input level across level and frequency. E1999A-202 is a superset of the discontinued E1999A-201. It not only offers the equivalent capabilities of theE1999A-201, but is also further enhanced to reduce the calibration test times for W-CDMA, cdma2000®, and 1xEV-DO wireless devices with smaller step size support (10 ms step size versus 20 ms step size).Reach your high-volume production goals by moving prototypes quickly into production with this test solution’s fast and repeatable measurements, accurate characterization, and ease of programming. The HSPA, W-CDMA, GSM, GPRS, and EGPRS product combination delivers a complete and integrated UMTS test solution in a single box. FM radio source, a single channel GPS source (E1999A-206) and PESQ measurement (E1999A-301) are also added into the test box for FM radio receiver calibration, GPS receiver calibration and audio quality test without the need of an external audio analyzer. This fast, one-box approach simplifies your production process and increases your production line effectiveness. With the most complete test functionality for 3GPP TS34.121 Section 5 and 6 tests, E1963A Options 403,405 and 413 provide fast, flexible measurements and options in user equipment (UE) connectivity, giving design and manufacturing test engineers more flexibility in creating test plans and the assurance that designs meet technology standards. The option 423 supports 64QAM downlink modulation and RB test mode connection.Key Capabilities•Fast device calibration across level and frequency simultaneously•Test HSPA devices as defined in 3GPP TS34.121•Switch between HSPA sub-test conditions while on an active connection•Test all UMTS technologies with one connection maintained throughout•Test all frequency bands I through XIV•FM and GPS receiver calibration in one box•Test vocoder speech quality using the industry standard PESQ algorithmTx measurements W-CDMA HSDPA HSUPA Thermal power Yes Yes Yes Channel power Yes Yes Yes Adjacent channel leakage ratio Yes Yes Yes Waveform quality Yes Yes Yes Spectrum emission mask Yes Yes Yes Phase discontinuity Yes Yes Yes Inner loop power Yes Occupied bandwidth Yes Yes Yes Code domain power Yes Yes YesIQ constellation Yes Yes- YesTx on/off power Yes Yes Yes Frequency stability Yes Yes Yes Dynamic power analysis Yes Yes YesTx dynamic power YesSpectrum monitor Yes Yes YesRx measurements W-CDMA HSDPA HSUPA Loopback BER Yes N/A N/A BLER on DPCH (W-CDMA)Yes N/A N/A HBLER on HS-DPCCH (HSDPA)N/A YesN/A3GPP TS 34.121 Adherence3GPP TS34.121 Testdescription E1963A5.2 Maximum output power Yes(Release 5 only)5 5.2AA Maximum output power with HS-DPCCH(Release 6 and later)Yes55.2B Maximum output power with HS-DPCCH and E-DCHYes5 5.2C UE-relative code-domain power accuracy Yes5DPCCH and E-DCH55.3 Frequencyerror Yes5.4.1 Open loop power control Yes5.4.2 Inner loop power control Yes5.4.3 Minimum output power Yes5.4.4 Out-of-sync handling of output power E6703X2 5.5.1 Transmit off power Yes5.5.2 Transmit on/off time mask Yes5.6 Change of TFC E6703X5.7 Power setting in UL compressed mode5.7A HS-DPCCH Yes55.8 Occupied bandwidth (OBW)Yes5.9 Spectrum emission mask (SEM) Yes5.9A Spectrum emission mask with HS-DPCCH Yes5 5.9B Spectrum emission mask with E-DCH Yes5 5.10 Adjacent channel leakage power ratio (ACLR) Yes5.10A ACLR with HS-DPCCH Yes5 5.10B ACLR with E-DCH Yes5 5.11 Spuriousemissions Yes2 5.12 Transmitintermodulation Yes3 5.13.1 Error vector magnitude (EVM) Yes5.13.1A Error vector magnitude (EVM) with HS-DPCCH Yes5 5.13.1AA EVM and phase discontinuity with HS-DPCCH Yes5 5.13.2 Peak code domain error Yes5.13.2A Relative code domain error with HS-DPCCH Yes5.13.2B Relative code domain error with HS-DPCCH andE-DCHYes5.13.3 Phase discontinuity measurement Yes3GPP TS34.121 Testdescription E1963A/ E6703X6.2 Referencesensitivity Yes6.3 Maximum input level Yes 6.3A Maximum input level for HS-DPCCH reception(16QAM)Yes56.4 Adjacent channel selectivity (ACS)(Release 99 and Release 4)Yes1 6.4A ACS (Release 5 and later releases) Yes16.5 Blockingcharacteristics Yes16.6 Spuriousresponse Yes16.7 Intermodulationcharacteristics Yes16.8 Spuriousemissions Yes21 Requires use of external source2 Requires use of external spectrum analyzer3 Requires use of external spectrum analyzer and source4 Internal fading is possible using Baseband Studio. Most of these tests require external instrumentation such as faders. Consult TS34.121 for details.5 Requires Feature option license 3GPP TS34.121Test description E1963A7.2Demod in static propagation Yes7.3Demod in multi-path E6703X47.4Demod in moving channel E6703X47.5Demod in birth-death E6703X4What to Order for W-CDMA/HSPAModel number DescriptionE5515C8960 Series 10 Wireless Communications Test SetE5515C-003Flexible CDMA base station emulatorE1963A W-CDMA mobile test applicationE1963A-403HSDPA test modesE1963A-405E1963A-413HSDPA 14.4Mbps TMHSUPA test modesE1963A-423HSPA+ test modesWhat to Order for UMTSModel number DescriptionE5515C8960 Series 10 Wireless Communications Test SetE5515C-002Second RF sourceE5515C-003Flexible CDMA base station emulatorE1963A W-CDMA mobile test applicationE1963A-403HSDPA test modesE1963A-405HSDPA 14.4Mbps test modeE1963A-413HSUPA test modesE1963A-423HSPA+ test modesE1968A-202GSM/GPRS/EGPRS mobile test applicationE1987A Fast switching test applicationFeature Options List for W-CDMA/HSPA Model number DescriptionE1963A-401End-to-end videoE1963A-402Video loopbackE1963A-403HSDPA test modesE1963A-405HSDPA 14.4Mbps test modeE1963A-408Enhanced Audio (real-time vocoder, WB-AMR, DAI) E1963A-409Adv. SMSE1963A-413HSUPA test modesE1963A-423E1999A-202E1999A-206E1999A-301HSPA+ test modesEnhanced fast device tune measurementSingle channel GPS sourcePESQ MeasurementRelated LiteratureE1963A W-CDMA Test Application, photocard, 5989-3414ENAgilent 8960 Wireless Communications Test Set HSPA Applications, photocard, 5989-7515EN8960 Series 10 Wireless Communications Test Set, configuration guide, 5968-7873EFor More InformationLearn more about the E1963A test application and HSPA Options at:/find/E1963AFor details on the manufacturing test solutions visit:/find/8960mfg Technical SpecificationsThese specifications apply to an E5515C mainframe with Option 003 (or E5515B/T upgraded to equivalent configuration) when used with the latest E1963A test application or the E1987A test application.Specifications describe the test set’s warranted performance and are valid for the unit’s operation within the stated environmental ranges unless otherwise noted. All specifications are valid after a 30-minute warm-up period of continuous operation.Supplemental characteristics are intended to provide typical, but non-warranted, performance parameters that may be useful in applying the instrument. These characteristics are shown in italics and labeled as “typical” or “supplemental.” All units shipped from the factory meet these typical numbers at +25 °C ambient temperature without including measurement uncertainty. What Included in This Technical OverviewThis data sheet is organized in four sections:•HSPA Specifications•W-CDMA Specifications•HSPA and W-CDMA Common Technical Specifications •General SpecificationsHSPA/HSPA+ Specifications(E1963A Option 403, 405, 413 and 423)Call connection typesHSPA FDD test modeHSPA FDD test modes are supported by the E1963A. FDD test mode provides Layer 1 functionality only. No higher-level signaling is provided or accepted. No higher-level call processing operations are performed. The test set assumes that the user has appropriately configured the UE.FDD test mode allows you to test the parametric performance of your UE’s transmitter and receiver without call processing. In FDD test mode, the test set does not send any signaling information on the downlink. Rather, it continuously generates a downlink signal and searches for a corresponding uplink signal. The UE must synchronize to the downlink signal and send an appropriate uplink signal, which the test set uses to measure the UE’s transmitter and receiver performance. Any changes to the UE configuration must be accomplished by directly sending commands to the UE from a system controller through a proprietary digital interface./rfcomms/refdocs/wcdma/ wcdma_gen_bse_fddtest.phpFRC H-Set supportH-Set Modulation Nominal avg. inf. Bit rate (Mbps)2 QPSK, 16QAM 0.801, 1.1663 QPSK, 16QAM 1.601, 2.3324 QPSK 0.5345 QPSK 0.8016 QPSK, 16QAM 3.219, 5.6898 64QAM 13.25210 QPSK, 16QAM 4.68, 8.774HSPA RB test modeRB test mode uses signaling to establish a test control connection between the test set and UE, allowing you to test the parametric performance of your UE’s transmitter and receiver. In RB test mode, the test set provides signaling to establish a connection between the UE and the test set. The test set can also signal the UE to change its configuration and alter the uplink signal. The test set measures the uplink signal to determine the UE’s transmitter and receiver performance. RB test mode is operated on the downlink, simultaneously supporting a symmetrical RMC (Reference Measurement Channel) of 12.2 kbps. This symmetrical RMC is typically used for transmitter testing and receiver testing using BER./rfcomms/refdocs/wcdma/ wcdma_gen_bse_hsdpa_rbtest_setup.php HSPA handoversTo support the HSPA tests and sub-test conditions specified in the 3GPP standards, the Transport Channel Reconfiguration procedure allows you to change HSPA parameters while on a live connection. βc, βd, ∆ACK,∆NACK, ∆CQI, CQI feedback cycle (k), CQI repetition factor, Ack-Nack repetition factor, and default DPCH offset (DOFF) parameters can all be modified without dropping the HSPA connection. In addition, when using the user-defined DL configuration for HSDPA in RB test mode, the number of HARQ processes and UE IR buffer size can be changed on a live HSDPA connection to provide flexibility in testing multiple configurationsThe Radio Bearer Reconfiguration allows you to handover from a CS Domain or CS/PS Domain HSDPA RB Test Mode connection or HSPA RB Test Mode connection to a (non-HSDPA/non-HSPA) symmetrical RMC. The Radio Bearer Reconfiguration also allows you to change many other network parameters as part of the reconfiguration.You can also hand over between channels within a band and between bands using the Physical Channel Reconfiguration procedure. This allows you to test channels in the low, middle, and high frequency portions of each UE-supported band without dropping the HSPA connection./rfcomms/refdocs/wcdma/ wcdma_gen_call_handoffs.phpInter-system handoversAlmost all UEs support multiple formats today. To speed the process of testing multiple formats with call processing, you can perform handovers from HSPA to GSM and from HSPA to W-CDMA. If your test plan requires testing HSPA followed by GSM, GPRS, and/or EGPRS, you can hand over from an HSPA FRC to GSM test mode using the system handover. If your test plan requires testing W-CDMA as well, you can hand over from an HSPA FRC to a W-CDMA RMC, then use the existing W-CDMA RMC to GSM test mode system handover to test GSM, GPRS, and/or EGPRS./rfcomms/refdocs/wcdma/ wcdma_gen_call_handoffs.phpHSDPA user-defined downlinkVerify your device’s HSDPA throughput at the MAC-hs level with the user-defined downlink (DL) in the E1963A Option 403 and 405. Flexibly configure the 8960 to provide up to a 14.4 Mbps Radio Bearer (RB) test mode signal for testing HS-DSCH category 9 and 10 devices by setting the number of active HS-PDSCHs, transport block size index, modulation type, inter-TTI, number of HARQ processes, and UE incremental redundancy (IR) buffer size. HSPA+ option supports DL 64QAM and throughput is up to 21 Mbps./rfcomms/refdocs/wcdma/ wcdma_gen_bse_hsdpa_rbtest_setup.phpHSPA RF generatorW-CDMA channels active in HSPA modeW-CDMA(spread factor) Default assignmentAlternate choicesP-CCPCH (256) 1 --PICH (256) 16channel code settable within available coderangeDPCH, 12.2 kpbs RMC(128)20 HSDPA within available coderangeHS-SCCH-2 (128) 6 HS-SCCH-3 (128) 9 HS-SCCH-4 (128) 10 HS-PDSCH (16) 7OCNS HSDPA (128)122, 123, 124, 125, 126, 127HSUPA within available coderangeE-HICH (128) 22 E-RGCH (128) 22Common pilot channel relative level: -20 to 0 dBPrimary CCPCH relative level: -20 to 0 dB PICH relative level: -20 to 0 dBDPCH relative level : settable from -30 to 0 dB with 0.01 dB resolutionHS-SCCH relative level of individual code channels:HS-SCCH channel can be off but at least one channel is in presence. For 64QAM downlink, at least two channels are in presence. the channel level is settable from -20 to 0 dB HS-PDSCH relative level of all active code channels: settable from -20 to 0 dBPrimary sync channel relative level: always the same as P-CCPCHDownlink CDMA modulationModulation type: QPSK,16QAM and 64 QAM per 3GPP standard QPSK residual EVM : < 10%, typically < 3%QPSK carrier feed through: < -25 dBc , typically < -35 dBc nominal ambient performance: < -45 dBc 16QAM residual EVM: typically < 3%16QAM carrier feed through: typically < -35 dBc nominal ambient performance: < -45 dBcOCNS – orthogonal channel noise sourceComposed of 6 channels per Table E.5.5 in Annex E of 3GPP 34.121. OCNS channel can be off but at least 1 OCNS channel is in presence.OCNS channel relative level range: automatically calculated from other code channel relative levels to provide thecomposite W-CDMA cell power, but user-allocated channel level available./rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.php#BCGCBAHEHSPA RF analyzer (measurements only) Real-time demodulation of: uplink– DPCH, HS-DPCCH, E-DCHTx measurementsChannel power measurementMeasurement bandwidthRRC filter off: measured with a bandwidth greater than (1 + α) * chip rate, where α = 0.22 and chip rate = 3.84 McpsRRC filter on:measured with a filter that has a root-raised cosine(RRC) filter response with roll-off α = 0.22 and a bandwidth equal to the chip rate 3.84 MHz BW centered on the active uplink channel)Measurement range:-61 to +28 dBm/3.84 MHzMeasurement interval: settable from 0.01 to 12 msMeasurement accuracy (at + 10 °C from the calibration temperature):< ±1.0 dB (typically < ±0.5 dB) for measurement intervals of 333 µs to12 ms over 698 to1024 MHz, 1400 to 1500 MHz and 1700 to 2000MHz< ±1.0 dB (typically < ±0.55 dB) for measurement intervals of 333 µs to12 ms over 2480 to 2580 MHz,< ±1.0 dB (typically < ±0.6 dB) for measurement intervals of 67 to < 333 µs over 698 to1024 MHz, 1400 to 1500 MHz and 1700 to 2000 MHz Measurement triggers: auto, immediate, protocol, RF rise, external, and HS-DPCCH/rfcomms/refdocs/wcdma/ wcdma_meas_chanpow_desc.php Phase discontinuityMeasurement method: the measured results include the phase discontinuity (defined as the phase difference of adjacent timeslots) as well as all waveform quality results for each timeslotInput power level range:Phase discontinuity: -61 to +28 dBm/3.84 MHzOther measurements: -25 to +28 dBm/3.84 MHzInput frequency ranges: 800 to 1000 MHz, 1700 to 1990 MHz Phase discontinuity range: ±180 degreesEVM range: 0 to 35% rmsPhase discontinuity measurement accuracy:< ±2.4 degrees (typically < ±1.7 degrees) for input levels of -25 to +28 dBm/3.84 MHz< ±2.6 degrees (typically < ±1.9 degrees) for input levels of -51 to < -25 dBm/3.84 MHzOther reported parameters with phase discontinuity: all measurements found in the waveform quality measurement are also available; the specifications are the same in both measurements, including the input power range of the waveform quality measurement Measurement interval: 617 µs (= 1 timeslot (667 µs) – 25 µs transient periods at either side of the nominal timeslot boundaries) or 283 µs (0.5 timeslot (333 µs) – 25 µs transient periods at either side of the nominal timeslot boundaries)Measurement triggers: protocol, external, and HS-DPCCH Temperature range: +20 to +55 °CConcurrency capabilities: phase discontinuity measurements cannot be made concurrently with other measurements/rfcomms/refdocs/wcdma/ wcdma_meas_wpdiscon_desc.phpWaveform quality measurement (HSDPA)Waveform quality measurement: composite EVMMeasurement format:HPSKMeasurement chip rate: 3.84 McpsInput level range: -25 to +28 dBm/3.84 MHzMeasurement range: < 35% EVMMeasurement interval: 0.5 to 1.0 timeslot with choice to include orexclude 25 µs transient periodsEVM measurement accuracy (including the effects of residualEVM):EVM measurement accuracy:< 2.8% rms, typically < 2.4% rms for UE EVM > 1% rms, < 2200 MHz< 3.2% rms, typically < 2.8% rms, for UE EVM > 1% rms, 2300 to 2580MHzMeasurement triggers: auto, protocol, immediate, external, and HS-DPCCHHS-DPCCH trigger alignment:adjustable oversubframes 0 to 5timeslots Ack Nack or CQIsubslots 0 to 0.5 timeslotOther reported parameters with EVM:•frequency error•magnitude error•phase error•origin offset•timing error•peak code domain errorFrequency error measurement range: ±1 kHzResidual frequency error:< ± (5 Hz + timebase accuracy) for a measurement interval of 1timeslot< ±(7 Hz + timebase accuracy) for a measurement interval of 0.5timeslotFrequency error measurement accuracy:Peak code domain error accuracy:< ±0.4 dB for code power levels > -25 dBTiming error measurement range: ±10 µsTiming error measurement accuracy: < ±0.5 chips (±130 ns)/rfcomms/refdocs/wcdma/wcdma_meas_wfrmqual_desc.php#CIHBBHDJIQ tuningAll measurements found in the waveform quality measurementare also available in the IQ tuning measurement; thespecifications are the same in both measurements./rfcomms/refdocs/wcdma/wcdma_meas_iqtuning_desc.phpHSPA Code domain powerCode domain power accuracy:< ±0.4 dB for code power level > -25 dBRelative code domain error (RCDE) accuracy:< ±0.5 dB for RCDE level > -20 dBRelative code domain power accuracy (RCDPA):< ±0.2 dB for code power level from ≥ -10 to 0 dB< ±0.3 dB for code power level from ≥ -15, -10 dB< ±0.4 dB for code power level from ≥ -20, -15 dBAll measurements found in the waveform quality measurement are also available in the code domain measurement; the specifications are the same in both measurements.Measurement triggers: immediate, protocol, external, auto, HS-DPCCH and Even Frame/rfcomms/refdocs/wcdma/ wcdma_meas_cod_dom_desc.phpAdjacent channel leakage ratio (ACLR) Measurement method:ratio of the filtered mean transmitted power to the filtered mean power in an adjacent channel; both the transmitted and the adjacent channel powers are measured with a filter that has a RRC response with roll-off α = 0.22 and a bandwidth equal to the chip rateInput power level range: +5 to +28 dBm/3.84 MHzInput frequency ranges: 698 to 1000 MHz, 1400 to 1500 MHz, 1700 to 2000 MHz, and 2480 to 2580 MHz,Measurement level ranging: autoMeasurement accuracy: < +0.8 dB (typically < +0.5 dB), including the effects of the residual floor, for measurements at -33 dBc at +5 MHz offsets and -43 dBc at +10 MHz offsets, and +10 °C from the calibration temperatureResidual ACLR floor: < -48 dBc for +5 MHz offsets, < -58 dBc for +10 MHz offsetsMeasurement triggers: auto, protocol, immediate, external, HS-DPCCH Trigger alignment: adjustable over subframes 0 to 5 Measurement interval: 1 timeslotMeasurement result: dBc relative to in-channel transmitted power /rfcomms/refdocs/wcdma/ wcdma_meas_aclr_desc.php Dynamic power analysisMeasurement method: graphical display of the uplink power waveform including HS-DPCCH, DPCH versus time; by using the HS-DPCCH trigger source, results will be aligned to the HS-DPCCHInput power level range: -61 to +28 dBm/3.84 MHz Measurement level ranging: autoData capture range: combination of number of steps and step length cannot exceed 58.26 msMeasurement bandwidth: selectable RRC filter on or offMeasurement interval: settable from 0.01 to 12 ms (must be less than or equal to the step length)Measurement accuracy: (at +10 °C from calibration temperature with measurement interval 333 µs to 12 ms):Input level range Measurement accuracy Frequency range < 25 dBtypically < ±0.5 dB 1700 to 2000 MHz< ±1.0 dB,typically < ±0.55 dB 2480 to 2580 MHz < 35 dBtypically < ±0.55 dB 1700 to 2000 MHz< ±1.0 dB,typically < ±0.6 dB 2480 to 2580 MHz< 40 dB typically < ±0.55 dB1700 to 2000 MHz< ±1.0 dB,typically < ±0.7 dB2480 to 2580 MHz Measurement triggers: RF rise, external, and HS-DPCCHHS-DPCCH trigger alignment:adjustable over subframes 0 to 5 /rfcomms/refdocs/wcdma/ wcdma_meas_wdpanalysis_desc.phpSpectrum emission mask (SEM)Measurement method: ratio of the transmitted power (3.84 MHz BW RRC) to offset frequencies, which are between 2.5 MHz and 12.5 MHz away from the UE center carrier frequency; the offset frequencies are measured in 30 kHz or 1 MHz bandwidths, depending on the offsetInput power level range:+5 to +28 dBm/3.84 MHzInput frequency ranges: 698 to 1000 MHz, 1400 to 1500 MHz, 1700 to 2000 MHz, and 2480 to 2580 MHzMeasurement accuracy:< +1.5 dB (typically < +0.8 dB) for the following offsets (+10 °C from the calibration temperature)8.5 to 12.5 MHz -49 1 MHz Measurement accuracy for additional spectrum emission limits for bands II, IV, V, X, XII, XIII and XIV:typically < +1.1 dB for the following offsets (+10 °C from the calibration temperature) Frequency offset Levels (dBm) Meas BW2.5 to3.5 MHz --15 dBm 30 kHz3.5 to 12.5 MHz -13 dBm or -15 dBm 1 MHz or 100 kHzMeasurement triggers:auto, protocol, immediate, external, and HS-DPCCHHS-DPCCH trigger alignment:adjustable over subframes 0 to 5 /rfcomms/refdocs/wcdma/ wcdma_meas_spec_em_mask_desc.php Rx measurementsHSDPA/HSPA+ block error ratioMeasurement method: test set counts the ACK/NACK/statDTX on UE HS-DPCCH and uses the results to calculate BLERBLER measurement input level range: -50 to +28 dBm/3.84 MHzReported parameters: measured BLER, number of blocks tested, throughput, number of ACKs, number of NACKs, number of stat DTXs, and median CQIConcurrency capability: HSDPA BLER measurements cannot be made concurrently with phase discontinuity, PRACH Tx on/off, or inner loop power measurements, or while speech is provided on the downlink; HSDPA BLER measurements can be made concurrently with all other measurements, including W-CDMA loopback BER and BLER/rfcomms/refdocs/wcdma/ wcdma_meas_hblerror_desc.phpHSDPA bit error ratioMeasurement method: the 8960 can be configured so that BER can be measured externally using the 8960 downlink and external UE monitoring softwareW-CDMA SpecificationsCall connection typesEnd-to-end video conferencing (Option 401)Loop back video conferencing (Option 402)Imaging testing real-time mobile video conferencing at your own desk!The E1963A, when configured as a two-instrument system, provides true H324 call setup with live video and audio from both mobile devices.With only one E5515C, Loop back video call can be setup with option 402.Validate compatibility by testing interoperability between your mobile and the competitor models offered for the same network.•complete call setup, mobile origination, and mobile release•64k circuit-switched UDI channel•H324 call setup/rfcomms/refdocs/wcdma/ wcdma_gen_call_video_call.phpAMR voiceStandard voice call with audio loopback for a quick check of voice functionality for 12.2 k rate; also many more AMR rates, such as 4.75, 5.15, 5.9, 6.7, 7.4, 7.95, 10.2, and 12.2 k•UE and BS origination 12.2 k•UE and BS release/rfcomms/refdocs/wcdma/ wcdma_gen_bse_amrvoice.phpFDD test modeFDD test mode allows you to test the parametric performance of your UE’s transmitter and receiver without call processing. In FDD test mode, the test set does not send signaling information on the downlink. Rather, it continuously generates a downlink signal and searches for a corresponding uplink signal. The UE must synchronize to the downlink signal and send and appropriate uplink signal, which the test set uses to measure the UE’s transmitter and receiver performance. Any changes to the UE configuration must be accomplished by directly sending commands to the UE from a system controller through a proprietary digital interface./rfcomms/refdocs/wcdma/ wcdma_gen_bse_fddtest.php RB test modeFast conformance test calls with significant configuration control and testing capabilities•BS origination and release•Symmetrical configuration: W-CDMA modes support symmetrical RMCs at 12.2, 64, 144 and 384 k rates.These symmetrical RMCs are typically used fortransmitter testing and receiver testing user BER (vialoopback type 1) or BLER (via loopback type 2) •Asymmetric configuration: the asymmetrical RMCs use either a 12.2 k channel or a 64 k channel on theuplink. The primary purpose of the symmetrical RMCsis to provide a way to make a BLER measurement bycounting retransmission requests that the UE sends.There is no need for data loopback in this mode /rfcomms/refdocs/wcdma/ wcdma_gen_bse_rbtest_setup.phpInter-system handoverDual-mode functionality is required for most W-CDMA phones, as GSM is an integral part in the majority of devices shipping today. Inter-system handovers provide a means to validate dual-mode performance at your desk instead of roaming on a real network. When operated in conjunction with compressed mode, this feature can very closely emulate the basics of a real handover as made on the network.•blind handovers from W-CDMA to GSM•configurable landing GSM cell•test control to GSM voice•W-CDMA AMR voice to GSM voice/rfcomms/refdocs/wcdma/ wcdma_gen_call_handoffs.php。

5G第三阶段测什么? 5G技术研发试验第三阶段首批规范准备就绪

5G第三阶段测什么? 5G技术研发试验第三阶段首批规范准备就绪

5G第三阶段测什么? 5G技术研发试验第三阶段首批规范准备就绪作者:王欣来源:《通信产业报》2018年第02期新年伊始,通信圈就开始快马加鞭准备5G技术研发试验第三阶段测试,大秀5G加速度。

1月2日,工业和信息化部信息通信发展司组织召开“5G技术研发试验第三阶段规范”评审会,对IMT-2020(5G)推进组制定的5G技术试验第三阶段(以下简称5G第三阶段测试)首批规范进行评审。

与此同时,IMT-2020(5G)推进组正在积极进行5G第三阶段测试的环境建设,现已经完成从怀柔外场到室内实验室的传输改造,预计今年3月完成可以支持第三阶段测试的室内外环境建设。

实际上,5G第三阶段测试作为5G技术研发测试的最后一环,也是最接近5G商用的一环。

工信部信息通信发展司司长闻库指出,希望在2018年加快研发进度,重点突破5G核心关键技术,以技术试验为抓手,加快测试方案和测试规范的制定,使三阶段的目标通过规范落地。

第三阶段测试规范评审通过测试规范的确定能够为技术研发试验打下基础,成为5G第三阶段试验的首要任务。

而目前,5G第三阶段测试首批规范已经接受评审,并将于1月中旬正式发布。

在1月2日召开的“5G技术研发试验第三阶段规范”评审会上,评审专家组认为,《5G核心网设备技术要求》《5G低频基站设备功能技术要求》《5G终端设备技术要求》等八项5G 技术试验第三阶段首批规范,原则选择合理,规范内容较完整,可有效地指导第三阶段试验。

值得一提的是,评审组专家阵容强大,可谓涵盖整个通信圈。

据悉,中国工程院院士邬贺铨任评审专家组组长,来自“新一代宽带无线移动通信网”重大专项的总师和副总师、通信科技委、高校和科研机构等权威专家,基础电信企业、国内外设备和芯片制造企业等产业链代表参加评审。

同时,国家发展改革委、科技部及工信部相关司局参加会议。

5G标准未定,5G第三阶段测试规范的敲定,有力推动我国5G商用步伐更进一步。

评审专家组表示,当前5G国际标准尚未完全确定,率先制定试验规范进一步明确了测试目标、内容和指标,细化了设备研发和设备之间的互联互通的具体要求,奠定了5G第三阶段研发试验的基础,支撑了5G国际标准化和产业化,为下一步运营企业开展规模试验打下良好基础,推动5G更好、更快地发展。

3gppts25[1].303中文规范(系统连接模式下的层间过程)

3gppts25[1].303中文规范(系统连接模式下的层间过程)

通信标准参考性技术研究报告IMT-DS FDD(WCDMA)系统连接模式下的层间过程IMT-DS FDD(WCDMA) System Interlayer Procedures inConnected Mode20XX-XX-XX发布 20XX-XX-XX实施中华人民共和国无线标准通信研究组印发目次前言..................................................................................................................................................................... I II1 范围 (1)2 引用标准 (1)3 空白 (1)4 连接模式的一般描述 (1)5 无线承载控制---过程概要 (2)5.1 可配置参数 (2)5.2 典型的配置情况 (2)5.3 RRC基本过程 (3)5.3.1 类别1:无线承载配置 (3)5.3.2 类别2:传输信道的配置 (3)5.3.3 类别3:物理信道配置 (4)5.3.4 类别4:传输格式组合限制 (4)5.3.5 类别5:CRNC中上行专用信道的控制 (4)6 过程举例 (4)6.1 RRC连接建立和释放过程 (5)6.1.1 RRC连接建立 (5)6.1.2 UE发起的信令连接建立 (7)6.1.3 一般RRC连接释放 (7)6.2 无线承载控制过程 (11)6.2.1 无线承载配置 (11)6.2.2 传输信道重配 (23)6.2.3 物理信道重配 (26)6.2.4 传输格式组合控制 (31)6.2.5 上行DCH的动态资源分配控制 (32)6.2.6 上行DCH的变速率分组传输 (34)6.3 数据传输 (36)6.3.1 采用TFCI-word硬分割的DSCH上的应答模式数据传输 (36)6.3.2 采用TFCI-word逻辑分割的DSCH上的应答模式数据传输 (37)6.3.3 CPCH上的数据传输 (39)6.3.4 USCH上的数据传输(TDD) (41)6.3.5 DSCH上的数据传输(TDD) (41)6.4 RRC连接移动性过程 (41)6.4.1 切换测量报告 (41)6.4.2 小区更新 (42)6.4.3 URA更新 (44)6.4.4 无线链路增加 (47)6.4.5 无线链路去除 (48)6.4.6 组合的无线链路增加和去除 (49)6.4.7 硬切换 (50)6.4.8 SRNS重定位 (51)6.4.9 RRC连接重建 (55)6.4.10系统间切换:GSM/BSS到UTRAN (56)6.4.11系统间切换:UTRAN 到GSM/BSS,PSTN/ISDN域的业务 (58)6.5 连接模式下CN发起的寻呼请求 (60)6.5.1 利用DCCH的由UTRAN协调的寻呼 (60)6.6 UTRAN发起的寻呼请求和寻呼响应 (62)6.7 其他过程 (63)6.7.1 UE能力信息 (63)6.7.2 随机接入传输过程(FDD) (64)6.7.3 随机接入传输过程(TDD) (64)6.7.4 CPCH紧急停止过程 (64)7 业务量监控 (65)前言本通信标准参考性技术研究报告主要用于规定IMT-2000 DS系统FDD模式(WCDMA)的连接模式层间过程。

3GPP规范结构说明

3GPP规范结构说明

3GPP规范结构说明No Type Number Title1TS21.101适用于基于UTRAN 3GPP系统的技术规范和技术报告2TS21.111对USIM和IC卡的要求3TS21.1333G安全;安全威胁与安全要求4TR21.801规范起草规则5TR21.900技术规范小组的工作方法6TR21.9023GPP的系统演进7TR21.9053GPP规范字典8TS22.001公共陆地移动网(PLMN)所支持的电路电讯业务原理9TS22.002公共陆地移动网(PLMN)所支持的电路承载业务(BS)10TS22.003公共陆地移动网(PLMN)所支持的电路电信业务11TS22.004增补业务概要12TS22.011业务接入性能13TS22.016国际移动设备标识码(IMEI)14TS22.022移动台设备(ME)的个性化;移动台设备功能规范15TS22.024计费通知消息(CAI)描述16TS22.030用户设备(UE)的人机接口(MMI)17TS22.031欺诈信息搜集系统(FIGS);业务描述;第一阶段18TS22.032立即业务终止(IST);业务描述;第一阶段19TS22.034高速电路交换数据(HSCSD);第一阶段20TS22.038USIM/SIM应用工具箱(USAT/SAT);业务描述;第一阶段21TS22.041运营商决定的呼叫限制22TS22.042网络标识及时区(NITZ)业务描述;第一阶段23TS22.048适用于(U)SIM应用工具箱的安全机制;第一阶段24TS22.053串行自由操作(TFO);业务描述;第一阶段25TS22.057移动台执行环境(MExE)业务描述;第一阶段26TS22.060通用分组无线业务(GPRS);业务描述;第一阶段27TS22.066移动号码便携性(MNP)支持;第一阶段28TS22.067增强型多级别优先及占先业务(eMLPP);第一阶段29TS22.071定位业务(LCS);第一阶段30TS22.072呼叫改向(CD)增补业务;第一阶段31TS22.076AMR编解码的噪声抑制;业务描述;第一阶段32TS22.078移动网络增强型逻辑的自定义应用(CAMEL);业务描述;第一阶段33TS22.079优化路由支持(SOR);第一阶段34TS22.081线性鉴定增补业务;第一阶段35TS22.082呼叫前转(CF)增补业务;第一阶段36TS22.083呼叫等待(CW)和呼叫挂起(HOLD)增补业务;第一阶段37TS22.084多方通话增补业务;第一阶段38TS22.085闭合用户群(CUG)增补业务;第一阶段39TS22.086计费通知增补业务;第一阶段40TS22.087用户对用户信令(UUS);第一阶段41TS22.088呼叫阻塞(CB)支持业务;第一阶段42TS22.090非结构化补充业务数据(USSD);第一阶段43TS22.091显式呼叫转移(ECT)增补业务;第一阶段44TS22.093遇忙回叫(CCBS);业务描述,第一阶段45TS22.094Follow Me业务描述;第一阶段46TS22.096名字鉴别支持业务;第一阶段47TS22.097多用户配臵概要(MSP);业务描述;第一阶段48TS22.101业务类型;业务原则49TS22.105业务及业务容量50TS22.112USIM工具箱解释程序;第一阶段51TS22.115业务类型;计费和帐单编制52TR22.121业务类型;虚拟归属环境;第一阶段53TS22.127开放业务接入(OSA)的业务要求;第一阶段54TS22.129UTRAN与GERAN或其它无线系统的切换要求55TS22.135多路呼叫;业务描述;第一阶段56TS22.140多媒体信息业务(MMS);第一阶段57TS22.141Presence业务;第一阶段58TS22.146多媒体广播/多播业务(MBMS);第一阶段59TS22.173IP多媒体核心网子系统(IMS)多媒体电话业务及增补业务;第一阶段60TS22.174Push业务;第一阶段61TS22.182定制振铃音(CAT)要求;第一阶段62TS22.226全局文本电话(GTT)第一阶段;业务描述63TS22.228互联网协议(IP)多媒体核心网络子系统业务要求;第一阶段64TS22.233透明的终端对终端分组交换流业务;第一阶段65TS22.2343GPP系统与WLAN交互工作要求66TS22.240对3GPP通用用户模型(GUP)的业务要求;第一阶段67TS22.242数字版权管理(DRM);第一阶段68TS22.243用于自动话音业务的话音识别框架;第一阶段69TS22.246多媒体广播/多播业务(MBMS)的用户业务;第一阶段70TS22.250IP多媒体子系统(IMS)组管理;第一阶段71TS22.258全IP网络(AIPN)的业务要求(已经取消)72TS22.259个人网络管理(PNM)的业务要求73TS22.278演进的分组系统(EPS)的业务要求74TS22.279综合电路交换(CS)与IP多媒体子系统(IMS)会话;第一阶段75TS22.340IP多媒体子系统(IMS)消息;第一阶段76TS22.401TISPAN;NGN之上的视频电话业务描述77TS22.800IP多媒体子系统(IMS)订阅与接入场景(已经取消)78TR22.811网络选择原则回顾(已经取消)79TR22.857运行独立框架可行性研究(已经取消)80TR22.868推动3GPP设备间通讯的研究81TR22.892对IMS集中业务(ICS)要求的研究82TR22.903视频电话业务研究83TR22.908接入控制下允许寻呼的研究84TR22.912对非3GPP接入的网络选择要求的深入研究85TR22.9343GPP系统与WLAN交互工作的可行性研究86TR22.935定位业务(LCS)在WLAN互操作中的可行性研究87TR22.936多系统终端88TR22.937移动台与WLAN网络之间业务连贯性的要求89TR22.940IP多媒体子系统(IMS)消息;第一阶段90TR22.942短消息业务(SMS)的增值业务(VAS)研究91TR22.944UE功能分离的业务要求92TR22.948IMS融合多媒体会议要求的研究93TR22.949广义保密性能研究94TR22.950优先服务可行性研究95TR22.951网络共享的业务特征与要求96TR22.952优先服务指南97TR22.953多媒体优先服务可行性研究98TR22.967紧急呼叫数据传送99TR22.968公众通知系统(PWS)业务要求的研究100TR22.973IMS多媒体电话业务及增补业务101TR22.977话音许可业务的可行性研究102TR22.978全IP网络(AIPN)可行性研究103TR22.979综合电路交换(CS)与IP多媒体子系统(IMS)会话可行性研究104TR22.980网络融合可行性研究105TR22.981自定义振铃音(CAT)业务要求的研究106TR22.983业务队列与移植107TR22.984未鉴权的分组交换(PS)紧急呼叫108TS23.002网络结构109TS23.003编号、寻址和鉴权110TS23.007更新过程111TS23.008用户数据的组织112TS23.009切换过程113TS23.011增补业务的技术实现114TS23.012定位管理过程115TS23.014双音多频信号(DTMF)的支持116TS23.015运营商决定的呼叫阻塞(ODB)的技术实现117TS23.016用户数据管理;第二阶段118TS23.018基础呼叫处理;技术实现119TS23.031欺诈信息搜集系统(FIGS);业务描述;第二阶段120TS23.032通用地理区域描述(GAD)121TS23.034高速电路交换数据(HSCSD);第二阶段122TS23.035立即业务终止(IST);业务描述;第二阶段123TS23.038字母表和语言细节信息124TR23.039短消息业务中心(SMSCs)至短消息实体(SMEs)连接的接口协议125TS23.040短消息业务(SMS)的技术实现126TS23.041小区广播业务(CBS)的业务实现127TS23.042SMS的压缩算法128TS23.048适用于(U)SIM工具箱的安全机制;第二阶段129TS23.053串行自由操作(TFO);业务描述;第二阶段130TS23.057移动台执行环境(MExE)业务描述;第二阶段131TS23.060通用分组无线业务(GPRS);业务描述;第二阶段132TS23.066移动号码可移植性(MNP)支持;第二阶段133TS23.067增强型多级别优先及预臵空业务(eMLPP);第二阶段134TS23.072呼叫转移(CD)增补业务;第二阶段135TS23.078移动网络增强型逻辑的自定义应用(CAMEL);业务描述;第二阶段136TS23.079优化寻址支持(SOR);技术实现;第二阶段137TS23.081线性鉴定增补业务;第二阶段138TS23.082呼叫前转(CF)增补业务;第二阶段139TS23.083呼叫等待(CW)和呼叫挂起(HOLD)增补业务;第二阶段140TS23.084多类型增补业务;第二阶段141TS23.085闭合用户群(CUG)增补业务;第二阶段142TS23.086计费通知增补业务;第二阶段143TS23.087用户对用户信令(UUS);第二阶段144TS23.088呼叫阻塞(CB)支持业务;第二阶段145TS23.090非结构化补充业务数据(USSD);第二阶段146TS23.091显式呼叫转移(ECT)增补业务;第二阶段147TS23.093遇忙回叫(CCBS);业务描述,第二阶段148TS23.094Follow Me业务描述;第二阶段149TS23.096名字鉴别支持业务;第二阶段150TS23.097多用户配臵概要(MSP)第一阶段;第二阶段151TS23.101一般UMTS结构152TS23.107服务等级(QoS)概念与结构153TS23.108移动台空中接口层三规范核心网络协议;第二阶段(结构化过程)154TS23.110UMTS接入层155TS23.116Super-Charger的技术实现;第二阶段156TS23.119网关位臵寄存器(GLR);第二阶段157TS23.122在空闲模式下与移动台(MS)相关的非接入层功能158TS23.127虚拟归属环境(VHE)及开放业务接入(OSA);第二阶段159TS23.135多路呼叫增补业务;第二阶段160TS23.140多媒体信息业务(MMS);功能描述;第二阶段161TS23.146组三传真业务的技术实现——非透明162TS23.153带外代码转换管理;第二阶段163TS23.172电路交换(CS)多媒体业务的技术实现;UDI/RDI 支持及业务修正;第二阶段164TS23.195至网络实体的用户设备特殊行为信息(UESBI)的规定165TS23.198开放业务接入(OSA);第二阶段166TS23.202电路交换数据承载业务167TS23.203政策与计费控制结构168TS23.204短消息业务(SMS)在通用3GPP IP接入上的支持;第二阶段169TS23.205承载无关的电路交换核心网络;第二阶段170TS23.207终端对终端的服务等级(QoS)概念和结构171TS23.216单一无线话音呼叫连续性(SRVCC);第二阶段172TS23.218IP多媒体(IM)会话处理;IM呼叫模型;第二阶段173TS23.221结构需求174TS23.226全局文本电话;第二阶段;结构175TS23.227UE中的应用与用户交特性互;原理与特性需求176TS23.228IP多媒体子系统;第二阶段177TS23.231基于SIP-I的电路交换核心网;第二阶段178TS23.2343GPP系统与WLAN互联;系统描述179TS23.236无线接入网(RAN)节点至多种核心网(CN)节点的域内连接180TS23.237IP多媒体子系统(IMS)业务连续性;第二阶段181TS23.2403GPP通用用户模型(GUP)要求;结构(第二阶段)182TS23.246多媒体广播/多播业务(MBMS);结构与功能描述183TS23.251网络共享;结构与功能描述184TS23.259个人网络管理(PNM);过程与信息流185TS23.271定位业务(LCS);功能描述;第二阶段186TS23.272在演进分组系统(EPS)中的电路交换回退;第二阶段187TS23.278移动网络增强型逻辑的自定义应用(CAMEL)-IP 多媒体系统(IMS)之间的互动;第二阶段188TS23.279结合电路交换(CS)与IP多媒体子系统(IMS)业务;第二阶段189TS23.292IP多媒体子系统(IMS)业务集中;第二阶段190TS23.327在3GPP-WLAN交互及3GPP系统之间的移动性191TS23.333多媒体资源功能控制(MRFC)与多媒体资源功能处理(Mp)接口;过程描述192TS23.380IMS恢复过程193TS23.402对非3GPP接入的结构增强194TS23.506TISPAN;IP多媒体子系统(IMS)第二阶段描述195TS23.507TISPAN;话音呼叫连续性(VCC);第二阶段描述196TS23.508TISPAN;Presence业务;结构与功能描述197TS23.509TISPAN;NGN下支持群众至权力机构的紧急通信的系统结构198TS23.511TISPAN;XML文档管理;结构与功能描述199TS23.517TISPAN;IP多媒体子系统(IMS)功能结构;200TS23.521TISPAN;NGN IMS子系统上短消息业务(SMS)的支持;第二阶段201TS23.611TISPAN;XML文档管理;结构与功能描述202TS23.802端对端服务等级(QoS)的结构性增强203TR23.810业务借鉴对结构带来的冲击的研究204TR23.811消息业务的业务级别交互;第二阶段205TR23.815IMS结构中的计费206TR23.820IMS恢复过程研究207TR23.826话音呼叫连续性(VCC)对紧急呼叫的支持的可行性研究208TR23.828地震与海啸预报系统(ETWS);要求与解决方案;解决方案预臵209TR23.846多媒体广播与多播业务;结构与功能描述210TR23.847为推动多点传送承载业务而做的IMS业务功能增强211TR23.868对IMS紧急呼叫支持的扩展的可行性研究212TR23.869对基于IP的GPRS与EPS之上的IMS紧急呼叫的支持213TR23.871在定位业务(LCS)中对用户私密的增强型支持214TR23.872对基于IMS的个性振铃音(CAT)结构的研究215TR23.873在PS的CN域中传输与控制分离的可行性研究216TR23.875Push业务支持217TR23.879在EPS接入下对电路交换域业务的研究218TR23.880第二阶段人口密集区登记;解决方案预臵219TR23.8823GPP系统结构演进(SAE);有关技术选项和结论的报告220TR23.892IMS集中业务221TR23.893多媒体会话连续性的可行性研究;第二阶段222TR23.894在本地总结及媒体路由优化中使用IMS业务的系统增强223TR23.903话音-视频切换的径向解决方案224TR23.910电路交换数据承载业务225TR23.919直接隧道部署指南226TR23.976Push结构227TR23.977电路交换网络的带宽与资源节约(BARS)及与话音增强228TR23.979开放移动联盟(OMA)的蜂窝系统按-讲(PoC)业务的3GPP许可;第二阶段229TR23.981基于IPV4的IMS实现的交互作用层面及移植场景230TS24.002GSM-UMTS公共陆地移动网(PLMN)接入参考结构231TS24.007移动空中接口层三信令;一般特征232TS24.008移动空中接口层三规范;核心网络协议;第三阶段233TS24.010移动空中接口层三——增补业务规范——一般特征234TS24.011移动空中接口中对点对点(PP)短消息业务(SMS)的支持235TS24.022适用于电路交换的承载及电信业务的无线链路协议(RLP)236TS24.030定位业务(LCS);增补业务操作;第三阶段237TS24.067增强型多级别优先及预臵空业务(eMLPP);第三阶段238TS24.072呼叫转移增补业务;第三阶段239TS24.080移动空中层三增补业务规范;格式与编码240TS24.081线性定义与增补业务;第三阶段241TS24.082呼叫前转增补业务;第三阶段242TS24.083呼叫等待(CW)与呼叫挂起(HOLD)增补业务;第三阶段243TS24.084多组(MPTY)增补业务;第三阶段244TS24.085闭合用户群(CUG)增补业务;第三阶段245TS24.086计费通知增补业务;第三阶段246TS24.087用户对用户信令(UUS);第三阶段247TS24.088呼叫阻塞(CB)增补业务;第三阶段248TS24.090无结构化的增补业务数据(USSD);第三阶段249TS24.091清晰呼叫传输(ECT)增补业务;第三阶段250TS24.093对遇忙回叫(CCBS);第三阶段251TS24.096名字鉴别增补业务;第三阶段252TS24.109自举接口(Ub)和网络应用功能接口(Ua);协议细节253TS24.135多路呼叫增补业务;第三阶段254TS24.141使用IP多媒体核心网子系统的Presence业务;第三阶段255TS24.147使用IP多媒体核心网子系统的会议;第三阶段256TS24.1673GPP IMS管理对象;第三阶段257TS24.173IMS多媒体电话业务及增补业务;第三阶段258TS24.182IMS下个性振铃音(CAT);协议规范259TS24.216通信连续性管理对象260TS24.228在SIP及SDP上的IP多媒体呼叫管理信令流;第三阶段261TS24.229基于会话初始化协议(SIP)及会话描述协议(SDP)的互联网协议(IP)多媒体呼叫管理协议;第三阶段262TS24.2343GPP系统与WLAN交互工作;WLAN用户设备至网络协议;第三阶段263TS24.237IMS业务连续性;第三阶段264TS24.238基于会话初始化协议(SIP)的用户配臵;第三阶段265TS24.239使用IP多媒体核心网子系统的灵活振铃(FA);协议规范266TS24.247使用IP多媒体核心网子系统的消息业务;第三阶段267TS24.259个人网络管理(PNM);第三阶段268TS24.279电路交换(CS)业务与IMS业务的融合;第三阶段269TS24.285允许闭合用户组列表(CSG);管理对象(MO)270TS24.292IP多媒体核心网子系统集中业务;第三阶段271TS24.301用于EPS的非接入层(NAS)协议;第三阶段272TS24.302通过非3GPP接入网络接入演进分组核心(EPC);第三阶段273TS24.303基于双协议栈移动IPV6的移动性管理;第三阶段274TS24.304基于移动IPV4的移动性管理;用户设备(UE)-外地代理接口;第三阶段275TS24.305UE性能的选择性禁止(SDoUE)管理对象276TS24.312接入网发现与选择功能(ANDSF)管理对象277TS24.3233GPP下IMS业务级别追踪管理对象278TS24.3273GPP的WLAN交互(I-WLAN)与3GPP系统之间的移动性;GPRS与3GPP I-WLAN问题;第三阶段279TS24.341在IP网之上的SMS支持;第三阶段280TS24.406TISPAN;PSTN/ISDN模拟业务;消息等待指示(MWI);协议规范281TS24.407TISPAN;PSTN/ISDN模拟业务;主叫号码呈现(OIP)与主叫号码隐藏(OIR);协议规范282TS24.410TISPAN;NGN信令控制协议;通话保持(HOLD)PSTN/ISDN模拟业务;协议规范283TS24.411TISPAN;PSTN/ISDN模拟业务;匿名通讯拒绝(ACR)与通讯阻止(CB);协议规范284TS24.423TISPAN;PSTN/ISDN模拟业务;为操作NGN PSTN/ISDN模拟在Ut接口上的可扩展标记语言(XML)配臵接入协议(XCAP)285TS24.430TISPAN;Presence业务性能;协议规范286TS24.441TISPAN;使用IP多媒体核心网子系统的消息业务;第三阶段;协议规范287TS24.447TISPAN;NGN IMS增补业务;计费通知(AoC)288TS24.451TISPAN;支持基于NGN IMS子系统的SMS和MMS;第三阶段;289TS24.454TISPAN;PSTN/ISDN模拟业务;协议规范封闭用户群(CUG)290TS24.503TISPAN;基于会话初始化协议(SIP)及会话描述协议(SDP)的IP多媒体呼叫控制协议;第三阶段291TS24.504TISPAN;PSTN/ISDN模拟业务;通话转移(CDIV);协议规范292TS24.505TISPAN;PSTN/ISDN模拟业务;会议(CONF);协议规范293TS24.508PSTN/ISDN模拟业务;被叫号码呈现(TIP)与被叫号码隐藏(TIR);协议规范294TS24.516TISPAN;PSTN/ISDN模拟业务;恶意通讯识别(MCID);协议规范295TS24.528TISPAN;一般基础通讯过程;协议规范296TS24.529TISPAN;PSTN/ISDN模拟业务;显式通讯转移(ECT);协议规范297TS24.604使用IP多媒体核心网子系统的通讯转移(CDIV);协议规范298TS24.605使用IP多媒体核心网子系统的会议(CONF);协议规范299TS24.606使用IP多媒体核心网子系统的消息等待指示(MWI);协议规范300TS24.607使用IP多媒体核心网子系统的主叫号码呈现(OIP)与主叫号码隐藏(OIR);协议规范301TS24.608使用IP多媒体核心网子系统的被叫号码呈现(TIP)与被叫号码隐藏(TIR);协议规范302TS24.610使用IP多媒体核心网子系统的通讯保持(HOLD);协议规范303TS24.611使用 IP多媒体核心网子系统的匿名通讯拒绝(ACR)与通讯阻止(CB);协议规范304TS24.615使用IP多媒体核心网子系统的通讯等待(CW);协议规范305TS24.616使用P多媒体核心网子系统的恶意通讯识别(MCID);协议规范306TS24.623为操作模拟业务在Ut接口上使用的可扩展标记语言(XML)配臵接入协议307TS24.628使用IP多媒体核心网子系统的一般基础通讯过程;协议规范308TS24.629使用IP多媒体核心网子系统的显式通讯转移(ECT);协议规范309TS24.642使用IP多媒体核心网子系统的遇忙通讯完成(CCBS)和无回应通讯完成(CCNR);协议规范310TS24.647使用IP多媒体核心网子系统的计费通知(AoC);协议规范311TS24.654使用 IP多媒体核心网子系统的闭合用户组(CUG);协议规范312TR24.8013GPP系统结构演进(SAE)CT WG1方面313TR24.880使用IP多媒体核心网子系统的媒体服务器控制;第三阶段314TR24.930在IMS中基于会话初始化协议(SIP)及会话描述协议(SDP)用于会话建立的信令流;第三阶段315TS25.101UE无线发射与接收(FDD)316TS25.102UTRA(UE)TDD;无线发射与接收317TS25.104UTRA(BS)FDD;无线发射与接收318TS25.105UTRA(BS)TDD;无线发射与接收319TS25.106UTRA中继器;无线发射与接收320TS25.111位臵测量单位(LMU)性能规范;UTRAN中的用户设备(UE)定位321TS25.113基站与中继器的电磁兼容(EMC)322TS25.123无线资源管理支持的要求(TDD)323TS25.133无线资源管理支持的要求(FDD)324TS25.141基站一致性检测(FDD)325TS25.142基站一致性检测(TDD)326TS25.143UTRA中继器;一致性检测327TS25.144用户设备(UE)和移动台(MS)的空中性能要求328TS25.171支持辅助全球定位系统(A-GPS)的要求(FDD)329TS25.201物理层—概要描述330TS25.2027.68Mcps时分复用(TDD)选项;一般描述;第二阶段331TS25.211物理层信道及传输信道在物理层信道上的映射(FDD)332TS25.212信道编码与多路复用(FDD)333TS25.213扩频与调制(FDD)334TS25.214物理层过程(FDD)335TS25.215物理层;测量(FDD)336TS25.221物理层信道及传输信道在物理层信道上的映射(TDD)337TS25.222信道编码与多路复用(TDD)338TS25.223扩频与调制(TDD)339TS25.224物理层过程(TDD)340TS25.225物理层;测量(TDD)341TS25.301无线接口协议结构342TS25.302物理层所提供的服务343TS25.303在接续模式下的层间流程344TS25.304空闲模式下的UE过程及接续模式下的小区重选过程345TS25.305在UTRAN中的UE定位;第二阶段346TS25.306UE无线接入性能定义347TS25.307支持版本无关性频段的UE的要求348TS25.308UTRA高速下行分组接入(HSDPA);整体描述;第二阶段349TS25.309FDD增强型上行;全面描述;第二阶段350TS25.319增强型上行;全面描述;第二阶段351TS25.321介质接入管理(MAC)协议规范352TS25.322无线链路管理(RLC)协议规范353TS25.323分组数据汇聚协议(PDCP)规范354TS25.324广播/多播控制(BMC)355TS25.331无线资源管理(RRC)协议规范356TS25.346多媒体广播/多播(MBMS)在无线接入网(RAN)中的介绍;第二阶段357TS25.367用于归属Node B(HNB)的移动性过程;整体描述;第二阶段358TS25.401UTRAN整体描述359TS25.402UTRAN中的同步;第二阶段360TS25.410UTRAN Iu接口;一般性质与原理361TS25.411UTRAN Iu接口层一362TS25.412UTRAN Iu接口信令传输363TS25.413UTRAN Iu接口无线接入网应用部分(RANAP)信令364TS25.414UTRAN Iu接口数据传输与信令传输365TS25.415UTRAN Iu接口用户平面协议366TS25.419UTRAN Iu-BC接口;业务区域广播协议(SABP)367TS25.420UTRAN Iur接口;一般性质与原理368TS25.421UTRAN Iur接口层一369TS25.422UTRAN Iur接口信令传输370TS25.423UTRAN Iur接口无线网络子系统应用部分(RNSAP)信令371TS25.424UTRAN Iur接口数据传输及CCH数据流的传输信令372TS25.425UTRAN Iur接口CCH数据流的用户平面协议373TS25.426UTRAN Iur及Iub接口数据传输及DCH数据流的传输信令374TS25.427UTRAN Iur及Iub接口CCH数据流的用户平面协议375TS25.430UTRAN Iub接口;一般性质与原理376TS25.431UTRAN Iub接口层一377TS25.432UTRAN Iub接口信令传输378TS25.433UTRAN Iub接口NBAP信令379TS25.434UTRAN Iub接口数据传输及CCH数据流的传输信令380TS25.435UTRAN Iub接口公共传输信道数据流用户平面协议381TS25.442UTRAN中O&M传输的执行细节382TS25.446MBMS同步协议383TS25.450UTRAN Iupc接口;一般性质与原理384TS25.451UTRAN Iupc接口层一385TS25.452UTRAN Iupc接口信令传输386TS25.453UTRAN Iupc接口定位计算应用部分(PCAP)信令387TS25.460UTRAN Iuant接口;一般描述与原则388TS25.461UTRAN Iuant接口;层一389TS25.462UTRAN Iuant接口;信令传输390TS25.466UTRAN Iuant接口;应用部分391TS25.467适用于3G归属Node B的UTRAN结构;第二阶段392TS25.468UTRAN Iuh接口RANAP用户适应(RUA)信令393TS25.469UTRAN Iuh接口归属Node B(HNB)应用部分(HNBAP)信令394TR25.8203G归属Node B研究项目技术报告395TR25.821UMTS 1500 MHz工作项目技术报告396TR25.822UMTS 700 MHz工作项目技术报告397TR25.823对UTRA FDD的同步E-DCH的可行性研究398TR25.824适用于1.28Mcps TDD的HSPA的研究范围399TR25.825双小区高速下行分组接入(HSDPA)操作400TR25.828UMTS 2300 MHz TDD 工作项目技术报告401TR25.830HS-PDSCH服务小区变换过程与性能402TR 25.854上行同步发射方案(USTS)403TR 25.858UTRA高速下行分组接入中的物理层问题404TR 25.859为1.28McpsTDD用户设备(UE)定位增强405TR 25.860无线接入承载支持增强406TR 25.8673G网络中宽带分布式系统的可行性研究407TR 25.868 1.28 Mcps TDD的Node B同步408TR 25.870DSCH中强分裂模式的增强409TR 25.875NAS节点选择器功能410TR 25.876多路输入与多路输出天线411TR 25.877高速下行分组接入(HSDPA)—Iub/Iur协议问题412TR 25.878RL定时调整413TR 25.879资源保留与无线链路激活的分离414TS 25.880Iub 传输承载电路的再分配415TR 25.881RNS与RNS/BSS之间无线资源管理(RRM)的改进416TR 25.882 1.28 Mcps TDD基站分级选项417TR 25.883SRNC和Node-B之间的直接传输承载电路418TR 25.884Iur邻小区报告效率优化419TR 25.889在考虑可行性分配的UTRA附加频谱分配的可行性研究420TR 25.890高速下行分组接入(HSDPA);用户设备(UE)无线发射与接收(FDD)421TR 25.903分组数据用户的连续连接422TR 25.906当达到QoS预期要求时为减少能量浪费对频分复用(FDD)用户设备(UE)接收机的动态重配臵423TR 25.912对通用陆地无线接入(UTRA)和通用陆地无线接入网(UTRAN)演进的可行性研究424TR 25.913演进UTRA(E-UTRA)和演进UTRAN(E-UTRAN)的要求425TR 25.914在UMTS终端的话音模式下对无线性能的测量426TR 25.921协议描述及错误处理的方针和原理427TR 25.922无线资源管理策略428TR 25.929数据业务用户连续的连通性;1.28Mcps TDD429TR 25.931在信令过程中的UTRAN功能与实例430TR 25.933UTRAN中的IP传输431TR 25.942RF系统方案432TR 25.943扩展方面433TR 25.945低码片速率TDD选择下的RF要求434TR 25.951FDD基站(BS)分类)435TR 25.952基站分类(TDD)436TR 25.956UTRA中继器;设计方针和系统分析437TR 25.963对UTRA FDD用户设备(UE)接口取消的可靠性研究438TS 25.967FDD归属Node BRF要求439TR 25.991减缓公共导频信道(CPICH)对用户设备干扰的影响的可行性研究440TR 25.992MBMS;UTRAN/GERAN要求441TR 25.993由通用陆地无线接入(UTRA)支持的无线接入承载电路(RABs)和无载电路(RBs)的典型例子442TR 25.994UMTS无线接入网(UTRAN)所做的用于克服早期用户设备(UE)执行错误的测试443TR25.995UMTS无线接入网(UTRAN)所做的为配合符合RAN接口规范的替换版本的用户设备(UE)的测试444TR25.996用于多路输入多路输出(MIMO)仿真的空间信道模型445TS26.071AMR话音编解码;一般描述446TS26.073AMR话音编解码;C源编码447TS26.074AMR话音编解码;训练序列448TS26.077自适应多速率(AMR)话音编解码器的噪声抑制应用的最低性能要求449TS26.090AMR话音编解码;代码转换功能450TS26.091AMR话音编解码;丢帧的错误隐藏451TS26.092AMR话音编解码;AMR话音业务信道的舒适噪声452TS26.093AMR话音编解码;源控制速率操作453TS26.094AMR话音编解码;AMR话音业务信道的话音激活检测454TS26.101强制话音编解码话音处理功能;自适应多速率(AMR)话音编解码帧结构455TS26.102自适应多速率(AMR)话音编解码;至Iu及Uu的接口456TS26.103GSM和UMTS的话音编解码列表457TS26.104适用于浮点自适应多速率(AMR)话音编解码的ANSI-C编码458TS26.110电路交换多媒体电话业务编解码;一般描述459TS26.111电路交换多媒体电话业务编解码;对应于H.324的460TS26.114IMS;多媒体电话;媒体处理与交互461TS26.115话音及多媒体业务的回声抑制462TS26.131电话业务终端的声学特性;要求463TS26.132窄带(3.1kHz)话音及视频电话终端声学测试规范464TS26.140多媒体信息业务(MMS);媒体结构及编码465TS26.141IMS消息与呈现;媒体格式与编码466TS26.142动态与交互多媒体情景(DIMS)467TS26.171AMR话音编解码,宽带;一般描述468TS26.173适用于自适应多速率宽带(AMR-W)话音编解码的ANSI-C编码469TS26.174AMR话音编解码,宽带;训练序列470TS26.177话音增强业务(SES);分布式话音识别(DSR)扩展高级前端测试序列471TS26.190强制话音编解码话音处理功能;AMR宽带话音编解码;代码转换功能472TS26.191AMR话音编解码,宽带;丢帧的错误隐藏473TS26.192强制话音编解码话音处理功能;AMR宽带话音编解码;舒适噪声问题474TS26.193AMR话音编解码,宽带;源控制速率操作475TS26.194强制话音编解码话音处理功能;AMR宽带话音编解码;话音激活检测(VAD)476TS26.201AMR话音编解码,宽带;帧结构477TS26.202AMR话音编解码,宽带;至Iu及Uu的接口478TS26.204适用于浮点自适应多速率宽带(AMR-W)话音编解码的ANSI-C编码479TS26.226全局文本电话(GTT);话音信道中的文本传输480TS26.230全局文本电话(GTT);蜂窝文本电话Modem发射机C编码描述481TS26.231全局文本电话(GTT);蜂窝文本电话Modem最低性能要求482TS26.233终端对终端透明流业务;一般描述483TS26.234透明终端对终端透明流业务;协议及编解码484TS26.235分组会话多媒体应用;缺省编解码485TS26.236分组会话多媒体应用;传输协议486TS26.237基于IMS的PSS与MBMS用户业务;协议487TS26.243用于定点分布式话音识别的ANSI-C码扩展高级前端488TS26.244透明的终端至终端分组交换流业务(PSS);3GPP 文件格式(3GP)489TS26.245透明的终端至终端分组交换流业务(PSS);同步文本格式490TS26.246透明的终端至终端分组交换流业务(PSS); 3GPP SMIL语言分布491TS26.267eCall数据传输;带内Modem解决方案;一般描述492TS26.268eCall数据传输;带内Modem解决方案; ANSI-C 参考码493TS26.269eCall数据传输;带内Modem解决方案;一致性测试494TS26.273用于定点扩展自适应多速率宽带话音编码的ANSI-C码495TS26.274话音编码话音处理功能;扩展自适应多速率宽带话音编码;一致性测试496TS26.290音频编码处理功能;扩展自适应多速率宽带话音编码;代码转换功能497TS26.304扩展自适应多速率宽带话音编码;浮点ANSI-C码498TS26.346多媒体广播/多播业务(MBMS);协议与编码499TS26.401一般音频编码处理功能;增强型aacPlus一般音频编码;一般描述500TS26.402一般音频编码处理功能;增强型aacPlus一般音频编码;增补解码工具501TS26.403一般音频编码处理功能;增强型aacPlus一般音频编码;编码器规范;高级音频编码(AAC)部分502TS26.404一般音频编码处理功能;增强型aacPlus一般音频。

3gpp 5g广播标准介绍

3gpp 5g广播标准介绍

5G+AI3GPP 5G广播标准介绍*付光涛 夏治平 国家广播电视总局广播电视科学研究院彭莉 中央广播电视总台播送中心播出一部摘要:本文通过跟踪正在标准制定过程中的5G 广播标准,介绍了3GPP 5G广播标准提出、标准的技术方向和标准制定情况,为了解5G广播技术的发展提供了技术依据。

关键词:LTE 5G广播 参数集1 引言多媒体广播多播业务(Multimedia Broadcast/Multicast Service,MBMS)是3GPP组织提出的基于通用移动通信系统的手机多媒体技术方案[1],在Release 8中首次进行了物理层定义。

3GPP从Release 9版本开始支持增强型多媒体广播多播业务(enhanced Multimedia Broadcast/Multicast Service,eMBMS),并完成了eMBMS整个架构设计和单频网MBSFN的支持。

3GPP Release 10版本进行功能优化,主要包括DASH Content和Counting Support。

Release 11、Release 12版本主要进行业务增强,包括Service Continuity、QoE Support、MooD、Multiple FLUTE 等的支持。

上述版本中,都是低功率小塔(移动通信基站)支持广播模式,最多只能利用60%信道资源,覆盖范围与移动通信基站相当,频谱利用率低。

3GPP Release 14版本中LTE广播组播技术引入高功率大塔(HPHT)广播(该特性也称为“entv”),支持独立组网,能够利用接近100%的信道资源;采用更长循环前缀的200μs,1.25kHz子载波间隔,基站间距可以达到60km;支持无SIM卡的单独接收模式。

上述技术的改进,未针对移动场景设计,商业部署案例较少。

2 3GPP 5G广播标准的提出第五代移动通信技术(5G)相比较4G,主要面对增强宽带(eMMB)、超可靠低时延(uRLLC)和大规模机器通信(mMTC)三大应用场景,实现人与人、人与物、物与物的智能互联。

5G 38.201物理层概述

5G 38.201物理层概述
定义..................................................................................................................................................................... 5 符号..................................................................................................................................................................... 5 缩略语................................................................................................................................................................. 5 与其他图层的关系............................................................................................................................................. 6 通用协议架构................................................................................................................................................6 服务提供给更高层........................................................................................................................................7 物理层的一般描述............................................................................................................................................. 7 多次访问........................................................................................................................................................7 物理信道和调制............................................................................................................................................7 频道编码........................................................................................................................................................7 物理层流程....................................................................................................................................................7 物理层测量....................................................................................................................................................8

3gpp标准

3gpp标准

*E TSI SMG-TR 004T ECHNICAL C OMMITTEE May 1996T ECHNICAL R EPORTSource: ETSI TC-SMGReference: RTR/SMG-050001UICS:33.060.50Key words:Universal Mobile Telecommunications System (UMTS), work programmeSpecial Mobile Group (SMG);Work programme for the standardization of the Universal Mobile Telecommunications System (UMTS)(UMTS 00.01)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.Page 2SMG-TR 004 (UMTS 00.01): May 1996Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editing and Committee Support Dept." at the address shown on the title page.Page 3SMG-TR 004 (UMTS 00.01): May 1996ContentsForeword (5)Introduction (5)1Scope (7)2Milestones (7)3Documentation (7)3.1General (7)3.1.1Types of deliverables (7)3.1.2Approval responsibility (8)3.1.3.UMTS document numbering (8)3.2Details of the UMTS work programme (8)3.2.1General (UMTS 21-series) (8)3.2.2Service aspects (UMTS 22-series) (8)3.2.3Network aspects (UMTS 23-series) (8)3.2.4Radio aspects (UMTS 25-series) (8)3.2.5UMTS management aspects (UMTS 32-series) (9)3.2.6Voice-band and audio aspects (UMTS 26-series) (9)3.2.7Video aspects (UMTS 34-series) (9)3.2.8Security aspects (UMTS 33-series) (9)3.2.9Terminal aspects (UMTS 35-series) (9)3.2.10Interworking and internetwork signalling aspects (UMTS 24-series) (9)3.2.11Conformance testing specifications (UMTS 31-series) (9)4Working structure (10)Annex A (informative):Milestones for the standardization of UMTS (11)Annex B (informative):Deliverables for UMTS standardization (12)B.1Baseline material (12)Annex C (informative):Standards (14)Annex D (informative):Terms of Reference for ETSI/SMG5 (17)D.1Responsibility (17)D.2Work Plan (17)D.3Working methods (17)D.4Liaisons (18)D.5Specific guidance for SMG5 work in the years 1996 - 1997 (18)History (19)Page 4SMG-TR 004 (UMTS 00.01): May 1996Blank pagePage 5SMG-TR 004 (UMTS 00.01): May 1996 ForewordThis Technical Committee Reference Technical Report (TC-TR) was prepared by the Special Mobile Group (SMG) Technical Committee of the European Telecommunications Standards Institute (ETSI).This TC-TR is an informative document resulting from ETSI studies which are not appropriate for European Telecommunication Standard (ETS), Interim European Telecommunication Standard (I-ETS) or ETSI Technical Report (ETR) status.They can be used for guidelines, status reports, co-ordination documents, etc. They are used to manage studies inside TCs. They may also be utilised by the TC with overall responsibility for a study area for co-ordination documents (e.g. models, reference diagrams, principles, structures of standards, framework and guideline documents).IntroductionThe Universal Mobile Telecommunications System (UMTS) is envisaged as the third generation mobile telecommunications system to follow in Europe after the second generation systems like GSM, DCS 1800, DECT, etc.Universal Mobile Telecommunication System (UMTS) will offer flexible service capabilities, digital mobile voice, fax, video, multi-media, data and other information service capabilities and capacity via seamless wireless access to everyone equipped with a single easy to use terminal. UMTS is intended to enter service at the beginning of the 21st century (1.1.2002) in the 2 GHz frequency band.Page 6SMG-TR 004 (UMTS 00.01): May 1996Blank pagePage 7SMG-TR 004 (UMTS 00.01): May 1996 1ScopeThis ETSI Technical Committee Technical Report (TC-TR) describes the work programme for the standardization of the Universal Mobile Telecommunications System (UMTS) to be carried out by ETSI. It is envisaged that the work will be carried out in close co-operation with the work on Future Public Land Mobile Telecommunications Systems (FPLMTS) within the ITU. The ITU FPLMTS Recommendations form the global framework for system specifications such as the ETSI UMTS standard.A single set of UMTS standards (ETSs) will cover general, service, network, radio, management and various implementation aspects. The application scopes and technical objectives of UMTS are already defined in the UMTS ETRs. The UMTS work within ETSI may additionally include technical studies for the support of work towards UMTS ETSsThe overall responsibility for the standardization of UMTS within ETSI has been given to TC SMG. STC SMG5 has been producing UMTS framework documents over the period 1991 - 1995 in the form of a set of ETRs[ refs]. The definition of detailed UMTS ETSs has been started now within the TC SMG and other ETSI TCsThis UMTS work programme is to be used for long term programme management purposes and will be maintained by SMG 5. This UMTS work programme is used as the basis of the ETSI Work Programme (EWP).This UMTS work programme contains short-term and long-term documentation, the time scales for their production, as well as allocation of responsibilities. In some cases, in particular for the short-term documentation, exact deliverables have been identified, while for the more long-term documentation only work areas identified for potential standards have been identified.2MilestonesThe outline of milestones identified for the standardization of UMTS are included in annex A. Annex B. contains the milestones for baseline documents defining UMTS objectives, requirements and frameworks. The detailed structure for UMTS ETSs together with the timing and responsibilities is contained in annex C.In defining and maintaining the ETSI Work Programme (EWP) sheets, the market demand for various parts of the UMTS standards has to be taken into account, taking into consideration the market situation for existing mobile systems, as well as the availability of frequencies for UMTS.3Documentation3.1General3.1.1Types of deliverablesThe documentation for UMTS will generally consist of two types of deliverables:1)Baseline material:This material will consist of some form of Technical Reports, typically ETSI Technical Reports (ETRs), containing material for key decisions, or work leading up to these, overall framework and requirements etc.2)Standards:This material will typically consist of European Telecommunications Standards (ETSs), and in exceptional cases Technical Basis for Regulations (TBRs), containing material for the exact definition of the system.The UMTS system standard will be defined to the degree necessary for compatibility and international roaming. Open network interfaces are also desirable. For practical reasons, the UMTS system standard will further be developed in phases corresponding to the implementation phases of UMTS. This will bePage 8SMG-TR 004 (UMTS 00.01): May 1996identified in the ETSI deliverable numbering, for example, the deliverable numbers of a phase 1 UMTS standard, shall be different from those of a potential phase 2 UMTS standard.3.1.2Approval responsibilityThe work programme contains primary and secondary technical responsibilities, finalization dates and status for each deliverable. Primary technical responsibility is referred to the ETSI group which is carrying out the main part of the technical work on the deliverable, while secondary technical responsibility is referred to the ETSI groups with the most significant responsibility for consulting in a specific technical area. It should, however, be noted that the approval responsibility is with TC-SMG.The finalization dates indicated in annex C refer to the time when the UMTS deliverables are submitted to TC SMG for approval. The other deliverable milestones are Maintained in the EWP.3.1.3.UMTS document numberingAll UMTS deliverables in this work programme are allocated a specification number (identifier).The UMTS document processing is executed as defined in “Working Procedures for TC-SMG; SMG Standards Management” (GSM 01.00).3.2Details of the UMTS work programme3.2.1General (UMTS 21-series)The general UMTS ETSs describe the system concept(s) and reference model for UMTS.3.2.2Service aspects (UMTS 22-series)The UMTS Service ETSs contain the specifications (stage 1 type of descriptions) for the framework of services, terminals and environments that the UMTS system will support and the description of the service capabilities and service related requirements for the implementation of UMTS services.3.2.3Network aspects (UMTS 23-series)The UMTS network ETSs contain specifications of network functions, interfaces, operation, numbering and procedures for the implementation and provision of UMTS services. These are the foundations for choices of network architectures and network interfaces for UMTS. The UMTS network ETSs support evolutionary implementation of UMTS capabilities into existing and evolving networks.3.2.4Radio aspects (UMTS 25-series)The UMTS radio ETSs will introduce a new radio interface technology for the FPLMTS frequency bands (see figure 1) which provide radio bearer capabilities up to 144 kbits/s with full coverage and mobility and up to 2 Mbits/s with possibly limited coverage, mobility or capacity.Though the primary objective is to define the UMTS radio interface for the frequencies available in Europe (foreseen to be the frequency bands 1900 MHz - 1980 MHz / 2010 MHz - 2025 MHz / 2110 MHz - 2170 MHz for terrestrial applications and 1980 MHz - 2010 MHz / 2170 MHz - 2200 MHz for satellite applications), the standard should also possess a long term applicability for deploying UMTS services and technology in the existing European 2nd generation mobile frequency bands.Page 9SMG-TR 004 (UMTS 00.01): May 1996Figure 1: European UMTS/FPLMTS frequency bands after WARC'92 and WRC'95 decisions. 3.2.5UMTS management aspects (UMTS 32-series)One or several ETSs will be needed on management aspects of UMTS. This includes the TMN framework for UMTS, requirements on operations, administration, maintenance and management of the system etc.3.2.6Voice-band and audio aspects (UMTS 26-series)One or several ETSs will be needed on voice-band aspects of UMTS. Voice-band refers to any signal within the band 300 - 3 400 Hz. This includes description of speech codecs, other codecs, voice-band data, integration of audio coding and related issues. In the long term a merging of UMTS and GSM voice band/audio coding aspects is expected3.2.7Video aspects (UMTS 34-series)ETSs will be needed on video aspects of UMTS. This includes description of video codecs and integrated support of video services in UMTS.3.2.8Security aspects (UMTS 33-series)One or several ETSs will be needed on specific security aspects of UMTS. This includes the detailed realization of the various security mechanisms for UMTS. General security aspects are otherwise planned to be integrated in the other ETSs throughout the whole series of ETSs.3.2.9Terminal aspects (UMTS 35-series)The UMTS ETSs for terminal specify user interface (formerly man-machine interface, or MMI), UIM functions and interfaces necessary to support the UMTS service capabilities.3.2.10Interworking and internetwork signalling aspects (UMTS 24-series)One or several ETSs will be needed on interworking of UMTS with other systems. This includes service, network and protocol interworking issues. The systems to be considered include, non-UMTS satellite systems, PSTN, ISDN, PLMN, PMR, LANs etc. Evolutionary protocols (INAP, MAP) need to be considered3.2.11Conformance testing specifications (UMTS 31-series)The UMTS conformance testing ETSs define testing methods and conformance criteria for UMTS Mobile Station, Base Station, UIM and other equipment performances. These ETSs may include subparts dealing separately with physical (e.g. radio or audio) and protocol performance.It is the purpose of the description methods for ETSs to support a direct and simultaneous creation of the test standards on the basis of corresponding functional ETSs. Additionally, the conformance testing standards are aimed to clearly and easily serve two different purposes, firstly to support voluntary testing for full conformity to UMTS functional standards, and secondly the creation of legal documents (e.g. TBRs, CTRs) for type approval or market access purposes applying the relevant European directives.Page 10SMG-TR 004 (UMTS 00.01): May 19964Working structureTC SMG has been given the mandate to study and define the third generation mobile system UMTS, and SMG 5 has been set up to reflect this task. The terms of reference for SMG 5 are included in Annex D. The work on UMTS will require work in a wide range of technical areas. The work will therefore need to be well co-ordinated and organized, internally and externally, to best carry out the task.Within TC SMG, the following general guidelines for the work on UMTS apply:-TC SMG has been given the mandate for the standardization of UMTS by the ETSI Technical Assembly, and is thus the primary responsible body for the system;-within TC SMG, the overall responsibility for the study and design of the UMTS standard resides with SMG 5. SMG 5 is the system architect for UMTS;-for the UMTS standardization work, the expertise of the existing SMG STCs and other STCs outside SMG will be used as far as relevant;-as regards UMTS matters, SMG 5 co-ordinates within and outside TC SMG and its STCs the contributions to and from the ITU, RACE, ACTS, COST etc.;-the baseline material in the UMTS work programme is the primary responsibility of SMG 5, with secondary responsibility for the appropriate other STCs;Within the whole of ETSI, SMG 5 co-ordinates the work on UMTS and maintains a consistent work programme. When appropriate, e.g. when a detailed knowledge of a particular technology is required, SMG 5 shall request assistance from a TC other than SMG for assistance in the production of deliverables identified in the UMTS work programme. In addition, SMG 5 keeps direct liaisons with TCs and STCs outside SMG, when appropriate.Annex A (informative):Milestones for the standardization of UMTS Preparatory meeting of SMG 5:End 91Spectrum identified by WARC:Mid 92UMTS work programme agreed in ETSI:End 94Initial UMTS vocabulary defined:Mid 95UMTS objectives and requirements defined Mid 95Service framework defined:Mid 95Security principles defined Mid 95Framework for satellite integration defined:Mid 95System concepts and reference model defined End 96Service principles defined Mid 97Service capability aspects defined End 97Security algorithms defined:Mid 98Audi coding issues defined:End 97Video coding issues defined:End 97Voice-band, audio and video aspects ready:End 98Radio interface requirements defined:End 95Selection procedure and choice for radio transmission technologies End 96Radio interface principles defined End 97Radio interface protocols defined :Mid 98Physical radio access aspects ready:End 98Network requirements defined:End 95Network management principles defined:Mid 95Network protocols ready:End 98Network management aspects ready:End 98UMTS functional standards completed End 98Conformance specifications ready:Mid 99Possible start of service:2000 - 2005NOTE:Dates for Standards refer to TC approval for public enquiryPlanned and estimated milestones for the introduction of UMTS into service:WRC '95 resolutions on MSS bands within the FPLMTS frequencies End 1995ERO report on UMTS frequencies Mid 1996ERC decisions on UMTS frequencies End 1997Licensing policy for UMTS defined End 1998ACTS demonstrations on UMTS type of services Mid 1999First licenses for UMTS frequency band delivered End 1999Allocation of MSS bands within FPLMTS frequencies possible 1.1.2000Part of UMTS frequencies into use 1.1.2002UMTS frequency bands into use 1.1.2005 NOTE:The European plans for the implementation of UMTS are outlined in the following documents:1. Commission of the European Communities “Communication to the European Parliament and the Councilon the consultation on the Green Paper on Mobile and Personal Communications: Proposal for a CouncilResolution on the further Development of Mobile and Personal Communications in the European Union”(COM(94) 492 final/23.11.1994 Brussels2. Resolution of the European Parliament on the further development of mobile and personal communicationsin the EU (PE211.595). Unanimously adopted 19.5.19953. Council resolution on the further development of mobile and personal communication in the EuropeanUnion, 13.6.19954. UMTS Task Force Report “The Road to UMTS”, published 1.3.1996 and available from CEC DG XIIIB.Annex B (informative):Deliverables for UMTS standardization B.1Baseline materialTable B.1Annex C (informative):StandardsTable C.1Annex D (informative):Terms of Reference for ETSI/SMG5Sub Technical Committee SMG5UMTSD.1ResponsibilitySMG5 has a co-ordinating role for the Universal Mobile Telecommunications System (UMTS). Its main task is to study and define this third generation mobile system, based on the conclusions of ad-hoc group UMTS (as given in doc. TC/RES(91)34 rev 1) and ,ITU studies on FPLMTS. UMTS should also respond to emerging market needs and technology opportunities.D.2Work Plan-To study and define the objectives, requirements, framework and system concept for the standardization of UMTS:-services;-system architecture;-air interface(s);-network interfaces, functions and support requirements;-other functions and interfaces as requiredwithin the appropriate ETSI TC/STCs or other bodies.-To ensure the mutual coherence of UMTS standards-To ensure that regulatory and commercial requirements are properly addressed within UMTS system concept and work plan-To ensure timely and effective exploitation of research results in UMTS standards.- To position UMTS with developments of GSM, FPLMTS, DECT, fixed telecommunications and development outside telecommunication standardization (e.g. audio/visual source coding, information technology applications)-To develop a migration strategy towards UMTS standards implementing true 3rd generation objectives and also optimizing the use of existing standards and system implementations.-To study and recommend where new areas of standardization for UMTS are required because of market needs, system requirements or technology opportunities (e.g. adaptive terminals, Application Programming Interfaces, Mobile Broadband Systems)D.3Working methodsSMG5 should-Establish links with other TCs and STCs as well as other bodies preparing relevant standards for UMTS. The objectives behind such links will be to make use of the existing expertise, and to subcontract out defined specific tasks e.g. where a detailed knowledge of a particular technology is required.-Liaise with European funded and other research relevant to UMTS (e.g. European COST, RACE, ACTS and STM programs) on the conduct of this research if necessary.-Work with world-wide standards bodies such as the ITU-R and ITU-T with the objective of establishing a common framework of standards and detailed world-wide standards where appropriate or third generation mobile systems. It is desired to submit a European view to such bodies through TC SMG. Informal arrangements where one ETSI member submits a contribution with the support of other members are also possible.-Co-ordinate, agree and keep under review a programme (TCR-TR 015) defining the work to be undertaken and the resources required to enable it to be successfully completed, and to submitsuch work programme for approval to TC SMG and to any other relevant bodies on a regular basis(e.g. annually).-Work in close liaison with SMG1-4/6-9 and other TC/STCs for the proper planning and timing of UMTS standards falling under mandate of these groupsD.4LiaisonsSMG5 has direct liaisons with appropriate ETSI TCs and STCs on issues concerning UMTS standards. Examples are TCs NA, RES, SES, SPS, TE, and TM. In addition, SMG5 has direct liaison with CEPT/ERC, with information to RES/RPM, on UMTS spectrum issues, and should further liaise in coordination with SMG with other regional/national standardisation bodies and processes relevant to third generation mobile systems (e.g. FAMOUS, RAST, GSC).D.5Specific guidance for SMG5 work in the years 1996 - 1997SMG5 should-propose a revised UMTS WP in early 1996-complete a high level UMTS definition (ETRs) during 1996-define the system concept for UMTS in during 1996, for the support and technical coordination of ETS work-support the detailed standardization with e.g. requirement and framework documents, review of draft documents from other groups, joint meetings, and exchange of experts and groups from SMG5 to other SMG STSc.-aim at supporting and contributing to a European overall plan for UMTS, including, in addition to technical objectives and requirements, frequency band and regulatory aspectsHistory。

3gpp标准 文档

3gpp标准 文档

3GPP标准概述和组织架构首先3GPP标准化组织主要包括项目合作组(PCG)和技术规范组(TSG)两类。

其中PCG工作组主要负责3GPP总体管理、时间计划、工作的分配等,具体的技术工作则由各TSG工作组完成。

目前,3GPP包括3个TSG,分别负责EDGE无线接入网(GERAN)、无线接入网(RAN)、系统和业务方面(SA)、核心网和终端(CT)。

每一个TSG进一步分为不同的工作子组,每个工作子组分配具体的任务。

例如SA WG1负责需求制定,SA WG2负责系统架构,SA WG3负责安全,SA WG5负责网络管理等等。

又如,TSG RAN 划分为5个工作小组,分别是RAN层1规范组、层2和层3规范组、lub/Lur/Lu规范与OAM需求规范组。

无线性能与协议规范组和终端一致性测试规范组。

目前,3GPP已经正式发布R99、R4、R5、R6、R7、R8共6个版本。

R8版本于2009年3月正式发布,R9的标准工作也已正式启用。

其中,R99-R7版本已基本稳定,R8部分特征正在完善过程中。

另外,3GPP相关的标准工作可以分为两个阶段:SI(Study Item,技术可行性研究阶段)和WI(Work Item,具体技术规范撰写阶段)。

SI阶段主要以研究的形式确定系统的基本框架,并进行主要的候选技术选择,以对标准化的可行性进行判断。

WI阶段分为Stage2、Stage3两个子阶段。

其中,Stage2主要通过对SI阶段中初步讨论的系统框架进行确认,同时进一步完善技术细节。

该阶段规范并不能够直接用于设备开发,而是对系统的一个总体描述,仅是一个参考规范,根据Stage2形成的初步设计,进一步验证了系统的性能。

Stage3主要是确定具体的流程、算法及参数等。

3GPP各版本针对核心网的演进1 R99阶段:这是3G标准的第一个阶段,2000年3月发布。

延续了GSM/GPRS系统的核心网系统结构,即分为电路域和分组域分别处理语音和数据业务。

3GPP规范-R15-TS38系列NR38816-f00

3GPP规范-R15-TS38系列NR38816-f00

3GPP TR 38.816 V15.0.0 (2017-12)Technical Report3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Study on CU-DU lower layer split for NR;(Release 15)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Report is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.Keywords<keyword[, keyword]>3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.U MTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members an d of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationContentsForeword (4)1 Scope (5)2 References (5)3 Definitions, symbols and abbreviation (5)3.1 Definitions (5)3.2 Symbols ........................................................................................................................... 错误!未定义书签。

5G标准-3GPP TS 38.401

5G标准-3GPP TS 38.401

5G标准-3GPP TS 38.401无线接入网NG-RAN1. 基本原理信令和数据传输网络的逻辑分离。

NG-RAN和5GC功能与传输功能完全分离。

RRC连接的移动性完全由NG-RAN控制。

2. 基本架构Uu和NG接口上的协议分为两种结构:用户平面协议这些是实现实际PDU会话服务的协议,即通过接入层承载用户数据。

控制平面协议这些是用于从不同方面(包括请求服务,控制不同传输资源,切换等)控制PDU会话和UE 与网络之间的连接的协议。

还包括用于透明传输NAS消息的机制。

注:CM,SM:这举例说明了UE和5GC之间的一组NAS控制协议。

这些协议的协议体系结构的演变超出了本文档的范围。

NG-RAN分为无线网络层(RNL)和传输网络层(TNL):NG-RAN架构,即NG-RAN逻辑节点和它们之间的接口,被定义为RNL的一部分对于每个NG-RAN接口(NG,Xn,F1),指定相关的TNL协议和功能。

TNL为用户平面传输,信令传输提供服务3. NG-RAN架构NG-RAN由一组通过NG接口连接到5GC的gNB组成。

其中:gNB-CU是集中单元,包括RRC和PDCP;gNB-DU是分布单元,包括RLC/MAC/PHY;NG为逻辑接口,是无线接入网和5G核心网之间的接口Xn为逻辑接口,是无线接入网之间的接口F1为逻辑接口,是gNB-CU和gNB-DU之间的接口en-gNB是在非独立NSA组网下,和4G核心网对接的5G基站ng-eNB是在非独立NSA组网下,升级后的可以和5G核心网对接的4G基站NE-DC(NR eNB Dual Connection)架构:在NSA非独立组网下,5G NR基站和4G eNB基站的双连接架构NGEN-DN(NG-Enb NR Dual Connection)架构:在NSA非独立组网下,5G NR基站和升级后的4G ng-eNB基站的双连接架构AMF:接入和移动管理功能gNB可以由gNB-CU和一个或多个gNB-DU组成4. gNB内部架构其中:gNB-CU-CP是gNB集中单元的控制面gNB-CU-UP是gNB集中单元的用户面gNB可以包括gNB-CU-CP,多个gNB-CU-UP和多个gNB-DUgNB-CU-CP通过F1-C接口连接到gNB-DUgNB-CU-UP通过F1-U接口连接到gNB-DUgNB-CU-UP通过E1接口连接到gNB-CU-CP5. NG-RAN标识符5.1 AP ID当在NG-RAN节点或AMF中创建新的UE相关逻辑连接时,分配应用协议标识(AP ID)。

3GPP规范-R15-TS38系列NR38104-f00

3GPP规范-R15-TS38系列NR38104-f00

3GPP TS 38.104 V15.0.0 (2017-12)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;NR;Base Station (BS) radio transmission and reception(Release 15)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMT S™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationContentsForeword (9)1Scope (10)2References (10)3Definitions, symbols and abbreviations (10)3.1Definitions (10)3.2Symbols (14)3.3Abbreviations (14)4General (16)4.1Relationship with other core specifications (16)4.2Relationship between minimum requirements and test requirements (16)4.3Conducted and radiated requirement reference points (16)4.3.1BS type 1-C (16)4.3.2BS type 1-H (17)4.3.3BS type 1-O and BS type 2-O (18)4.4Base station classes (18)4.5Regional requirements (19)4.6Applicability of requirements (19)4.7Requirements for contiguous and non-contiguous spectrum (20)4.8Requirements for BS capable of multi-band operation (20)4.9OTA co-location with other base stations (22)5Operating bands and channel arrangement (23)5.1General (23)5.2Operating bands (23)5.3BS channel bandwidth (24)5.3.1General (24)5.3.2Maximum transmission bandwidth configuration (24)5.3.3Minimum guardband and transmission bandwidth configuration (24)5.3.4RB alignment with different numerologies (25)5.3.5BS channel bandwidth per operating band (25)5.4Channel arrangement (27)5.4.1Channel spacing (27)5.4.1.1Channel spacing for adjacent NR carriers (27)5.4.1.2Channel spacing for CA (27)5.4.2Channel raster (28)5.4.2.1Channel raster and numbering (28)5.4.2.2Channel Raster to Resource Element Mapping (28)5.4.2.3Channel raster entries for each operating band (28)5.4.3Synchronization raster (29)5.4.3.1Synchronization raster and numbering (29)5.4.3.2Synchronization raster to synchronization block resource element mapping (30)5.4.3.3Synchronization raster entries for each operating band (30)6Conducted transmitter characteristics (32)6.1General (32)6.2Base station output power (32)6.2.1General (32)6.2.2Minimum requirement for BS type 1-C (32)6.2.3Minimum requirement for BS type 1-H (32)6.2.4Additional requirements (regional) (33)6.3Output power dynamics (33)6.3.1General (33)6.3.2RE power control dynamic range (33)6.3.2.1General (33)6.3.2.2Minimum requirement for BS type 1-C and 1-H (33)6.3.3.1General (33)6.3.3.2Minimum requirement for BS type 1-C and 1-H (34)6.4Transmit ON/OFF power (34)6.4.1Transmitter OFF power (34)6.4.1.1General (34)6.4.1.2Minimum requirement for type 1-C (34)6.4.1.3Minimum requirement for type 1-H (34)6.4.2Transmitter transient period (34)6.4.2.1General (34)6.4.2.2Minimum requirement for type 1-C (35)6.4.2.3Minimum requirement for type 1-H (35)6.5Transmitted signal quality (35)6.5.1Frequency error (35)6.5.1.1General (35)6.5.1.2Minimum requirement for BS type 1-C and 1-H (36)6.5.2Modulation quality (36)6.5.2.1General (36)6.5.2.2Minimum Requirement for BS type 1-C and 1-H (36)6.5.2.3EVM Frame Structure for Measurement (36)6.5.3Time alignment error (36)6.5.3.1General (36)6.5.3.2Minimum requirement for BS type 1-C and 1-H (37)6.6Unwanted emissions (37)6.6.1General (37)6.6.2Occupied bandwidth (38)6.6.2.1General (38)6.6.2.2Minimum requirement for BS type 1-C and 1-H (38)6.6.3Adjacent Channel Leakage Power Ratio (38)6.6.3.1General (38)6.6.3.2Basic limits (39)6.6.3.3Minimum requirement for BS type 1-C (40)6.6.3.4Minimum requirement for BS type 1-H (40)6.6.4Operating band unwanted emissions (41)6.6.4.1General (41)6.6.4.2Basic limits (42)6.6.4.2.1Basic limits for Wide Area BS (Category A) (42)6.6.4.2.2Basic limits for Wide Area BS (Category B) (42)6.6.4.2.3Basic limits for Medium Range BS (Category A and B) (44)6.6.4.2.4Basic limits for Local Area BS (Category A and B) (44)6.6.4.2.5Basic limits for additional requirements (45)6.6.4.2.5.1Limits in FCC Title 47 (45)6.6.4.3Minimum requirements for BS type 1-C (45)6.6.4.4Minimum requirements for BS type 1-H (45)6.6.5Transmitter spurious emissions (45)6.6.5.1General (45)6.6.5.2Basic limits (46)6.6.5.2.1Tx spurious emissions (46)6.6.5.2.2Protection of the BS receiver of own or different BS (46)6.6.5.2.3Additional spurious emissions requirements (47)6.6.5.2.4Co-location with other base stations (52)6.6.5.3Minimum requirements for BS type 1-C (55)6.6.5.4Minimum requirements for BS type 1-H (55)6.7Transmitter intermodulation (56)6.7.1General (56)6.7.2Minimum requirements for BS type 1-C (56)6.7.2.1Co-location minimum requirements (56)6.7.2.2Additional requirements (57)6.7.3Minimum requirements for BS type 1-H (57)6.7.3.1Co-location minimum requirements (57)6.7.3.2Intra-system minimum requirements (58)7Conducted receiver characteristics (59)7.1General (59)7.2Reference sensitivity level (59)7.2.1General (59)7.2.2Minimum requirements for BS type 1-C and BS type 1-H (59)7.3Dynamic range (60)7.3.1General (60)7.3.2Minimum requirement for BS type 1-C and BS type 1-H (60)7.4In-band selectivity and blocking (63)7.4.1Adjacent Channel Selectivity (ACS) (63)7.4.1.1General (63)7.4.1.2Basic limits (63)7.4.1.3Minimum requirement for BS type 1-C (65)7.4.1.4Minimum requirement for BS type 1-H (65)7.4.2In-band blocking (65)7.4.2.1General (65)7.4.2.2Basic limits (65)7.4.2.3Minimum requirement for BS type 1-C (66)7.4.2.4Minimum requirement for BS type 1-H (66)7.5Out-of-band blocking (67)7.5.1General (67)7.5.2Basic limits (67)7.5.3Minimum requirement for BS type 1-C (67)7.5.4Minimum requirement for BS type 1-H (67)7.6Receiver spurious emissions (67)7.6.1General (67)7.6.2Basic limits (68)7.6.3Minimum requirement for BS type 1-C (68)7.6.4Minimum requirement for BS type 1-H (68)7.7Receiver intermodulation (69)7.7.1General (69)7.7.2Minimum requirement for BS type 1-C and BS type 1-H (69)7.8In-channel selectivity (72)7.8.1General (72)7.8.2Minimum requirement for BS type 1-C and BS type 1-H (72)8Performance requirements (74)9Radiated transmitter characteristics (75)9.1General (75)9.2Radiated transmit power (75)9.2.1General (75)9.2.2Minimum requirement for BS type 1-H and BS type 1-O (75)9.2.3Minimum requirement for BS type 2-O (76)9.3OTA base station output power (76)9.3.1General (76)9.3.2Minimum requirement for BS type 1-O (76)9.3.3Minimum requirement for BS type 2-O (76)9.3.4 Additional requirements (regional) (76)9.4OTA output power dynamics (77)9.4.1General (77)9.4.2OTA RE power control dynamic range (77)9.4.2.1General (77)9.4.2.2Minimum requirement for BS type 1-O (77)9.4.3 OTA total power dynamic range (77)9.4.3.1General (77)9.4.3.2Minimum requirement for BS type 1-O (77)9.4.3.3Minimum requirement for BS type 2-O (77)9.5OTA transmit ON/OFF power (78)9.5.1General (78)9.5.2Transmitter OFF power (78)9.5.2.2Minimum requirement for type BS type 1-O (78)9.5.2.3Minimum requirement for type BS type 2-O (78)9.5.3OTA transient period (78)9.5.3.1General (78)9.5.3.1Minimum requirement for BS type 1-O (79)9.5.3.2Minimum requirement for BS type 2-O (79)9.6OTA transmitted signal quality (79)9.6.1OTA frequency error (79)9.6.1.1General (79)9.6.1.2Minimum requirement for BS type 1-O (79)9.6.1.3Minimum requirement for BS type 2-O (79)9.6.2OTA modulation quality (80)9.6.2.1General (80)9.6.2.2Minimum Requirement for BS type 1-O (80)9.6.2.3Minimum Requirement for BS type 2-O (80)9.6.3OTA time alignment error (80)9.6.3.1General (80)9.6.3.2Minimum requirement for BS type 1-O (80)9.6.3.3Minimum requirement for BS type 2-O (81)9.7OTA Unwanted emissions (81)9.7.1General (81)9.7.2OTA occupied bandwidth (82)9.7.2.1General (82)9.7.2.2Minimum requirement for BS type 1-O and 2-O (82)9.7.3OTA Adjacent Channel Leakage Power Ratio (ACLR) (82)9.7.3.1General (82)9.7.3.2Minimum requirement for BS type 1-O (82)9.7.3.3Minimum requirement for BS type 2-O (82)9.7.4OTA out-of-band emissions (83)9.7.4.1General (83)9.7.4.2Minimum requirement for BS type 1-O (83)9.7.4.3Minimum requirement for BS type 2-O (83)9.7.4.3.1General (83)9.7.4.3.2OTA spectrum emission mask (84)9.7.5OTA transmitter spurious emissions (84)9.7.5.1General (84)9.7.5.2Minimum requirement for BS type 1-O (85)9.7.5.3Minimum requirement for BS type 2-O (85)9.7.5.3.1General (85)9.7.5.3.2General OTA transmitter spurious emissions requirements (85)9.7.5.3.3Additional OTA transmitter spurious emissions requirements (85)9.8OTA transmitter intermodulation (85)9.8.1General (85)9.8.2Minimum requirement for BS type 1-O (85)10Radiated receiver characteristics (87)10.1General (87)10.2OTA sensitivity (87)10.2.1BS type 1-H and BS type 1-O (87)10.2.1.1General (87)10.2.1.2Minimum requirement (88)10.2.2BS type 2-O (88)10.3OTA reference sensitivity level (88)10.3.1General (88)10.3.2Minimum requirement for BS type 1-O (88)10.3.3Minimum requirement for BS type 2-O (89)10.4OTA Dynamic range (90)10.4.1General (90)10.4.2Minimum requirement for BS type 1-O (90)10.5OTA in-band selectivity and blocking (92)10.5.1OTA adjacent channel selectivity (92)10.5.1.2Minimum requirement for BS type 1-O (92)10.5.1.3Minimum requirement for BS type 2-O (94)10.5.2OTA in-band blocking (95)10.5.2.1General (95)10.5.2.2OTA in-band blocking for BS type 1-O (95)10.5.2.3OTA in-band blocking for BS type 2-O (97)10.6OTA out-of-band blocking (98)10.6.1General (98)10.6.2Minimum requirement for BS type 1-O (98)10.6.2.1General minimum requirement (98)10.6.2.2Co-location minimum requirement (99)10.7OTA receiver spurious emissions (100)10.7.1General (100)10.7.2Minimum requirement for BS type 1-O (100)10.7.3Minimum requirement for BS type 2-O (100)10.8OTA receiver intermodulation (101)10.8.1General (101)10.8.2Minimum requirement for BS type 1-O (101)10.8.3Minimum requirement for BS type 2-O (103)10.9OTA in-channel selectivity (104)10.9.1General (104)10.9.2Minimum requirement for BS type 1-O (104)10.9.3Minimum requirement for BS type 2-O (105)11Radiated performance requirements (107)Annex A (normative): Reference measurement channels (108)A.1Fixed Reference Channels for receiver sensitivity and in-channel selectivity (QPSK, R=1/3) (108)A.2Fixed Reference Channels for dynamic range (16QAM, R=2/3) (109)Annex B (normative): Error Vector Magnitude (FR1) (110)B.1Reference point for measurement (110)B.2Basic unit of measurement (110)B.3Modified signal under test (111)B.4Estimation of frequency offset (111)B.5Estimation of time offset (111)B.5.1General (111)B.5.2Window length (112)B.6Estimation of TX chain amplitude and frequency response parameters (112)B.7Averaged EVM (112)Annex C (normative): Error Vector Magnitude (FR2) (114)C.1Reference point for measurement (114)C.2Basic unit of measurement (114)C.3Modified signal under test (115)C.4Estimation of frequency offset (115)C.5Estimation of time offset (115)C.5.1General (115)C.5.2Window length (116)C.6Estimation of TX chain amplitude and frequency response parameters (116)C.7Averaged EVM (117)Annex D (informative): Change history (119)ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document establishes the minimum RF characteristics and minimum performance requirements of NR Base Station (BS).2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.- For a specific reference, subsequent revisions do not apply.- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the sameRelease as the present document.[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".[2] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain".[3] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions".[4] 3GPP TR 25.942: "RF system scenarios".[5] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformancetesting".[6] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing; Part 2: Radiated conformancetesting".[7] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for theterrestrial component of International Mobile Telecommunications-2000".[8] “Title 47 of the Code of Federal Regulations (CFR)”, Federal Communications Commission.[9] 3GPP TR 38.211: "NR; Physical channels and modulation".3 Definitions, symbols and abbreviations3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].antenna connector: connector at the conducted interface of the BS type 1-Cactive transmitter unit: transmitter unit which is ON, and has the ability to send modulated data streams that are parallel and distinct to those sent from other transmitter units to a BS type 1-C antenna connector, or to one or more BS type 1-H TAB connectors at the transceiver array boundaryBase Station RF Bandwidth: RF bandwidth in which a base station transmits and/or receives single or multiple carrier(s) within a supported operating bandNOTE: In single carrier operation, the Base Station RF Bandwidth is equal to the channel bandwidth.3GPP TS 38.104 V15.0.0 (2017-12) Release 1511beam: beam (of the antenna) is the main lobe of the radiation pattern of an antenna arrayNOTE: For certain BS antenna array, there may be more than one beam.beam centre direction: direction equal to the geometric centre of the half-power contour of the beambeam direction pair: data set consisting of the beam centre direction and the related beam peak directionbeam peak direction: direction where the maximum EIRP is foundbeamwidth: beam which has a half-power contour that is essentially elliptical, the half-power beamwidths in the two pattern cuts that respectively contain the major and minor axis of the ellipseBS channel bandwidth: RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlinkNOTE: The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.NOTE: It is possible for the BS to transmit to and/or receive from one or more UE Bandwidth parts that are smaller than or equal to the BS transmission bandwidth configuration, in any part of the BS transmissionbandwidth configuration.BS type 1-C: NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual antenna connectorsBS type 1-H: NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual TAB connectors and OTA requirements defined at RIBBS type 1-O: NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIBBS type 2-O: NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIBco-location reference antenna: a passive antenna used as reference for base station to base station co-location requirements[Inter RF Bandwidth gap: frequency gap between two consecutive Base Station RF Bandwidths that are placed within two supported operating bands]maximum carrier output power: mean power level measured per carrier at the indicted interface, during the transmitter ON period in a specified reference conditionmaximum carrier TRP output power: mean power level measured per RIB during the transmitter ON period for a specific carrier in a specified reference condition and corresponding to the declared rated carrier TRP output power (P rated,c,TRP)maximum total output power: mean power level measured within the operating band at the indicated interface, during the transmitter ON period in a specified reference conditionmaximum total TRP output power: mean power level measured per RIB during the transmitter ON period in a specified reference condition and corresponding to the declared rated total TRP output power (P rated,t,TRP) measurement bandwidth: RF bandwidth in which an emission level is specifiedminSENS RoAoA: The reference RoAoA associated with the OSDD with the lowest declared EISmulti-band antenna connector:antenna connector supporting operation in multiple operating bands through common active electronic component(s)NOTE: For common TX and RX antenna connectors, the definition applies where common active electronic components are in the transmit path and/or in the receive path.multi-band RIB:operating band specific RIB which is paired with one or more additional operating band specific RIBs where the multiple bands are supported through common active electronic component(s)3GPP。

3Gpp38.XX系列介绍

3Gpp38.XX系列介绍

3GPP TS 38.xx 系列规范涵盖了与5G无线通信系统相关的多个协议,每个规范都有不同的编号,用于讨论不同的方面和功能。

以下是一些重要的3GPP TS 38.xx 系列规范及其主要内容的简要介绍:1.3GPP TS 38.101 系列:o TS 38.101-1:5G系统架构的概述和一般要求,包括测试方法和测试设备的一般要求。

o TS 38.101-2:5G系统的协议体系结构,包括核心网和无线接入网的协议体系结构。

o TS 38.101-3:5G系统的信令协议和流程,包括核心网和无线接入网的信令流程。

o TS 38.101-4:5G系统的安全性能规范,描述了与安全相关的测试和性能要求。

2.3GPP TS 38.104 系列:基于IP的核心网络(NGCN)介绍o TS 38.104-1:5G系统的系统级能力测试和性能测试,包括测试用例和测试环境的定义。

o TS 38.104-2:5G系统的性能测试结果的表示和定义。

3.3GPP 38.106:o3GPP 38.106规范是关于5G新无线接口的规范,主要涉及了5G新空中接口的技术规范,包括物理层和射频(RF)层的要求。

o38.106规范详细定义了5G NR(New Radio)的物理层特性,如载波频率、信号结构、多路访问方法、信道编码等。

o这个规范为5G系统的实际实施提供了技术指导,确保了不同厂家的设备和网络能够互操作,并满足5G通信的性能和可靠性要求。

4.3GPP 38.108:o3GPP 38.108规范是关于5G系统架构的规范,提供了有关5G网络架构和协议的详细信息。

o这个规范定义了5G核心网络和无线接入网络之间的接口,包括用户面和控制面的协议。

o38.108规范还包括了与服务质量(QoS)、移动性管理、安全性、用户身份验证和连接管理等相关的规定。

o该规范的主要目标是确保5G系统的各个组件能够协同工作,为5G提供高性能、低延迟和广泛的应用支持。

3GPP LTE规范梳理

3GPP LTE规范梳理

1.3GPP标准体系3GPP技术规范组(technical specification group, TSG)的工作分为四个工作组,即GSM/EDGE无线接入网(GERAN)、无线接入网(RAN)、业务和系统(SA)、核心网和终端(CT)。

其中,GERAN工作组负责GSM/GPRS/EDGE无线接入网技术规范的制定,范围有Layer1、Layer2、Layer3规范,Iu、Iub、Iur接口规范,基站的无线性能规范和一致性测试规范等;RAN工作组负责3GPP UTRAN/E-UTRAN 的无线接入网技术规范的制定;SA工作组负责3GPP业务与系统方面的技术规范制定,包括业务能力,系统架构,安全,编码,网络管理等;CT工作组负责3GPP 核心网和终端方面的技术规范的制定,范围有移动性管理,呼叫控制,核心网内网元间信令,网际互联的定义,核心网操作维护需求、业务能力协议,端到端互联,终端的一致性测试等。

针对于LTE项目中,TSG RAN负责开发LTE无线侧规范,分组核心演进(EPC)规范是由TSG SA和TSG CT制定的。

图 1 3GPP技术标准分类2.LTE核心网相关标准2.1 EPC相关架构等相关体系标准号涵盖内容TS 23.401 LTE系统的整体架构(各网元功能,QoS,用户面和控制面的接口描述和相关数据信令流)TS 29.305 主要介绍了LTE系统interworking场景中有关的基于MAP的Gr,Gf接口和基于Diameter的S6a,S13,S13a接口)TS 29.805 主要分析了LTE系统interworking的可行性TS 24.301 EPS中的NAS协议上述所述的标准中,涉及到PCC部分的标准集合如下:标准号涵盖内容TS 23.203 策略与计费控制体系架构TS 29.212 策略与计费控制Gx接口TS 29.213 策略与计费控制信令流和QoS参数映射TS 29.214 策略与计费控制Rx接口TS 29.215 策略与计费控制S9接口TS 29.219 策略与计费控制Sy接口TS 32.240 电信管理、计费管理、计费架构和原理3.无线侧相关标准LTE的规范采用与WCDMA规范类似的表示方式,使用的是以36开头的编号方式。

3GPP规范-R15-TS38系列NR38331-f00

3GPP规范-R15-TS38系列NR38331-f00

3GPP规范-R15-TS38系列NR38331-f003GPP TS 38.331 V15.0.0 (2017-12)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access NetworkNR Radio Resource Control (RRC) protocol specification(Release 15)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internet/doc/216b4a3b32d4b14e852458fb770bf78a64293a9c.htmlCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UM TS? is a Trade Mark of ETSI registered for the benefit of its members3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE? is aTrade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM? and the GSM logo are registered and owned by the GSM AssociationContentsForeword (8)1Scope (9)2References (9)3Definitions, symbols and abbreviations (10)3.1Definitions (10)3.2Abbreviations (10)4General (11)4.1Introduction (11)4.2Architecture (12)4.2.1UE states and state transitions including inter RAT (12)4.2.2Signalling radio bearers (14)4.3Services (14)4.3.1Services provided to upper layers (14)4.3.2Services expected from lower layers (14)4.4Functions (14)5Procedures (15)5.1General (15)5.1.1Introduction (15)5.1.2General requirements (16)5.2System information (16)5.2.1Introduction (16)5.2.2System information acquisition (17)5.2.2.1General UE requirements (17)5.2.2.2SI validity and need to (re)-acquire SI (17)5.2.2.2.1SI validity (18)5.2.2.2.2SI change indication and PWS notification (18)5.2.2.3Acquisition of System Information (18)5.2.2.3.1Acquisition of MIB and SIB1 (18)5.2.2.3.2Acquisition of an SI message (19)5.2.2.3.3Request for on demand system information (20)5.2.2.4 Actions upon receipt of SI message (20)5.2.2.4.1Actions upon reception of the MasterInformationBlock (20)5.2.2.4.2Actions upon reception of the SystemInformationBlockType1 (21)5.2.2.4.3Actions upon reception of SystemInformationBlockTypeX (21) 5.2.2.5Essential system information missing (21)5.3Connection control (21)5.3.1Introduction (22)5.3.2Paging (22)5.3.3RRC connection establishment (22)5.3.4Initial security activation (22)5.3.5RRC reconfiguration (22)5.3.5.1General (22)5.3.5.2Initiation (23)5.3.5.3Reception of an RRCReconfiguration by the UE (23)5.3.5.4Secondary cell group release (24)5.3.5.5Cell Group configuration (24)5.3.5.5.1General (24)5.3.5.5.2Reconfiguration with sync (25)5.3.5.5.3RLC bearer release (26)5.3.5.5.4RLC bearer addition/modification (26)5.3.5.5.5MAC entity configuration (27)5.3.5.5.6RLF Timers & Constants configuration (27)5.3.5.5.7SpCell Configuration (27)5.3.5.5.8SCell Release (27)5.3.5.6Radio Bearer configuration (28)5.3.5.6.1General (28)5.3.5.6.2SRB release (28)5.3.5.6.3SRB addition/ modification (28)5.3.5.6.4DRB release (29)5.3.5.6.5DRB addition/ modification (29)5.3.5.7Full configuration (30)5.3.5.9Reconfiguration failure (32)5.3.5.9.1Integrity check failure (32)5.3.5.9.2Inability to comply with RRCReconfiguration (32)5.3.5.9.3T304 expiry (Reconfiguration with sync Failure) (32)5.3.6Counter check (33)5.3.7RRC connection re-establishment (33)5.3.8RRC connection release (33)5.3.9RRC connection release requested by upper layers (33)5.3.10Radio resource configuration (33)5.3.11Radio link failure related actions (33)5.3.11.1Detection of physical layer problems in RRC_CONNECTED (33)5.3.11.2Recovery of physical layer problems (33)5.3.11.3Detection of radio link failure (34)5.3.12UE actions upon leaving RRC_CONNECTED (34)5.3.13UE actions upon PUCCH/SRS release request (35)5.4Inter-RAT mobility (35)5.5Measurements (35)5.5.1Introduction (35)5.5.2Measurement configuration (37)5.5.2.1General (37)5.5.2.2Measurement identity removal (38)5.5.2.3Measurement identity addition/ modification (38)5.5.2.4Measurement object removal (38)5.5.2.5Measurement object addition/ modification (39)5.5.2.6Reporting configuration removal (40)5.5.2.7Reporting configuration addition/ modification (40)5.5.2.8Quantity configuration (41)5.5.2.9Measurement gap configuration (41)5.5.2.10Reference signal measurement timing configuration (41)5.5.3Performing measurements (41)5.5.3.1General (41)5.5.3.2Layer 3 filtering (43)5.5.3.3Derivation of measurement results (43)5.5.4Measurement report triggering (44)5.5.4.1General (44)5.5.4.2Event A1 (Serving becomes better than threshold) (46)5.5.4.3Event A2 (Serving becomes worse than threshold) (46)5.5.4.4Event A3 (Neighbour becomes offset better than PCell/ PSCell) (47)5.5.4.5Event A4 (Neighbour becomes better than threshold) (47)5.5.4.6Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better than threshold2) (48)5.5.4.7Event A6 (Neighbour becomes offset better than SCell) (49)5.5.5Measurement reporting (50)5.5.5.1General (50)5.5.5.2Reporting of beam measurement information (52)5.6UE capabilities (52)5.6.1UE capability transfer (52)5.7Other (53)5.7.1DL information transfer (53)5.7.2UL information transfer (53)5.7.3SCG failure information (53)5.7.3.1General (53)5.7.3.2Initiation (54)5.7.3.4Setting the contents of FailureReportSCG-ToOtherRAT (55) 6Protocol data units, formats and parameters (ASN.1) (56)6.1General (56)6.1.1Introduction (56)6.1.2Need codes for optional downlink fields (56)6.2RRC messages (57)6.2.1General message structure (57)–NR-RRC-Definitions (57)–BCCH-BCH-Message (58)–DL-DCCH-Message (58)–UL-DCCH-Message (59)6.2.2Message definitions (59)–MIB (59)–MeasurementReport (61)–RRCReconfiguration (61)–RRCReconfigurationComplete (63)–SIB1 (64)6.3RRC information elements (65)–SetupRelease Information Element (65)6.3.1System information blocks (65)6.3.2Radio resource control information elements (65)–DRB-Identity (65)–BandwidthPart-Config (66)–CellGroupConfig (67)–CellIndexList (69)–ControlResourceIndex (70)–CrossCarrierSchedulingConfig (70)–CSI-MeasConfig (71)–FailureReportSCG-ToOtherRAT (78)–FrequencyInfoUL (79)–LogicalChannelConfig (80)–MAC-CellGroupConfig (81)–MeasConfig (86)–MeasId (87)–MeasIdToAddModList (88)–MeasObjectEUTRA (88)–MeasObjectId (88)–MeasObjectNR (89)–MeasObjectToAddModList (94)–MeasResults (95)–PDCCH-Config (99)–PDCP-Config (102)–PDSCH-Config (106)–PhysCellId (109)–PUCCH-Config (109)–PUSCH-Config (112)–Q-OffsetRange (115)–QuantityConfig (115)–RACH-ConfigCommon (116)–RACH-ConfigDedicated (118)–RadioBearerConfig (119)–ReportConfigId (121)–ReportConfigNR (121)–ReportConfigToAddModList (125)–RLC-Config (126)–RLF-TimersAndConstants (128)–SCellIndex (129)–SchedulingRequest-Config (129)–SchedulingRequestResource-Config (130)–SDAP-Config (130)–ServCellIndex (132)–ServingCellConfigCommon (133)–ServingCellConfigDedicated (135)–SRB-Identity (137)–SPS-Config (137)–SRS-Config (138)–SubcarrierSpacing (140)6.3.3UE capability information elements (141)–BandCombinationList (141)–RAT-Type (141)–UE-CapabilityRAT-ContainerList (142)–UE-MRDC-Capability (142)–UE-NR-Capability (143)6.3.4Other information elements (146)6.4RRC multiplicity and type constraint values (146)–Multiplicity and type constraint definitions (146)7Variables and constants (148)7.1Timers (148)7.1.1Timers (Informative) (148)7.1.2Timer handling (148)7.2Counters (148)7.3Constants (148)7.4UE variables (149)–VarMeasConfig (149)–VarMeasReportList (149)8Protocol data unit abstract syntax (151)8.1General (151)8.2Structure of encoded RRC messages (151)8.3Basic production (151)8.4Extension (152)8.5Padding (152)9Specified and default radio configurations (152) 9.1Specified configurations (152)9.2Default radio configurations (153)9.2.1SRB configurations (153)9.2.1.1SRB1/SRB1S (153)9.2.1.2SRB2/SRB2S (153)9.2.1.3SRB3 (154)9.2.2SRB configurations (154)9.2.2.1SRB1/SRB1S (154)9.2.2.2SRB2/SRB2S (155)9.2.2.3SRB3 (155)10Generic error handling (155)10.1General (155)10.2ASN.1 violation or encoding error (155)10.3Field set to a not comprehended value (156)10.4Mandatory field missing (156)10.5Not comprehended field (157)11Radio information related interactions between network nodes (158) 11.1General (158)11.2Inter-node RRC messages (158)11.2.1General (158)11.2.2Message definitions (158)–HandoverCommand (158)–HandoverPreparationInformation (159)–SCG-Config (160)–SCG-ConfigInfo (162)11.3Inter-node RRC information element definitions (163)–CandidateCellInfoList (163)11.4Inter-node RRC multiplicity and type constraint values (164)12Processing delay requirements for RRC procedures (165)Annex A (informative):Guidelines, mainly on use of ASN.1 (165)A.1Introduction (165)A.2Procedural specification (166)A.2.1General principles (166)A.2.2More detailed aspects (166)A.3PDU specification (166)A.3.1General principles (166)A.3.1.1ASN.1 sections (166)A.3.1.2ASN.1 identifier naming conventions (167)A.3.1.3Text references using ASN.1 identifiers (169)A.3.2High-level message structure (170)A.3.3Message definition (171)A.3.4Information elements (173)A.3.5Fields with optional presence (174)A.3.6Fields with conditional presence (175)A.3.7Guidelines on use of lists with elements of SEQUENCE type (176)A.3.8Guidelines on use of parameterised SetupRelease type (176)A.4Extension of the PDU specifications (177)A.4.1General principles to ensure compatibility (177)A.4.2Critical extension of messages and fields (177)A.4.3Non-critical extension of messages (180)A.4.3.1General principles (180)A.4.3.2Further guidelines (180)A.4.3.3Typical example of evolution of IE with local extensions (181)A.4.3.4Typical examples of non critical extension at the end of a message (183)A.4.3.5Examples of non-critical extensions not placed at the default extension location (183)–ParentIE-WithEM (183)–ChildIE1-WithoutEM (184)–ChildIE2-WithoutEM (185)A.5Guidelines regarding inclusion of transaction identifiers in RRC messages (186)A.6Guidelines regarding use of need codes (186)Annex B (informative): Change history (188)ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN. The scope of the present document also includes:- the radio related information transported in a transparent container between source gNB and target gNB upon inter gNB handover;- the radio related information transported in a transparent container between a source or target gNB and another system upon inter RAT handover.- the radio related information transported in a transparent container between a source eNB and target gNB during E-UTRA-NR Dual Connectivity.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.- For a specific reference, subsequent revisions do not apply.- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the sameRelease as the present document.[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".[2] 3GPP TS 38.300: "NR; Overall description; Stage 2".[3] 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification".[4] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification".[5] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) protocol specification".[6] ITU-T Recommendation X.680 (07/2002) "Information Technology - Abstract Syntax NotationOne (ASN.1): Specification of basic notation" (Same as the ISO/IEC International Standard 8824-1).[7] ITU-T Recommendation X.681 (07/2002) "Information Technology - Abstract Syntax NotationOne (ASN.1): Information object specification" (Same as the ISO/IEC International Standard8824-2).[8] ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules:Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard8825-2).[9] 3GPP TS 38.215: "NR; Physical layer measurements".[10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio ResourceControl (RRC); Protocol Specification".[11] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".[12] 3GPP TS 38.104: “NR; Base Station (BS) radio transmission and receptio n”.3 Definitions, symbols and abbreviations3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].Field: The individual contents of an information element are referred as fields.Floor: Mathematical function used to 'round down' i.e. to the nearest integer having a lower or equal value. Information element: A structural element containing a single or multiple fields is referred as information element. RLC bearer configuration: The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations.Special Cell: For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell.SRB1S: The SCG part of MCG split SRB1 for EN-DC.SRB2S: The SCG part of MCG split SRB2 for EN-DC.3.2 AbbreviationsFor the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].ACK AcknowledgementAM Acknowledged ModeARQ Automatic Repeat RequestAS Access StratumASN.1 Abstract Syntax Notation OneBLER Block Error RateCCCH Common Control ChannelCMAS Commercial Mobile Alert ServiceCP Control PlaneC-RNTI Cell RNTIDCCH Dedicated Control ChannelDL DownlinkDRB (user) Data Radio BearerDRX Discontinuous ReceptionEHPLMN Equivalent Home Public Land Mobile NetworkEPC Evolved Packet CoreEPS Evolved Packet SystemETWS Earthquake and Tsunami Warning SystemE-UTRA Evolved Universal Terrestrial Radio AccessE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFDD Frequency Division DuplexFFS For Further StudyGERAN GSM/EDGE Radio Access Network GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat RequestIE Information elementIMEI International Mobile Equipment Identity IMSI International Mobile Subscriber IdentitykB Kilobyte (1000 bytes)L1 Layer 1L2 Layer 2L3 Layer 3MAC Medium Access ControlMCG Master Cell GroupMIB Master Information BlockN/A Not ApplicablePCell Primary CellPDCP Packet Data Convergence Protocol PDU Protocol Data UnitPLMN Public Land Mobile NetworkPTAG Primary Timing Advance GroupQoS Quality of ServiceRAN Radio Access NetworkRAT Radio Access TechnologyRLC Radio Link ControlRNTI Radio Network Temporary Identifier ROHC RObust Header CompressionRPLMN Registered Public Land Mobile Network RRC Radio Resource ControlSCell Secondary CellSCG Secondary Cell GroupSI System InformationSIB System Information BlockSpCell Special CellSRB Signalling Radio BearerSTAG Secondary Timing Advance GroupS-TMSI SAE Temporary Mobile Station IdentifierTM Transparent ModeUE User EquipmentUICC Universal Integrated Circuit CardUL UplinkUM Unacknowledged ModeUP User PlaneUTC Coordinated Universal TimeUTRAN Universal Terrestrial Radio Access NetworkIn the ASN.1, lower case may be used for some (parts) of the above abbreviations e.g. c-RNTI.4 General4.1 IntroductionThis specification is organised as follows:- sub-clause 4.2 describes the RRC protocol model;- sub-clause 4.3 specifies the services provided to upper layers as well as the services expected from lower layers; - sub-clause 4.4 lists the RRC functions;- clause 5 specifies RRC procedures, including UE state transitions;- clause 6 specifies the RRC messages in ASN.1;- clause 7 specifies the variables (including protocol timers and constants) and counters to be used by the UE;- clause 8 specifies the encoding of the RRC messages;- clause 9 specifies the specified and default radio configurations;。

5G 3GPP R15 38.212 物理层复用与信道编码

5G 3GPP R15 38.212 物理层复用与信道编码

范围.......................................................................................................................................................... 6 参考.......................................................................................................................................................... 6 定义,符号和缩写.................................................................................................................................. 6
定义..................................................................................................................................................................... 6 符号..................................................................................................................................................................... 6 缩略语.

3GPP规范-R15-TS38系列NR38211-f00

3GPP规范-R15-TS38系列NR38211-f00

3GPP TS 38.211 V15.0.0 (2017-12)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;NR;Physical channels and modulation(Release 15)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.KeywordsNew Radio, Layer 13GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationContentsForeword (6)1Scope (7)2References (7)3Definitions, symbols and abbreviations (7)3.1Definitions (7)3.2Symbols (7)3.3Abbreviations (7)4Frame structure and physical resources (7)4.1General (7)4.2Numerologies (8)4.3Frame structure (8)4.3.1Frames and subframes (8)4.3.2Slots (8)4.4Physical resources (11)4.4.1Antenna ports (11)4.4.2Resource grid (11)4.4.3Resource elements (11)4.4.4Resource blocks (11)4.4.4.1General (11)4.4.4.2Reference resource blocks (11)4.4.4.3Common resource blocks (12)4.4.4.4Physical resource blocks (12)4.4.4.5Virtual resource blocks (12)4.4.5Carrier bandwidth part (12)4.5Carrier aggregation (12)5Generic functions (13)5.1Modulation mapper (13)5.1.1π/2-BPSK (13)5.1.2BPSK (13)5.1.3QPSK (13)5.1.416QAM (13)5.1.564QAM (13)5.1.6256QAM (13)5.2Sequence generation (14)5.2.1Pseudo-random sequence generation (14)5.2.2Low-PAPR sequence generation (14)5.2.2.1Base sequences of length 36 or larger (14)5.2.2.2Base sequences of length less than 36 (15)5.3OFDM baseband signal generation (18)5.4Modulation and upconversion (19)6Uplink (19)6.1Overview (19)6.1.1Overview of physical channels (19)6.1.2Overview of physical signals (20)6.2Physical resources (20)6.3Physical channels (20)6.3.1Physical uplink shared channel (20)6.3.1.1Scrambling (20)6.3.1.2Modulation (21)6.3.1.3Layer mapping (21)6.3.1.4Transform precoding (21)6.3.1.5Precoding (22)6.3.1.6Mapping to virtual resource blocks (25)6.3.1.6Mapping from virtual to physical resource blocks (26)6.3.2Physical uplink control channel (26)6.3.2.1General (26)6.3.2.2Sequence and cyclic shift hopping (26)6.3.2.2.1Group and sequence hopping (27)6.3.2.2.2Cyclic shift hopping (27)6.3.2.3PUCCH format 0 (28)6.3.2.3.1Sequence generation (28)6.3.2.3.2Mapping to physical resources (28)6.3.2.4PUCCH format 1 (28)6.3.2.4.1Sequence modulation (28)6.3.2.4.2Mapping to physical resources (29)6.3.2.5PUCCH format 2 (29)6.3.2.5.1Scrambling (29)6.3.2.5.2Modulation (30)6.3.2.5.3Mapping to physical resources (30)6.3.2.6PUCCH formats 3 and 4 (30)6.3.2.6.1Scrambling (30)6.3.2.6.2Modulation (30)6.3.2.6.3Block-wise spreading (31)6.3.2.6.4Transform precoding (31)6.3.2.6.5Mapping to physical resources (32)6.3.3Physical random-access channel (32)6.3.3.1Sequence generation (32)6.3.3.2Mapping to physical resources (38)6.4Physical signals (41)6.4.1Reference signals (41)6.4.1.1Demodulation reference signal for PUSCH (41)6.4.1.1.1Sequence generation (41)6.4.1.1.2Precoding (41)6.4.1.1.3Mapping to physical resources (41)6.4.1.2Phase-tracking reference signals for PUSCH (44)6.4.1.2.1Sequence generation (44)6.4.1.2.1.1Sequence generation if transform precoding is not enabled (44)6.4.1.2.1.2Sequence generation if transform precoding is enabled (44)6.4.1.2.2Mapping to physical resources (45)6.4.1.2.2.1Mapping to physical resources if transform precoding is not enabled (45)6.4.1.2.2.2Mapping to physical resources if transform precoding is enabled (46)6.4.1.3Demodulation reference signal for PUCCH (47)6.4.1.3.1Demodulation reference signal for PUCCH format 1 (47)6.4.1.3.1.1Sequence generation (47)6.4.1.3.1.2Mapping to physical resources (48)6.4.1.3.2Demodulation reference signal for PUCCH format 2 (48)6.4.1.3.2.1Sequence generation (48)6.4.1.3.2.2Mapping to physical resources (48)6.4.1.3.3Demodulation reference signal for PUCCH formats 3 and 4 (49)6.4.1.3.3.1Sequence generation (49)6.4.1.3.3.2Mapping to physical resources (49)6.4.1.4Sounding reference signal (49)6.4.1.4.1SRS resource (49)6.4.1.4.2Sequence generation (50)6.4.1.4.3Mapping to physical resources (51)6.4.1.4.4Sounding reference signal slot configuration (54)7Downlink (54)7.1Overview (54)7.1.1Overview of physical channels (54)7.1.2Overview of physical signals (55)7.2Physical resources (55)7.3Physical channels (55)7.3.1Physical downlink shared channel (55)7.3.1.1Scrambling (55)7.3.1.2Modulation (56)7.3.1.3Layer mapping (56)7.3.1.4Antenna port mapping (57)7.3.1.5Mapping to virtual resource blocks (58)7.3.1.6Mapping from virtual to physical resource blocks (58)7.3.2Physical downlink control channel (PDCCH) (59)7.3.2.1Control-channel element (CCE) (59)7.3.2.2Control-resource set (CORESET) (59)7.3.2.3Scrambling (60)7.3.2.4 PDCCH modulation (60)7.3.2.5Mapping to physical resources (60)7.3.3Physical broadcast channel (60)7.3.3.1Scrambling (60)7.3.3.2Modulation (61)7.3.3.3Mapping to physical resources (61)7.4Physical signals (61)7.4.1Reference signals (61)7.4.1.1Demodulation reference signals for PDSCH (61)7.4.1.1.1Sequence generation (61)7.4.1.1.2Mapping to physical resources (61)7.4.1.2Phase-tracking reference signals for PDSCH (64)7.4.1.2.1Sequence generation (64)7.4.1.2.2Mapping to physical resources (64)7.4.1.3Demodulation reference signals for PDCCH (65)7.4.1.3.1Sequence generation (65)7.4.1.3.2Mapping to physical resources (65)7.4.1.4Demodulation reference signals for PBCH (66)7.4.1.4.1Sequence generation (66)7.4.1.4.2Mapping to physical resources (67)7.4.1.5CSI reference signals (67)7.4.1.5.1General (67)7.4.1.5.2Sequence generation (67)7.4.1.5.3Mapping to physical resources (67)7.4.2Synchronization signals (70)7.4.2.1Physical-layer cell identities (70)7.4.2.2Primary synchronization signal (70)7.4.2.2.1Sequence generation (70)7.4.2.2.2Mapping to physical resources (70)7.4.2.3Secondary synchronization signal (70)7.4.2.3.1Sequence generation (70)7.4.2.3.2Mapping to physical resources (71)7.4.3SS/PBCH block (71)7.4.3.1Time-frequency structure of an SS/PBCH block (71)7.4.3.1.1Mapping of PSS within an SS/PBCH block (71)7.4.3.1.2Mapping of SSS within an SS/PBCH block (72)7.4.3.1.3Mapping of PBCH and DM-RS within an SS/PBCH block (72)7.4.3.2Time location of an SS/PBCH block (72)Annex A: Change history (73)ForewordThis Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document describes the physical channels and signals for 5G-NR.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP TS 38.201: "NR; Physical Layer – General Description" [3] 3GPP TS 38.202: "NR; Services provided by the physical layer" [4] 3GPP TS 38.212: "NR; Multiplexing and channel coding" [5] 3GPP TS 38.213: "NR; Physical layer procedures for control " [6] 3GPP TS 38.214: "NR; Physical layer procedures for data " [7] 3GPP TS 38.215: "NR; Physical layer measurements"3Definitions, symbols and abbreviations3.1 Definitions For the purposes of the present document, the following definitions apply:3.2 Symbols For the purposes of the present document, the following symbols apply:3.3AbbreviationsFor the purposes of the present document, the following abbreviations apply:4Frame structure and physical resources4.1GeneralThroughout this specification, unless otherwise noted, the size of various fields in the time domain is expressed as anumber of time units ()f max c 1N f T ⋅∆= where 3max 10480⋅=∆f Hz and 4096f =N . The constant 64c s ==T T κwhere )ref f,ref s 1N f T ⋅∆=, Hz 10153ref ⋅=∆f and 2048ref f,=N .4.2 NumerologiesMultiple OFDM numerologies are supported as given by Table 4.2-1 where μ and the cyclic prefix for a carrierbandwidth part are given by the higher-layer parameters DL-BWP-mu and DL-BWP-cp for the downlink and UL-BWP-mu and UL-BWP-cp for the uplink.Table 4.2-1: Supported transmission numerologies.4.3Frame structure4.3.1Frames and subframesDownlink and uplink transmissions are organized into frames with ()ms 10100c f max f =⋅∆=T N f T duration, consisting of ten subframes of ()ms 11000c f max sf =⋅∆=T N f T duration each. The number of consecutive OFDM symbols per subframe is μμ,subframe slotslot sy mb ,subframe sy mbN N N =. Each frame is divided into two equally-sized half-frames of five subframes each with half-frame 0 consisting of subframes 0 – 4 and half-frame 1 consisting of subframes 5 – 9. There is one set of frames in the uplink and one set of frames in the downlink on a carrier.Transmission of uplink frame number i from the UE shall start ()c offset TA,TA TA T N N T += before the start of the corresponding downlink frame at the UE where offset TA,N depends on the frequency band according to [38.133].Figure 4.3.1-1: Uplink-downlink timing relation4.3.2 SlotsFor subcarrier spacing configuration μ, slots are numbered {}1,...,0subframe,slots -∈μμN n in increasing order within a subframe and {}1,...,0fram e,slotf s,-∈μμN n in increasing order within a frame. There are slotsy mb N consecutive OFDM symbols in a slot where slotsy mb N depends on the cyclic prefix as given by Tables 4.3.2-1 and 4.3.2-2. The start of slot μs nin a subframe is aligned in time with the start of OFDM symbol slotsy mb s N n μ in the same subframe.OFDM symbols in a slot can be classified as 'downlink' (denoted 'D' in Table 4.3.2-3), 'flexible' (denoted 'X'), or 'uplink' (denoted 'U').In a downlink slot, the UE shall assume downlink transmissions to occur in 'downlink' or 'flexible' symbols only.In an uplink slot, the UE shall transmit in 'uplink' or 'flexible' symbols only.Table 4.3.2-1: Number of OFDM symbols per slot, slots per frame, and slots per subframe for normalcyclic prefix.Table 4.3.2-2: Number of OFDM symbols per slot, slots per frame, and slots per subframe forextended cyclic prefix.Table 4.3.2-3: Slot formats.3GPP 3GPP TS 38.211 V15.0.0 (2017-12) 11 Release 154.4Physical resources 4.4.1 Antenna portsAn antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed.Two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port isconveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.4.4.2 Resource gridFor each numerology and carrier, a resource grid of RB sc size,grid,N N x μ subcarriers and μ,subfram e sy m b N OFDM symbols is defined,starting at common resource block μ,start grid N indicated by higher-layer signalling.The subscript x is DL or UL fordownlink and uplink, respectively. When there is no risk for confusion, the subscript x may be dropped. There is one resource grid per antenna port p , per subcarrier spacing configuration μ, and per transmission direction (downlink or uplink).4.4.3 Resource elementsEach element in the resource grid for antenna port p and subcarrier spacing configuration μ is called a resource element and is uniquely identified by ()μ,,p l k where k is the index in the frequency domain and l refers to the symbol position in the time domain relative to some reference point. Resource element ()μ,,p l k corresponds to the complexvalue ),(,μp lk a . When there is no risk for confusion, or no particular antenna port or subcarrier spacing is specified, the indices p and μ may be dropped, resulting in )(,p l k a or l k a ,.4.4.4Resource blocks 4.4.4.1 GeneralA resource block is defined as 12RB sc=N consecutive subcarriers in the frequency domain. 4.4.4.2 Reference resource blocksReference resource blocks are numbered from 0 and upwards in frequency. Subcarrier 0 of reference resource block 0 is common for all subcarrier configurations μ, also denoted as 'reference point A', and serves as a common reference point for other resource block grids. Reference point A is obtained from the higher-layer parameter- PRB-index-DL-common for a PCell downlink- PRB-index-UL-common for a PCell uplink- PRB-index-DL-Dedicated for an SCell downlink- PRB-index-UL-Dedicated for an SCell uplink- PRB-index-SUL-common for a supplementary uplink。

2018MWCS展前解读:3GPPR15打造5G时代LTE,开启全业务连接时代

2018MWCS展前解读:3GPPR15打造5G时代LTE,开启全业务连接时代

2018MWCS展前解读:3GPPR15打造5G时代LTE,开启全业务连接时代LTE自诞生以来,以其相对3G巨大的技术进步以及快速完善的生态系统,成为有史以来发展最快的移动通信系统技术:根据GSMA统计,LTE目前已覆盖全球75%的人口,连接比例已超过2G/3G,并且预计到2025年还将持续增加到50%以上。

LTE从最初的满足移动用户数据业务的基本要求,不断通过引入高阶MIMO、ShortTTI等核心技术,持续提升频谱效率,在覆盖、容量、体验等多个层次提供移动用户最佳体验。

LTE-Advanced Pro R13和R14版本更进一步支持mMTC LPWA 低功耗广域网:NB-IoT支持5G所要求的每平方公里1百万连接以及高达20dB的覆盖增强,eMTC则可支持部分中高速率物联应用。

在今年3月3GPP RAN#79次全会形成结论,NB-IoT和eMTC将是5G时代mMTC LPWA场景的基础解决方案,R16不在NR引入类似的解决方案。

R14版本同时也支持了车联网V2V / V2X和增强型MBMS(多媒体广播多播服务)等多个垂直行业的应用。

本月14日在美国圣地亚哥举行的3GPP RAN#80次全会上,3GPP R15版本宣布冻结。

在3GPP看来,这个版本具有里程碑的重要意义,因为它不仅是第一个5G NR的协议版本,而且将LTE的空口用户面从4.8 ms降低至0.8 ms,还引入了对E-UTRAN/NR双链接 (EN-DC)的支持及LTE to 5G new core的支持,使得LTE演进成为5G时代网络的重要组成部分。

因此3GPP在R15的LTE协议封面上也正式打上了5G的Logo,并将它与R15的NR一起作为5G的使能技术。

下面我们为您逐一解读R15版本在LTE领域的重大增强:低时延Short TTI随着手游竞技的日益火爆,低时延已经成为继高速率之后用户体验的又一个重要指标,而且低时延还将激发以VR/AR、车联、工业自动化等为代表的新一代5G业务。

相关主题
  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

3GPP TS 38.331 V15.0.0 (2017-12)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access NetworkNR Radio Resource Control (RRC) protocol specification(Release 15)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UM TS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationContentsForeword (8)1Scope (9)2References (9)3Definitions, symbols and abbreviations (10)3.1Definitions (10)3.2Abbreviations (10)4General (11)4.1Introduction (11)4.2Architecture (12)4.2.1UE states and state transitions including inter RAT (12)4.2.2Signalling radio bearers (14)4.3Services (14)4.3.1Services provided to upper layers (14)4.3.2Services expected from lower layers (14)4.4Functions (14)5Procedures (15)5.1General (15)5.1.1Introduction (15)5.1.2General requirements (16)5.2System information (16)5.2.1Introduction (16)5.2.2System information acquisition (17)5.2.2.1General UE requirements (17)5.2.2.2SI validity and need to (re)-acquire SI (17)5.2.2.2.1SI validity (18)5.2.2.2.2SI change indication and PWS notification (18)5.2.2.3Acquisition of System Information (18)5.2.2.3.1Acquisition of MIB and SIB1 (18)5.2.2.3.2Acquisition of an SI message (19)5.2.2.3.3Request for on demand system information (20)5.2.2.4 Actions upon receipt of SI message (20)5.2.2.4.1Actions upon reception of the MasterInformationBlock (20)5.2.2.4.2Actions upon reception of the SystemInformationBlockType1 (21)5.2.2.4.3Actions upon reception of SystemInformationBlockTypeX (21)5.2.2.5Essential system information missing (21)5.3Connection control (21)5.3.1Introduction (22)5.3.2Paging (22)5.3.3RRC connection establishment (22)5.3.4Initial security activation (22)5.3.5RRC reconfiguration (22)5.3.5.1General (22)5.3.5.2Initiation (23)5.3.5.3Reception of an RRCReconfiguration by the UE (23)5.3.5.4Secondary cell group release (24)5.3.5.5Cell Group configuration (24)5.3.5.5.1General (24)5.3.5.5.2Reconfiguration with sync (25)5.3.5.5.3RLC bearer release (26)5.3.5.5.4RLC bearer addition/modification (26)5.3.5.5.5MAC entity configuration (27)5.3.5.5.6RLF Timers & Constants configuration (27)5.3.5.5.7SpCell Configuration (27)5.3.5.5.8SCell Release (27)5.3.5.6Radio Bearer configuration (28)5.3.5.6.1General (28)5.3.5.6.2SRB release (28)5.3.5.6.3SRB addition/ modification (28)5.3.5.6.4DRB release (29)5.3.5.6.5DRB addition/ modification (29)5.3.5.7Full configuration (30)5.3.5.9Reconfiguration failure (32)5.3.5.9.1Integrity check failure (32)5.3.5.9.2Inability to comply with RRCReconfiguration (32)5.3.5.9.3T304 expiry (Reconfiguration with sync Failure) (32)5.3.6Counter check (33)5.3.7RRC connection re-establishment (33)5.3.8RRC connection release (33)5.3.9RRC connection release requested by upper layers (33)5.3.10Radio resource configuration (33)5.3.11Radio link failure related actions (33)5.3.11.1Detection of physical layer problems in RRC_CONNECTED (33)5.3.11.2Recovery of physical layer problems (33)5.3.11.3Detection of radio link failure (34)5.3.12UE actions upon leaving RRC_CONNECTED (34)5.3.13UE actions upon PUCCH/SRS release request (35)5.4Inter-RAT mobility (35)5.5Measurements (35)5.5.1Introduction (35)5.5.2Measurement configuration (37)5.5.2.1General (37)5.5.2.2Measurement identity removal (38)5.5.2.3Measurement identity addition/ modification (38)5.5.2.4Measurement object removal (38)5.5.2.5Measurement object addition/ modification (39)5.5.2.6Reporting configuration removal (40)5.5.2.7Reporting configuration addition/ modification (40)5.5.2.8Quantity configuration (41)5.5.2.9Measurement gap configuration (41)5.5.2.10Reference signal measurement timing configuration (41)5.5.3Performing measurements (41)5.5.3.1General (41)5.5.3.2Layer 3 filtering (43)5.5.3.3Derivation of measurement results (43)5.5.4Measurement report triggering (44)5.5.4.1General (44)5.5.4.2Event A1 (Serving becomes better than threshold) (46)5.5.4.3Event A2 (Serving becomes worse than threshold) (46)5.5.4.4Event A3 (Neighbour becomes offset better than PCell/ PSCell) (47)5.5.4.5Event A4 (Neighbour becomes better than threshold) (47)5.5.4.6Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better thanthreshold2) (48)5.5.4.7Event A6 (Neighbour becomes offset better than SCell) (49)5.5.5Measurement reporting (50)5.5.5.1General (50)5.5.5.2Reporting of beam measurement information (52)5.6UE capabilities (52)5.6.1UE capability transfer (52)5.7Other (53)5.7.1DL information transfer (53)5.7.2UL information transfer (53)5.7.3SCG failure information (53)5.7.3.1General (53)5.7.3.2Initiation (54)5.7.3.4Setting the contents of FailureReportSCG-ToOtherRAT (55)6Protocol data units, formats and parameters (ASN.1) (56)6.1General (56)6.1.1Introduction (56)6.1.2Need codes for optional downlink fields (56)6.2RRC messages (57)6.2.1General message structure (57)–NR-RRC-Definitions (57)–BCCH-BCH-Message (58)–DL-DCCH-Message (58)–UL-DCCH-Message (59)6.2.2Message definitions (59)–MIB (59)–MeasurementReport (61)–RRCReconfiguration (61)–RRCReconfigurationComplete (63)–SIB1 (64)6.3RRC information elements (65)–SetupRelease Information Element (65)6.3.1System information blocks (65)6.3.2Radio resource control information elements (65)–DRB-Identity (65)–BandwidthPart-Config (66)–CellGroupConfig (67)–CellIndexList (69)–ControlResourceIndex (70)–CrossCarrierSchedulingConfig (70)–CSI-MeasConfig (71)–FailureReportSCG-ToOtherRAT (78)–FrequencyInfoUL (79)–LogicalChannelConfig (80)–MAC-CellGroupConfig (81)–MeasConfig (86)–MeasId (87)–MeasIdToAddModList (88)–MeasObjectEUTRA (88)–MeasObjectId (88)–MeasObjectNR (89)–MeasObjectToAddModList (94)–MeasResults (95)–PDCCH-Config (99)–PDCP-Config (102)–PDSCH-Config (106)–PhysCellId (109)–PUCCH-Config (109)–PUSCH-Config (112)–Q-OffsetRange (115)–QuantityConfig (115)–RACH-ConfigCommon (116)–RACH-ConfigDedicated (118)–RadioBearerConfig (119)–ReportConfigId (121)–ReportConfigNR (121)–ReportConfigToAddModList (125)–RLC-Config (126)–RLF-TimersAndConstants (128)–SCellIndex (129)–SchedulingRequest-Config (129)–SchedulingRequestResource-Config (130)–SDAP-Config (130)–ServCellIndex (132)–ServingCellConfigCommon (133)–ServingCellConfigDedicated (135)–SRB-Identity (137)–SPS-Config (137)–SRS-Config (138)–SubcarrierSpacing (140)6.3.3UE capability information elements (141)–BandCombinationList (141)–RAT-Type (141)–UE-CapabilityRAT-ContainerList (142)–UE-MRDC-Capability (142)–UE-NR-Capability (143)6.3.4Other information elements (146)6.4RRC multiplicity and type constraint values (146)–Multiplicity and type constraint definitions (146)7Variables and constants (148)7.1Timers (148)7.1.1Timers (Informative) (148)7.1.2Timer handling (148)7.2Counters (148)7.3Constants (148)7.4UE variables (149)–VarMeasConfig (149)–VarMeasReportList (149)8Protocol data unit abstract syntax (151)8.1General (151)8.2Structure of encoded RRC messages (151)8.3Basic production (151)8.4Extension (152)8.5Padding (152)9Specified and default radio configurations (152)9.1Specified configurations (152)9.2Default radio configurations (153)9.2.1SRB configurations (153)9.2.1.1SRB1/SRB1S (153)9.2.1.2SRB2/SRB2S (153)9.2.1.3SRB3 (154)9.2.2SRB configurations (154)9.2.2.1SRB1/SRB1S (154)9.2.2.2SRB2/SRB2S (155)9.2.2.3SRB3 (155)10Generic error handling (155)10.1General (155)10.2ASN.1 violation or encoding error (155)10.3Field set to a not comprehended value (156)10.4Mandatory field missing (156)10.5Not comprehended field (157)11Radio information related interactions between network nodes (158)11.1General (158)11.2Inter-node RRC messages (158)11.2.1General (158)11.2.2Message definitions (158)–HandoverCommand (158)–HandoverPreparationInformation (159)–SCG-Config (160)–SCG-ConfigInfo (162)11.3Inter-node RRC information element definitions (163)–CandidateCellInfoList (163)11.4Inter-node RRC multiplicity and type constraint values (164)12Processing delay requirements for RRC procedures (165)Annex A (informative):Guidelines, mainly on use of ASN.1 (165)A.1Introduction (165)A.2Procedural specification (166)A.2.1General principles (166)A.2.2More detailed aspects (166)A.3PDU specification (166)A.3.1General principles (166)A.3.1.1ASN.1 sections (166)A.3.1.2ASN.1 identifier naming conventions (167)A.3.1.3Text references using ASN.1 identifiers (169)A.3.2High-level message structure (170)A.3.3Message definition (171)A.3.4Information elements (173)A.3.5Fields with optional presence (174)A.3.6Fields with conditional presence (175)A.3.7Guidelines on use of lists with elements of SEQUENCE type (176)A.3.8Guidelines on use of parameterised SetupRelease type (176)A.4Extension of the PDU specifications (177)A.4.1General principles to ensure compatibility (177)A.4.2Critical extension of messages and fields (177)A.4.3Non-critical extension of messages (180)A.4.3.1General principles (180)A.4.3.2Further guidelines (180)A.4.3.3Typical example of evolution of IE with local extensions (181)A.4.3.4Typical examples of non critical extension at the end of a message (183)A.4.3.5Examples of non-critical extensions not placed at the default extension location (183)–ParentIE-WithEM (183)–ChildIE1-WithoutEM (184)–ChildIE2-WithoutEM (185)A.5Guidelines regarding inclusion of transaction identifiers in RRC messages (186)A.6Guidelines regarding use of need codes (186)Annex B (informative): Change history (188)ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN. The scope of the present document also includes:- the radio related information transported in a transparent container between source gNB and target gNB upon inter gNB handover;- the radio related information transported in a transparent container between a source or target gNB and another system upon inter RAT handover.- the radio related information transported in a transparent container between a source eNB and target gNB during E-UTRA-NR Dual Connectivity.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.- For a specific reference, subsequent revisions do not apply.- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the sameRelease as the present document.[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".[2] 3GPP TS 38.300: "NR; Overall description; Stage 2".[3] 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification".[4] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification".[5] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) protocol specification".[6] ITU-T Recommendation X.680 (07/2002) "Information Technology - Abstract Syntax NotationOne (ASN.1): Specification of basic notation" (Same as the ISO/IEC International Standard 8824-1).[7] ITU-T Recommendation X.681 (07/2002) "Information Technology - Abstract Syntax NotationOne (ASN.1): Information object specification" (Same as the ISO/IEC International Standard8824-2).[8] ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules:Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard8825-2).[9] 3GPP TS 38.215: "NR; Physical layer measurements".[10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio ResourceControl (RRC); Protocol Specification".[11] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".[12] 3GPP TS 38.104: “NR; Base Station (BS) radio transmission and receptio n”.3 Definitions, symbols and abbreviations3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].Field: The individual contents of an information element are referred as fields.Floor: Mathematical function used to 'round down' i.e. to the nearest integer having a lower or equal value. Information element: A structural element containing a single or multiple fields is referred as information element. RLC bearer configuration: The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations.Special Cell: For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell.SRB1S: The SCG part of MCG split SRB1 for EN-DC.SRB2S: The SCG part of MCG split SRB2 for EN-DC.3.2 AbbreviationsFor the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].ACK AcknowledgementAM Acknowledged ModeARQ Automatic Repeat RequestAS Access StratumASN.1 Abstract Syntax Notation OneBLER Block Error RateCCCH Common Control ChannelCMAS Commercial Mobile Alert ServiceCP Control PlaneC-RNTI Cell RNTIDCCH Dedicated Control ChannelDL DownlinkDRB (user) Data Radio BearerDRX Discontinuous ReceptionEHPLMN Equivalent Home Public Land Mobile NetworkEPC Evolved Packet CoreEPS Evolved Packet SystemETWS Earthquake and Tsunami Warning SystemE-UTRA Evolved Universal Terrestrial Radio AccessE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFDD Frequency Division DuplexFFS For Further StudyGERAN GSM/EDGE Radio Access NetworkGNSS Global Navigation Satellite SystemGSM Global System for Mobile CommunicationsHARQ Hybrid Automatic Repeat RequestIE Information elementIMEI International Mobile Equipment IdentityIMSI International Mobile Subscriber IdentitykB Kilobyte (1000 bytes)3GPP TS 38.331 V15.0.0 (2017-12) Release 1511L1 Layer 1L2 Layer 2L3 Layer 3MAC Medium Access ControlMCG Master Cell GroupMIB Master Information BlockN/A Not ApplicablePCell Primary CellPDCP Packet Data Convergence ProtocolPDU Protocol Data UnitPLMN Public Land Mobile NetworkPTAG Primary Timing Advance GroupQoS Quality of ServiceRAN Radio Access NetworkRAT Radio Access TechnologyRLC Radio Link ControlRNTI Radio Network Temporary IdentifierROHC RObust Header CompressionRPLMN Registered Public Land Mobile NetworkRRC Radio Resource ControlSCell Secondary CellSCG Secondary Cell GroupSI System InformationSIB System Information BlockSpCell Special CellSRB Signalling Radio BearerSTAG Secondary Timing Advance GroupS-TMSI SAE Temporary Mobile Station IdentifierTM Transparent ModeUE User EquipmentUICC Universal Integrated Circuit CardUL UplinkUM Unacknowledged ModeUP User PlaneUTC Coordinated Universal TimeUTRAN Universal Terrestrial Radio Access NetworkIn the ASN.1, lower case may be used for some (parts) of the above abbreviations e.g. c-RNTI.4 General4.1 IntroductionThis specification is organised as follows:- sub-clause 4.2 describes the RRC protocol model;- sub-clause 4.3 specifies the services provided to upper layers as well as the services expected from lower layers;- sub-clause 4.4 lists the RRC functions;- clause 5 specifies RRC procedures, including UE state transitions;- clause 6 specifies the RRC messages in ASN.1;- clause 7 specifies the variables (including protocol timers and constants) and counters to be used by the UE;- clause 8 specifies the encoding of the RRC messages;- clause 9 specifies the specified and default radio configurations;3GPP。

相关文档
最新文档