Volte WPS
Volte WPS
Volte WPS
RAN
PA2
1 Introduction.................................................................................................4
1.1 Assumptions.............................................................................................................5
1.2 Project Scope............................................................................................................5
1.2.1 Scope for Claro.........................................................................................................6
1.3 Out of Scope.............................................................................................................7
2 Solution........................................................................................................7
2.1 Network Overview...................................................................................................7
2.2 Market Configuration............................................................................................10
2.3 Solution Description...............................................................................................11
1 Introduction
The term voice-over-LTE (VoLTE) is used to describe the GSMA specification for
voice and Short Message Service (SMS) in LTE, which has its origins in the 3GPP
IMS-based multimedia telephony (MMTel) solution. With the Ericsson MMTel,
users can – for example – start a voice session, add or drop media such as video,
and also invite additional callers.
Operators deploying VoLTE can evolve their voice services into rich multimedia
offerings, including, HD voice, video calling and other multimedia services, such as
Rich Communication Suite (RCS), which allows customers to be available
anywhere on any device, combining mobility with service continuity.
Although MMTel forms the basis of the VoLTE solution, EPC (with IP flow and
bearer management) and LTE (with conversational radio bearers) are integral
parts of it. Together, they secure interoperability on all interfaces between devices
and networks.
Access to WPS service will be defined per User based on the UE “access class”
defined on the HSS LTE subscription. For WPS Claro PR will use Access Class 14:
Wireless Priority Services
Priority treatment must be provided end-to-end in the LTE, EPC, HSS and IMS
networks, in both the originating and terminating PLMN
1.1 Assumptions
1. CORE Evolved Packet Core and IMS are fully operational and configured to
support Wireless Priority Service (WPS) by Ericsson
2. Claro PR to provide UEs capable and with the correct setting/configuration for
WPS services, this means correct VoLTE Configuration, Access Class 14
capability and according UE release to support Features mentioned in this
document
3. SIM or USIM cards must be provisioned for High Priority Services, this means
must be provisioned with Access Class 14
Access to WPS service will be defined per User based on the UE “access class”
defined on the HSS LTE subscription. For WPS Claro PR will use Access Class
14: Emergency Services
The following sections describes the Solution proposal and considerations for the
successful implementation of WPS considering the functionality implementation
and test per phases:
Claro PR is currently deploying an IMS Core and LTE RAN features to support
VOLTE Calls services for its LTE Network.
All activities proposed on the following scope of work for WPS activation, rely
on the successful implementation and lunch of the VOLTE standard services.
Phase 1 &2 includes SW and Services for LTE RAN, MME, HSS and IMS to
support the WPS Initial Operating Capability (IOC), and Testing for Limited
operating Capabilities (LOC). The following activities are included as part of
the scope, with the following milestones:
WPS Solution design for VOLTE considering the implementation for Initial
Operating Capabilities (IOC) – High level design (HLD) and Low-level
design (LLD)
Services for Feature activation and SW configuration of WPS features on
Ericsson Core Elements and LTE Toy Cell (FNI on toy cell)
WPS VOLTE Testing of Initial Operating Capabilities (IOC) - Standard
ATP (FNI on toy cell)
LTE RAN Parameter setting review for WPS
*NRO Services for LTE WPS configuration services on LTE network Level
(910 sites)
Final acceptance for WPS over VOLTE
The following sections describes the Scope of Work (SOW) for RAN and Core
to be implemented: Limited capability (LC) and initial operating capability
(IOC)
Once this SOW has been mutually agreed upon and incorporated into a Purchase
Order issued by CLARO PR pursuant to the Agreement, any change in the
deliverables, estimated timelines, assumptions, responsibilities and other relevant
terms specific to the implementation will result in a “Change”. All change requests
will be submitted by the party requesting the Change to the other party with a
written COR/JCO (Change Order Request / Job Change Order), that specifies any
adjustments to the charges and other changes/charges resulting from the
COR/JCO. No Change will be effective or acted upon in any way until an
authorized representative of each party has agreed to the terms of the COR/JCO
in writing as an amendment to the SOW, and until Ericsson receives a Purchase
Order from CLARO PR for any additional charges resulting from the COR/JCO.
2 Solution
Network Management
Evolved Packet Core
System
LTE RAN
OSS-RC
Transport
UE
UE
RBS
RBS
RBS
UE
The LTE RAN consists of all the RBSs in one operators’ network, one or more
OSS-RCs (RAN part), and the necessary infrastructure. The necessary
infrastructure is the infrastructure needed to provide interconnection between
the RBSs and the relevant EPC nodes, between the different RBSs, between
the RAN part of the OSS-RC and the RBSs, and site infrastructure.
The RBS controls the radio connection with active UEs as well as manages
the cell resources. Ciphering of the user plane and RAN control plane
signaling of the radio interface (RRC) is performed by the LTE RAN.
The transport network to the EPC and Network Management System is based
on IP, allowing for a multitude of physical layers for the transport. IPv6 is
supported as an alternative to IPv4 on the user and control plane interface
2.1.2 RBS
The Radio Base Station (RBS) is responsible for the radio connection to UEs
in RRC Connected mode. This includes QoS realization, based on the radio
bearers and their respective QoS classes as requested by the EPC. When a
UE, previously unknown to the RBS, accesses the RBS, the RBS is
responsible for routing of the initial access from the UE to the proper EPC
node. It also includes handling the mobility of the UE. The RBS is also in
control of most of the information controlling the UE behavior in RRC Idle
mode, i.e. the part of the information that is being broadcast. The RBS is
furthermore responsible for cell resource management. The RBS also handles
self-organization network features such as automated handling of neighbor
cell relations.
2.1.3 OSS-RC
The OSS-RC is the central point for Alarm and PM file collection from the
RBSs in LTE RAN. The Alarm and PM information is made available from the
OSS to NMS systems via the 3GPP Alarm, PM, and trace IRP interfaces.
OSS-RC supports 3GPP Basic and Bulk CM IRPs which will enable extraction
of data for, and rollout of planned configurations from, network planning tools.
The OSS-RC provides a central point for the software upgrade and inventory
The Ericsson solution proposal for the VoLTE RAN for Claro is based
upon the implementation of the following nodes:
Currently Claro Puerto Rico LTE Network has 4 carriers, in different frequencies
now using next configuration of bands and bandwidths for almost all island
Layer Management
B66 with highest Priority for reselection, parameters for layer management
baseline in file attached to this document
The list of LTE features to be consider for parametrization as part of WPS are
stated below. This features will enabled Wireless Priority Service, adding
mechanisms at Radio Access Network Level that gives priority treatment to a an
specific Radio Resource Control Connection or a EPS Radio Bearer Based on
Access Class and Allocation and Retention Priority definitions in a congested
network scenario, avoiding the High Priority Access users go to starvation of Radio
Resources and eventually not possible to stablish a VoLTE High Priority.
OPERABL
FAJ 121 1748 Dynamic GBR Admission Control
E
OPERABL
FAJ 121 1787 Differentiated Admission Control
E
OPERABL
FAJ 121 1857 Basic Admission Control
E
In this sense RAN Wireless Priority Features will enable special users have a
much better chance to be granted in a end to end VoLTE service, adding
mechanisms to the Core Network Features.
In order to show basic functionality for VoLTE RAN services, high level flow charts
will be described
This section describes the overview high level actions usually performed when a
VoLTE terminal is powered on for a WPS subscriber. The terminal will attach to
the radio network and then will register into IMS.
Pre-requisite:
The subscriber data including WPS\MPS for WPS specific data have been
provisioned on the EPC and IMS domains.
1. The terminal attaches to the E UTRAN and EPC network. The USIM in the UE
may be provisioned with an Access Class priority that can be used during the
attach request to receive priority in LTE prior to the establishment of the IMS
APN.
2. The UE will check if the IMS APN was setup as part of the initial attach.
3. If the default APN is not used for SIP signaling, the UE establishes a new EPS
bearer for the APN for SIP signaling. The MME applies the default QoS profile
including default priority based on the subscription information from HSS.
4. The UE registers in the IMS network using the P-CSCF address provided from
EPC when setting up the IMS APN.
5. As part of the IMS registration, the S-CSCF receives the priority level from
HSS and provides this default priority level to the P-CSCF.
This section describes the high level view for establishment of a call by a VoLTE
UE on PS access in the originating domain that is subscribed to Multimedia
Priority Service.
Pre-requisite:
The VoLTE terminal has been attached to the LTE/EPC and registered in
IMS for WPS\MPS usage.
1. The user initiates a call. If the UE is not already in active mode, the UE
re establishes the bearers by performing a service request
3. During the SIP negotiation, when receiving the SDP answer, IMS (P-
CSCF) performs a resource allocation request toward EPC for the
media being negotiated. IMS includes the WPS\MPS priority indication
and priority level to PCRF.
5. The called subscriber answers the call and replies with a SIP 200 OK.
The session setup is completed.
For the terminating leg of a priority call, an early Rx indication is sent in order to
signal the priority of the call to PCRF as early as possible in the call establishment,
this, in order to upgrade the signaling bearer for a non-prioritized terminating user
when a priority indicated call is received. The usage of the early Rx indication is
configurable in P-CSCF.
Thus, the terminating P-CSCF makes early Rx invocation indicating the requested
priority level. This means that the P-CSCF shall be able to provide preliminary
service information not fully negotiated yet when receiving with SDP offer.
Pre-requisite:
The VoLTE terminal has been attached to the LTE/EPC and registered in
IMS.
3. The PCRF maps the priority received in the early Rx request from IMS to
the correct ARP value, upgrades the ARP of the default bearer (if required),
and sets the ARP of the dedicated media bearers in the PCC rules.
5. During the SIP negotiation, when receiving the SDP answer, IMS performs
another resource allocation request toward EPC for the media being
negotiated. Note that it is only at this stage, IMS has the full media
information for the call. The WPS\MPS priority indication and priority level
are included from IMS also at this stage.
7. The called subscriber answers the call and replies with a SIP 200 OK. The
session setup is completed.
9. Any of the session participants can release the session by sending a SIP
BYE message. The resources from media are released, and IMS indicates
EPC to release the EPC releases, i.e. the dedicated media bearer is
terminated.
Differentiated Admission Control provides higher accessibility for UEs and E-RABs
with high Allocation and Retention Priority (ARP) and optionally SPID priority by
prioritizing UEs and bearers against each other in admission control. Two access
differentiation algorithms are supported: differentiated blocking and pre-emption.
The two algorithms can be activated together to achieve higher differentiation
effect.
For differentiated blocking, higher accessibility for UEs and E-RABs with high ARP
priority is achieved at the cost of lower accessibility for UEs and E-RABs with low
ARP priority. The same is also applied for the UEs with high SPID priority if SPID
based filtering is activated.
For differentiation by pre-emption the cost is lower retainability for UEs and E-
RABs with low ARP priority, and optionally low SPID priority.
When both differentiation algorithms are activated together, the cost in lower
retainability for UEs and E-RABs with low ARP priority can be traded for the cost in
lower accessibility.
*Note: Details for this feature as operation, impact, parameters, and other
specifications can be found on the Vendor Document.
The Priority Paging feature adds support for prioritization of S1AP paging
messages received from the core network.
The feature extends the paging functionality at the RBS by adding support for the
Paging Priority IE in the S1AP Paging message by performing prioritization of the
receivedS1AP paging messages.
This feature ensures that S1AP paging messages with higher priority have a
higher success rate than S1AP messages with lower priority. The highest priority
corresponds to the lowest priority number in the Paging Priority IE. For more
information about the overload protection mechanism.
For Wireless Priority Services this means that users with Priority Paging
Information Elements defined by the Core Network, will receive with priority the
paging messages from the Core and re- resend by the eNodeB to the user in order
to locate them in the network in a High Load scenario where several paging
messages has to be sent, avoiding that Radio Access Network be a bottle neck in
the flow of receiving a paging for High Priority Access.
*Note: Details for this feature as operation, impact, parameters, and other
specifications can be found on the Vendor Document.
The feature increases the chance that prioritized users who belong to access
classes 10-15, for example, public safety and emergency calls, can enter the
network at all times, even during overload conditions. Certain users and
Emergency Calls are prioritized based on Access Class concept defined in 3GPP.
High-priority users are the following:
Users that belong to access class 10 and perform Emergency Access calls.
Users that belong to access class 11- 15 and perform High-Priority Access
calls.
The access class to which the UE belongs is stored on the Universal Subscriber
Identity Module (USIM). It is tied to the mobile subscription. All UE (with a USIM)
are members of one of ten randomly-allocated populations, defined as access
classes 0–9.
In this sense WPS will be enabled by this feature giving especial access barring,
using Access Class 14, with prioritizing this calls as priority calls within the Radio
Access Network and the specific cell where the UE is attached, this means that
UEs with Access Class 10 will have access to the Network in a congestion
scenario at the same time with Access Class 14, also users with Access Class 14
will be treated with priority, giving them better chances to establish a RRC
connection in a congested scenario.
*Note: Details for this feature as operation, impact, parameters, and other
specifications can be found on the Vendor Document.
The feature adds enhanced functionality to the Admission Control feature. The
Admission Control feature reserves system resources for privileged access. The
feature also controls the admission of UEs and E-RABs based on whether the
resource request is privileged. Enhanced admission control of privileged access is
required if there is an excess number of privileged access users.
–Emergency call
From an admission control perspective, HPA privileged access has higher priority
than emergency call privileged access. To give priority to HPA privileged access,
the Privileged Access Admission Balancing feature reserves a part of the
resources reserved by Admission Control feature to admit only HPA privileged
access.
The feature manages system resources efficiently when the system is congested
by critical services like public safety.
*Note: Details for this feature as operation, impact, parameters, and other
specifications can be found on the Vendor Document.
The Dynamic GBR Admission Control feature assists in ensuring that the QoS is
maintained for the already established Guaranteed Bit Rate Bearer (GBR)
bearers, after a successful initial setup. The Dynamic GBR Admission Control
feature achieves this through limiting the number of Guaranteed Bit Rate Bearer
(GBR) bearers based on resource usage. The Dynamic GBR Admission Control
feature allows the setup of new Guaranteed Bit Rate Bearer (GBR) bearers, if the
GBR bearers do not exceed a configured threshold during the use of the MSR.
The main purpose of the Dynamic GBR Admission Control feature is to ensure
that the QoS is maintained for GBR bearers in the system. By enabling the
Dynamic GBR Admission Control feature, a headroom is created that allows
fluctuating radio conditions and mobility. The headroom can also be used to
control the ratio between GBR and non-GBR traffic. Furthermore, the use of a
dynamic method of measuring the resource usage by GBR bearers allows for a
more efficient use of resources. This measurement method helps avoiding
unnecessary rejections.
For Wireless Priority Services in VolTE, this feature will enabled the possibility to
avoid congestion in the number of VoLTE Calls, as all VoLTE calls are a
Guaranteed Bit Rate Bearer (GBR), this will prevent that the cell or eNodeB go to
starvation during a congestion scenario, and will ensure control admission to High
Priority Access users or WPS users.
*Note: Details for this feature as operation, impact, parameters, and other
specifications can be found on the Vendor Document.
The KPIs for VoIP and conversational video can be grouped in the same way as
for mobile broadband services:
Accessibility
Retainability
Integrity
Mobility
Availability
Below Table shows the main VoLTE KPI category and performance indicators and
how to measure by counters.
Key
KPI
Performance Formula
Category
Indicators
VoLTE (pmRrcConnEstabSuccMod+pmRrcConnEstabSu
KPIs ccMta)/
(pmRrcConnEstabAttMod+pmRrcConnEstabAttMt
Initial ERAB a-pmRrcConnEstabAttReattMod-
Accessibility Establishment pmRrcConnEstabAttReattMta)
SR per QCI ×(pmS1SigConnEstabSuccMod+pmS1SigConnE
stabSuccMta)/(pmS1SigConnEstabAttMod+pmS1
SigConnEstabAttMta)×pmErabEstabSuccInitQci/p
mErabEstabAttInitQci×100%
Added E-RAB
Establishment pmErabEstabSuccAddedQci/pmErabEstabAttAdd
Accessibility
Success Rate edQci×100%
per QCI
rmalMmeActQci)/
per QCI (pmErabRelAbnormalEnbActQci+pmErabRelNor
malEnbQci+pmErabRelMmeQci)×100%
E-RAB
Retainability -
(pmErabRelAbnormalEnbActQci+pmErabRelAbno
Retainability Session Time
rmalMmeActQci)/pmSessionTimeDrbQci×100%
normalized per
QCI
Downlink
pmPdcpLatTimeDlQci/pmPdcpLatPktTransDlQci×
Integrity Latency per
100%
QCI [ms]
Downlink
(pmPdcpVolDlDrbQci-
Throughput
Integrity pmPdcpVolDlDrbLastTTIQci)/pmDrbThpTimeDlQ
per QCI
ci/1000000
[Mbps]
Uplink
Throughput pmLcgThpVolUlLcg/pmLcgThpTimeUlLcg/100000
Integrity
per LGC 0
[Mbps]
(pmPdcpPktDiscDlPelrQci+pmPdcpPktDiscDlPelr
UuQci+pmPdcpPktDiscDlHoQci+pmPdcpPktDisc
DL Packet
DlAqmQci)/
Integrity Error Loss
(pmPdcpLatPktTransDlQci+pmPdcpPktTransDlQ
Rate per QCI
ci+pmPdcpPktDiscDlPelrUuQci+pmPdcpPktDiscD
lHoQci+pmPdcpPktDiscDlAqmQci)×100%
UL Packet pmPdcpPktLostUlQci/
Integrity Loss Rate per (pmPdcpPktReceivedUlQci+pmPdcpPktLostUlQci
QCI )×100%
pmVoipQualityUeUlOk/
Integrity VoIP Integrity (pmVoipQualityUeUlOk+pmVoipQualityUeUlNok)
×100%
Integrity(L14B) 00%
(pmHoPrepSuccLteIntraFQci+pmHoPrepSuccLteI
Intra LTE HO nterFQci)/
Mobility Success Rate (pmHoPrepAttLteIntraFQci+pmHoPrepAttLteInter
per QCI FQci)×pmHoExeOutSuccQci/pmHoExeOutAttQci
×100%
srvcc
Handover
Mobility pmHoPrepSucc/pmHoPrepAtt×100%
Prepartion
Success Rate
srvcc
pmHoPrepSucc/pmHoPrepAtt×pmHoExeSucc/pm
Mobility Handover
HoExeAtt×100%
Success Rate