Professional Documents
Culture Documents
• Voice call
• SMS
• Interworking between the LTE access and the 2/3G accessess
•
1.5 Usability requirements
• Dialing format, CLI display and SMS sending works same way as
calling between any GSM- and other terminal
• The use of LTE access technology is hidden by the terminal from the
end user
1.6 Security
User plane security is based on the LTE access security. On the control
plane (SIP signaling) USIM based IMS AKA is applied for the authentication
and the IMS signaling security capabilities based on the IPsec are applied.
MSC-s is enhanced with two inter system handover related components. The
first one being the SRVCC(Single Radio Voice Call Continuity), which is the
functionality defined in the rel-8 for enabling the inter system handover from
the LTE-access toward the CS-core. According to the specification this is an
additional capability in the MSC-s. The other additional component for the
system is the DTF (Domain Transfer Function). DTF has been defined in the
rel 7 Dual Radio VCC concept (23.206) and is used for the anchoring of the
calls. In the SRVCC context the DTF is also used fordoing the anchoring.
Release 8 SRVCC defines only the domain transfer from the LTE access to
the CS network and therefore in this architecture the anchoring is done only
for the calls that are initially using the LTE access.
slide added
Below is two possible architectures for implementing the solution for the core
network side. First option is the voice service deployment with IMS-core, in
this case the NVS uses the ISC interface toward the IMS core. IMS option is
shown in Figure 2. If the CS-access networks services are to be moved to
the IMS side the CS-network may be upgraded by having a I2 interface
toward the IMS, or the calls may be routed through CAMEL routing
capabilities to the IMS as indicated in the Figure 3.
Figure 2 Network reference architecture with IMS
Um
Uu
Figure 3 Network reference architecture with IMS enhanced to include also IMS
centralized services
Um
For a MSS based solution there exists also a possibility to deploy the NVS
only for the voice and SMS, for some part of the subscribers, then there is
also an option for deploying the NVS through the Mw´ interface toward the A-
SBC (Figure 4).
Uu
Um
Figure 4 Network reference architecture with fast track option
Uu
1.8 Technical Solution
• The solution is based on following subsystems and components
1.8.1 MSC Server (MSC-s)
MSC-s is the physical network element that implements firstly the basic
MSC-s and VLR functions for the CS-access, but in addition has the
capability to support the NVS, SRVCC and DTF software components.
1.8.1.1 NVS
Nokia Siemens Networks Mobile Voip Server (NVS) is collocated with the
3GPP R4 MSC Server (MSS). The solution is mainly targeted at operators
with existing 3GPP R4 infrastructure that want to introduce VoIP service by
re-using existing investments. Reuse of MSC Server has the advantage of
having one common MGCF both in the 3GPP R4 network and in the IMS
(when applicable), and a common Media Gateway (MGW) as well. The NVS
being part of MSS server platform can also be reused to provide services
both for fixed and mobile subscribers.
SRVCC initiation is coming from the MME and the SRVCC capability is
converting the Sv functionalities to the CS-access network A/Iu-interface
signaling in the case of intra MSC handover, or to the E-interface signaling in
case of inter MSC handover. During SRVCC initiation MME delivers the
related STN-SR relating to the subscriber. SRVCC functionality is responsible
for initiating the call toward the anchoring point (indicated by STN-SR).
1.8.1.3 DTF
Domain Transfer Functionality (DTF) is responsible for doing the anchoring of
the calls. In LTE case only the VoIP calls are anchored. If call originates in
CS domain the anchoring is not applied, while the SRVCC from CS to LTE
domain is not supported at a moment. With this approach also networks
resource usage is optimized.
1.8.2 MGW
MSS MGCF / Multimedia Gateway (MGW U4.1) ensures connectivity to the
CS/PSTN domain. The MGW consists of several functional elements
configured under the gateway architecture. The operator can use a number
of different configurations of the Multimedia Gateway depending on the
services the operator requires.
Figure 6 the terminals registration signalling in detail. Figure 7 shows the terminals
de-registration signalling.
Terminal sends INVITE in the LTE access. During the call establishment
signaling A-BCF links the SIP session setups media negotiation to the LTE
access resource reservation. Media reservation is done from A-BCF over the
Rx interface toward PCRF, which is responsible for policy control
functionalities. PCRF forwards the resource request indication to the SAE-
GW, which then handles the media reservation further toward the LTE
access. Policy control functionality ensures controlled use of LTE access
resources.
Call is anchored for enabling the potential domain transfer to the CS-domain.
NVS performs the originating service execution, including IN and other
services. At the end the call is routed toward the terminating network.
G
Figure 9 Mobile originated call setup toward PSTN
Figure 9 shows the mobile originated call setup toward the PSTN. In LTE
access the bearer setup is done form network toward the terminal and the A-
SBC contacts the police control (PCRF) for the sesource control.
NVS supports the emergency call delivery on a per cell level routing for
registered subscribers. If that is sufficient for the regulatory requirements the
emergency calls can be delivered in LTE-domain. If this is not sufficient the
terminal needs to be configured such way that it performs terminal initiated
fall back to CS network in the emergency call case.
While GMSC receives terminating call for a subscriber, it makes the HLR
enquiry (SRI=Send Routing Information). If the terminal is registered to the
LTE access the roaming number is allocated from the NVS. GMSC routes the
call toward the NVS. NVS performs the subscribers terminating services
makes the call anchoring and forwards the INVITE toward the called party.
During the call establishment signaling A-SBC links the SIP session setups
media negotiation to the LTE access resource reservation. Media reservation
is done from A-SBC over the Rx interface toward PCRF, which is responsible
for policy control functionalities. PCRF forwards the resource request
indication to the SAE-GW, which then handles the media reservation further
toward the LTE access. Policy control functionality ensures controlled use of
LTE access resources.
/3G
Figure 11 Mobile terminated call from PSTN
Figure 11 shows the signalling flow for the mobile terminating call from PSTN. Call
setup from GMSC toward the NVS is using standard MAP based routing
mechanisms. Call setup from the NVS toward the terminal (SIP-UA) is done with
release 8 IMS SIP signalling mechanisms.
2.5 Short Message Service
SMS service functions on the network side exactly the same way as in basic
CS-access network, using the same MAP procedures and related interfaces.
From the NVS toward the LTE access NVS uses SMS-payload type in the
SIP-MESSAGE method as defined by 3GPP, so the terminal interface is the
same as in SMS over IP specification. With this approach the standard HLR
functionality can be applied without any additional requirements.
Figure 12 describes how the Mobile Terminated SMS is delivered toward the
terminal in the LTE access.
G
Mobile originating SMS delivery follows the same principles, so that over the
LTE access the delivery is done with SMS over SIP and NVS converts the
SMS delivery to the CS-core network methods. Figure 13 describes the MO
SMS signalling interoperation
7. Because the MESSAGE was not delivered yet to the recipient and it was
just successfully submitted to SMSC for delivery not 200 OK but 202
Accepted is sent back to the UA-A.
3. SMSC delivers the MT-SM via routing the MAP MTForwardSM operation
to the NVS-B based on the received VMSC address.
5. The MESSAGE is sent out to the UA-B on SIP Normal Access interface.
SRVCC enables the end users voice calls continuity while moving from LTE
VoIP coverage to the 2G/3G CS-voice domain. Figure 15 describes the
functionality during the call setup. UE initiates the call and the call gets
anchored in the DTF residing in the NVS. While only the LTE to 2G/3G
direction has been specified and also for network resource usage
optimization resons the call is anchored only in the case when the call isi
initiated in the LTE access. For 2G/3G originated calls the call is routed
normally and there is no need for extra resources.
Voice over CS for 2G
Figure 16 SRVCC domain change from LTE toward CS
Figure 16 describes the functionality when the UE moves from the LTE
coverage area to the 2G/3G area. UE sends measurement information to the
eNodeB, which initiates handover toward MME. While MME receives a
intersystem handover request for certain QoS value (QCI=1) it triggers an
SRVCC toward the MSS. LTE subscriber has in the subscription information
STN-SR information, which is used in the MSS for VCC anchoring call setup.
When MSS receives the SRVCC indication from the MME, it initiates the
resource setup toward the target BSS/RNC and also initiates the call toward
the VCC anchoring point by using the STN-SR.
Voice over CS for 2G/3
Figure 17 Signalling connection after the domain change
Figure 17 shows the signaling what is the signaling connection after the
SRVCC. In the LTE side the resources are released. And the call continues
on the CS-access. In parallel with the voice calls SRVCC functionality there
may also be a parallel packet connections inter system handover
functionality. This functionality is of course dependent, whether the UE has
parallel packet session ongoing, whether the target access network has
parallel voice and packet access capability (3G, or DTM) and whether the
packet core is supporting the PS-PS inter system handover capability.
The selection of the service environment is done during initial registration and
if the subscriber has the subscription in the IMS/HSS the subscriber will be
served by the IMS and if not then the registration will be forwarded to NVS
and the fast track voice system is utilized.
Figure 18 Fast track and IMS coexistence
2.8 Roaming evolution
2.8.1 Phase 1
While the LTE is introduced with the 3GPP release 8 functionalities are
existing in the network. Release 8 does not yet specify the emergency call
handling in the LTE environment, so the assumption here is that the
emergency calls would be using CS networks in both nome network and
visited network cases.
Fast track VoIP solution is used only when own LTE network is used. While
the end user moves to some other network then the CS fallback and/or CS
network is used. With this approach the LTE introduction can be done such
way that the existing roaming agreements can still be used without changes.
2.8.2 Phase 2
Phase 3 solution assumes already wide IMS deployment also from visited
networks. In this phase all the calls from LTE access can be handled in IMS
domain and the CS-network is used only when using 2G or 3G-access.
In the network evolution the phase 1 will probably exist quite long time, but
with the LTE fast track voice approach proposed in this document a good
basis for future evolution is created also for the roaming functionalities.