1.

The vendors solution should support VoLTE Emergency Call allows subscribers to use
UEs on an LTE network to dial emergency numbers to connect to public safety answering
points (PSAPs) in the event of an emergency, such as a terrorist attack, medical
emergency, fire, or natural disaster.
2. The vendors solution should support prioritized access to network resources for specific
subscribers when network congestion or an emergency occurs.
3. The vendors solution should support configurable parameters that whether to provide the
IMS-based VoLTE service for UEs of certain models based on their international mobile
equipment identities (IMEIs).
4. The vendors solution should provide accessibility of basic VoLTE services and VoLTE
emergency call services based on whether the coverage area in the E-UTRAN supports
VoLTE services.
5. The provided MME should support the information after it receives an HSS-forwarded
request initiated by the IMS for the location information of a UE performing a VoLTE
service. Based on the UE location information, the IMS determines location-based
policies such as differentiated charging policies, roaming policies, and push policies. The
UE location information includes the E-UTRAN cell global identifier (ECGI) and tracking
area identity (TAI).
6. The provided MME pool should support one MME from the pool to take over services
from a faulty MME (caused by a system upgrade, power-off, fire, natural disaster or other
reasons) immediately. All the ongoing mobile-originated (MO) and mobile-terminated (MT)
VoLTE services on the faulty MME should not be impacted.
7. The provided MME should support to detect S-GW/P-GW faults and resets to restore
VoLTE services at the earliest possible time and implements gateway redundancy.
8. The provided MME should support optimized paging solution for fixed terminals. A fixed
terminal is a terminal that accesses the network at a fixed location, such as an fixed
network access point in the airport. Support configurable READY timer to extend the
READY state for fixed terminals.
9. The provided MME should implement basic mobility management (MM) and session
management (SM) procedures without a mobile station international ISDN number
(MSISDN). The procedures include attach, tracking area update (TAU), routing area
update (RAU), and Packet Data Protocol (PDP) context activation procedures.
10. The provided S-GW/P-GW should allow mobile stations (MSs) or UEs to access networks
without mobile station international ISDN numbers (MSISDNs).
11. The provided MME should support to determine a paging policy based on the UE type
(IMEI/IMSI/MSISDN) and service type (APN/ARP/QCI/etc.), perform paging rule filtering
based on UE mobility, and select appropriate scopes to page UEs to effectively reduces
the paging load on eNodeBs and saves network resources.
12. The vendors solution should support wireless optimization with service flow priority. PS
core distinguishes the kind of service flow and transfer the FPI (Flow Priority Index) to
eNodeB and eNodeB manage the wireless resource by the FPI.

13. The vendors solution should support implements bandwidth control on particular
subscribers or services, preventing or alleviating cell congestion base on the cell load
status report by eNodeB.
14. The provided P-GW should support detect the proxy-call session control function (PCSCF) status using the Internet Control Message Protocol (ICMP). When detecting that a
link between the P-GW and P-CSCF is not functioning properly, the P-GW pushes the IP
addresses of a pair of functioning P-CSCFs to a mobile station or user equipment
(MS/UE) to ensure the VoLTE.
15. The provided S-GW/P-GW should support network element level redundancy. Even the
S-GW/P-GW failed, the backup S-GW/P-GW will immediately take over the service and
the ongoing voice services will not be interrupted.
16. The eNodeB shall support the Carrier Aggregation of Band28 and Band40 in both UL and
DL links.

17. The vendor shall have rich experience of serving mission critical customer. The vendor
shall provide the list of cases which their solution are used for public safety sectors.

18. The vendor shall provide the mission critical features supported now for 3GPP R12 &
R13, and the roadmap for future Release.