Escolar Documentos
Profissional Documentos
Cultura Documentos
Contents
1
Deployment strategies..........................................................................5
4
4.1
4.2
4.3
4.4
4.5
4.6
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
eNodeB................................................................................................15
General.................................................................................................15
Performance and Air Interface...............................................................17
Installation and Antenna Configuration..................................................19
Reliability...............................................................................................21
Power Supply........................................................................................22
Synchronization.....................................................................................23
Environmental Conditions.....................................................................23
6
6.1
6.2
eUTRAN Transport..............................................................................26
General.................................................................................................26
eNodeB (eNB).......................................................................................27
8
8.1
8.2
8.3
8.4
O&M......................................................................................................30
General.................................................................................................30
Fault Management................................................................................30
Configuration Management...................................................................30
Performance Management....................................................................31
9
9.1
9.2
9.3
9.4
CORE....................................................................................................33
General.................................................................................................33
Hardware Requirements: PDN-GW, S-GW, MME................................33
Software Requirements: PDN-GW, S-GW, MME..................................34
Capacity & Performance: PDN-GW, S-GW, MME................................34
General
1.1.1
1.1.2
1.1.3
1.1.4
Give a list of your LTE commercial customer wins globally. For each,
include scope of project, spectrum band (FDD/TDD/Hybrid), expected
launch timelines, infrastructure to be deployed (RAN, EPC, OSS etc)
and device partnerships (if any). Also state whether these are for Tier 1,
Tier 2 or Tier 3 operators.
1.1.5
Please list completed and ongoing LTE trials (including spectrum band,
timelines, scope, key achievements), and any additional planned trials
(spectrum band, timeline, scope, goals), provide details of status of IOT
efforts in support of these trials?
1.1.6
Please state the Maximum Throughputs (UL and DL) achievable with
different spectrum bandwidths; include all assumptions, inputs and
equipment configurations used for these values.
1.1.7
Indicate what throughputs values (UL and DL) have been achieved in
field trials and the trial configuration/equipment used.
1.1.8
Deployment strategies
There are uncertainties with regard to the future market trends and demands
which may drive our decisions around LTE/SAE. This section provides the
opportunity for you to describe your beliefs about the future market and help
shape our strategic thinking and deployment plans for LTE/SAE.
2.1.1
2.1.2
Please list the main reasons (if any) why America Mvil should seek to
deploy LTE/SAE, please provide justification and rationale for these
reasons.
2.1.3
2.1.4
What spectrum should America Mvil use for their future LTE
deployment taking into consideration the current regional spectrum
situation, economies of scale, mature ecosystem and ongoing LTE
deployments/announcements worldwide?
2.1.5
3.1.1
Please describe your current roadmap for LTE/SAE system (HW and
SW) and the related dependencies and timelines (proposed releases).
3.1.2
3.1.3
3.1.4
Please provide IOT information and/or trial results on LTE/SAE InterRAT testing with GSM and UMTS.
3.1.5
Please indicate whether your company has any device IoT and IoDT
plans and if yes provide detailed information including vendors.
3.1.6
Please confirm that all your products are future-proof, in the sense that
future-proof means that the HW platform is both flexible enough and
equipped with sufficient processing resources to support future
releases of standardized features without the need to swap HW.
3.1.7
3.1.8
3.1.9
3.1.10
4.1
4.1.1
4.1.2
4.1.3
4.1.4
Please confirm that your system is scalable and flexible and specify
any limitations.
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
4.1.11
Please explain your Baseband Unit capacity upgrade policy (SW license
key?).
4.2
Mobility
4.2.1
The system shall support RAT selection priority for LTE, UMTS, GSM
and CDMA-eHRPD broadcast in system information. Please provide
roadmap details.
4.2.2
4.2.3
The system shall support Intra and Inter eNodeB handover with
neighbor cell-specific handover parameters
4.2.4
4.2.5
The system shall support IRAT handover for UE with multiple EPS
bearers by using handover parameters per QCI. The handover shall be
done when the first EPS bearer triggers.
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
Based on load
Based on service
4.2.13
4.2.14
4.2.15
The system shall support Inter eNB handover: over S1 interface (no X2
interface between serving and target eNB)
4.2.16
4.2.17
4.2.18
4.2.19
intra frequency,
4.2.20
intra frequency
inter MME
inter SGW
4.2.21
4.2.22
The system shall support Inter frequency reselection priority based on:
4.2.23
4.2.24
4.2.25
4.2.26
4.2.27
4.2.28
4.2.29
Please state your support for the below LTE to GSM handover:
4.2.30
PS (non-voice)
4.3
QoS
4.3.1
Please describe the end to end QoS solution, which types of bearers
are supported and how the QoS is controlled and managed in your
LTE/SAE solution.
4.3.2
4.3.3
The eUTRAN shall support that the QoS requirements signaled to the
eNodeB over the S1 interface are used to determine how the bearers
should be handled in a resource limited situation.
4.3.4
4.3.5
4.3.6
The system shall provide the ability for a user to have several
simultaneous data bearers with different QoS. Please state number of
simultaneous data bearers.
4.3.7
4.3.8
4.3.9
4.4
Scheduler
4.4.1
4.4.2
Max CQI,
4.4.3
4.5
Voice Support
4.5.1
SR VCC
CS Fall back
VoLGA
4.5.2
SRVCC
4.5.3
4.5.4
4.6
4.6.1
4.6.2
4.6.3
From what release will you support Interference Coordination via the X1
interface?
4.6.4
4.6.5
eNodeB
5.1
General
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7
Please state the functionality and the SW release, for a full working
MSR radio module.
The supplier shall state the MCPA IBW (Instantaneous Bandwidth, i.e.
how much BW does the RU support)
The supplier shall state the MCPA nominal output power if it is used
for one carrier configuration.
The supplier shall state the MCPA aging marginal taken into the
consideration in the design
The supplier shall state the MCPA Filter loss compensation marginal
taken into the consideration in the design
The supplier shall state the MCPA Temperature drift marginal taken
into the consideration in the design
The supplier shall state the MCPA power saturation taken into the
consideration in the design
The supplier shall state if the MCPA has a power back off if 64 QAM
modulation is used
5.1.8
5.1.9
Please state your HW life cycle plan and state valid proof points on how
your legacy equipment has been capable or can be modernized to meet
future enhancements?
5.2
5.2.1
State the total TX power constantly available at full load at the top of the
cabinet (or at the RF connector in case of RRH).
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
Please state the Peak data rates for uplink and downlink for each carrier
bandwidth and different MIMO configuration supported.
5.2.10
5.2.11
QPSK
16QAM
64QAM
QPSK
16QAM
64QAM
5.2.12
5.2.13
5.2.14
What MIMO (UL and DL) and Beam forming (UL and DL) schemes will be
supported, including space-time/frequency transmit diversity and multi
stream schemes
5.2.15
5.2.16
5.2.17
Maximum simultaneous idle users, active users and active + idle users
supported per eNodeB configuration
5.2.18
Max cell range supported and any features that limit the range and
plans to extend the range
5.2.19
5.2.20
The vendor shall describe how zero downtime can be achieved when
replacing or adding radio units in their macro eNodeBs.
5.2.21
The vendor shall describe how zero downtime can be achieved when
replacing or adding remote radio heads in their distributed eNodeBs.
5.2.22
5.2.23
5.2.24
The Radio Units and Remote Radio Heads (as applicable) shall support
VSWR measurement / monitoring.
5.2.25
The Radio Units and Remote Radio Heads (as applicable) shall support
faulty antenna determination together with the O&M system.
5.2.26
5.2.27
5.2.28
5.2.29
5.2.30
5.2.31
5.3
5.3.1
5.3.2
5.3.3
5.3.4
Height
Width
Depth
Weight
o Total weight, fully configured
o Per cabinet
o For each range of battery backup capacity offered
o For main-remote state the weight of its individual main components
Radio cabinet mounting and cable entry options and compatibility with
legacy equipment
Different mounting alternatives available for the eNodeB types. All macro
eNodeB shall allow back-to-back and side-to-side installation.
5.4
Reliability
5.4.1
List the MTBF for each element at the lowest field-replaceable module
level.
5.4.2
5.4.3
Identify redundant elements and type such as 1+1. N+1, and describe
resource pooling for each element. If service interruption occurs
during failover, provide the interruption time.
5.5
Power Supply
5.5.1
Please describe the power supply inputs for each eNodeB type.
5.5.2
5.5.3
Please state the power consumption for different eNodeB types under
different RF load conditions including both typical and maximum
values. Please indicate conditions assumed for typical consumption,
including transmit power levels, carrier bandwidths, operating
spectrum, ambient temperature, or other factors with significant impact
on power consumption.
5.5.4
The Outdoor eNode B shall include a battery backup within the cabinet.
5.5.5
Please describe the power backup solution for outdoor eNodeB types.
5.5.6
5.5.7
The O&M system shall in a Multi Standard Radio (MSR) ensure that the
Power System is used in the most cost-efficient and environmentally
friendly way.
5.6
Synchronization
5.6.1
5.6.2
5.6.3
5.6.4
5.6.5
5.6.6
5.6.7
5.7
Environmental Conditions
5.7.1
Relative humidity
5.7.2
5.7.2.1
a)
Storage Requirements:
ETS class 1.2 Weather Protected, Not Temperature Controlled Storage
Locations in ETS 300 019-1-1
b)
Product safety:
LVD 73/23/EEC and 93/68/EEC
EN 60950 / IEC 950
EN 60215 / IEC 215
EN 60952 / IEC 529
Code of Federal Regulation 21 CFR 1040.10 and 1040.11
ANSI/UL 60 950-1 / CSA C22.2 No.60950-1-03
c)
d)
The Indoor Node B shall comply with ETS class 2.3 Public Transportation
in ETS 300 019-1-2.
e)
The Indoor eNode B shall comply with the requirements for normal
operation in the climate conditions of class 3.1 of ETS 300 019-1-3
according to IEC/EN 721-3-3.
5.7.2.1.1
Outdoor version
a)
Storage Requirements
ETS class 1.2 Weather Protected, Not Temperature Controlled Storage
Locations in ETS 300 019-1-1
b)
The Outdoor eNode B shall comply with ETS class 2.3 Public
Transportation in ETS 300 019-1-2.
c)
The Outdoor eNode B shall be compliant with ETS class 4.1 (extended to
45 C). Non Weather Protected Locations as follows: ETS 300 019-1-4:
-33C to +45 C
d)
e)
f)
g)
Acoustic Noise: Measured according to ISO 7779 and ETS 300 753 with
max 54 dB (A)
eUTRAN Transport
6.1
General
6.1.1
6.1.2
6.1.3
Describe the transport solution for an eNodeB co-sited with GSM and
WCDMA nodes.
6.1.4
What physical interfaces for X1/S2 and O&M does the eNodeB provide?
6.1.5
6.1.6
The system shall support IPv4 and be hardware prepared for IPv6 for all
traffic interfaces in the eNodeB.
6.1.7
From which release will the system support IPv6 on IP (X1, S2)
interface?
6.1.8
The system shall support Gigabit Ethernet optical and/or electrical port
in the eNodeB.
6.1.9
6.1.10
6.2
eNodeB (eNB)
6.2.1
The system shall support traffic separation and Quality of Service (QoS)
on the IP respective Ethernet layer for all eNB traffic in the eNodeB; this
shall be described in detail.
6.2.2
The system shall support IPsec and IKEv2 for the traffic according to
the 3GPP specification in the eNodeB.
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
6.2.10
6.2.11
How does the traffic classification and marking and QoS enforcement
work on eNB S1 and X2 interfaces? Can this mapping be configurable
via OA&M?
6.2.12
6.2.13
6.2.14
6.2.15
6.2.16
6.2.17
6.2.18
6.2.19
7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.1.7
7.1.8
7.1.9
7.1.10
7.1.11
7.1.12
O&M
8.1
General
8.1.1
The same O&M system shall concurrently support the various radio
technologies when running Multi Standard Radio, MSR.
8.1.2
The same O&M system shall concurrently support a mixed single- and
multi-band radio environment with SCPA, MCPA, and MSR for backward
compatibility.
8.2
Fault Management
8.2.1
8.2.2
Please provide full details of the support for self-healing of the LTE/SAE
network (including interfaces). Provide full details of the distribution of
functions between the O&M solution and the LTE/SAE nodes to support
this, and the functional interaction between the LTE/SAE nodes and
O&M solution.
8.2.3
8.2.4
8.3
Configuration Management
8.3.1
8.3.2
8.3.3
8.3.4
8.3.5
8.3.6
8.3.7
8.4
Performance Management
8.4.1
8.4.2
8.4.3
Please provide details of the support for Cell level Tracing (real time
and non-real time).
8.4.4
Please provide details of the support for subscriber level tracing (real
time and non-real time).
8.4.5
8.4.6
PM acquisition functions
The vendor shall describe the features available for collection of PM
Counters and Events, such as:
PM Counters statistics
Cell trace
UE trace
CORE
This section covers the Evolved Packet CORE network as described by 3GPP
specification and covers the following components: PDN Gateway (PDN-GW),
Serving Gateway (S-GW), and Mobility Management Entity (MME)
9.1
General
9.1.1
The EPC network entities (MME, Serving GW, and PDN-GW) shall
comply with specifications defined in 3GPP Release 8.
9.1.2
9.2
9.2.1
9.2.2
9.2.3
9.2.4
9.2.5
Are all hardware elements redundant, such that the failure of a single
element does not impact the operational performance of the
equipment?
9.2.6
Height
Width
Depth
Weight
o Total weight, fully configured
o Per cabinet
o For each range of battery backup capacity offered
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.4
9.4.1
9.4.2
9.4.3