Sei sulla pagina 1di 49

RCS

VoLTE Interoperability Event 2012


Multivendor testing in global
RCS/VoLTE Networks

HostSites

OperatorSponsor

EventSponsor

SilverSponsor

Participants

Page 1

Abstract
ThiswhitepaperprovidesasummaryoftheRCS(RichCommunicationsSuite)VoLTE(VoiceoverLTE)
Interoperability event 2012 which took place from September 24th October 12th 2012. The event
wasjointlyorganisedbytheMultiServiceForum(MSF),EuropeanTelecomsStandardsInstitute(ETSI)
andtheGSMAssociation(GSMA).
InordertofacilitatethedeploymentofNGNtechnology,itisimportanttoidentifyandunderstand
thelevelofinteroperabilityofcommerciallyavailableequipmentforbothbackwardsincompatibility
andnoncompliancy,frombothaVendors'perspectiveandanOperators'perspective.Vendors'gain
fromthebenefitofidentifyingissuesandimprovingproductstobecomemorecommerciallyviable,
and Operators need to be awareof any backwards incompatibility aspects to take into account for
vendor selection and deployment strategy. Public multivendor interoperability events such as the
RCSVoLTEIOTeventhelptodetectandfixtheseissuesatanearlystage
TheeventbuildsonthesuccessofpreviousMSFVoLTEInteroperabilityeventsandETSIIMSPlugtests.
It reflects the industrys drive to continue to deliver major carrier driven events that benefit all its
membersintheirquesttokeeppacewithaneverfastermovingindustry.
The RCS VoLTE Interoperability event 2012 focused on validating key network and application
interfaces to ensure multivendor deployment strategies for LTE/EPC/IMS technology for RCS and
VoLTE.ThemainobjectivewastovalidatetheworkoftheGSMAaspartofitsglobalVoLTEinitiative,
focusing on the validation of a number of GSMAs technical recommendations, namely PRD IR.92
(IMSProfileforVoiceandSMS),PRDIR.65(IMSRoamingandInterworkingGuidelines),PRDIR.88
(LTE Roaming Guidelines), PRD IR.90 (RCS Interworking Guidelines), PRD IR.67 (DNS/ENUM
GuidelinesforServiceProvidersandGRX/IPX),PRDIR.58(IMSProfileforVoiceoverHSPA)andPRD
IR.94 (IMS Profile for Conversation Video Service). Different versions of RCS Services and Client
Specifications were valid to be tested in the event, namely RCSe Advanced Communications:
Services and Client Specification: Version 1.2.1 and "Rich Communication Suite 5.0 Advanced
Communications:ServicesandClientSpecification.
TheGSMAtechnicalrecommendationsarebasedonTheThirdGenerationPartnershipProject(3GPP)
standards.3GPPintroducedtheEvolvedPacketCoretosupportLTEaccesswiththeIMScorenetwork
providingtheapplicationlayerforwhichservices(e.g.voice)maybedeployed.TheEPCandIMScore
interact with the Policy and Charging Control (PCC) framework to enable Quality of Service for the
bearerssupportingvoiceandRCSservices.
ETSI,asoneofthepartnersoftheThirdGenerationPartnershipProject(3GPP),hasplayedakeyrole
towards the deployment of IMS via its Technical Committee dedicated to IMS Network Testing: TC
INT.
RCSVoLTEIOT2012TestPlansweredevelopedandsourcedfromeachofthepartnerorganisations:

ETSIcontributedtowiththefollowingTCINTTestSpecifications:TS186011IMSNetwork
toNetworkInterfaceInteroperability,TS102901IMSNetworktoNetworkInterface
InteroperabilityforRCSandTS103029IMS&EPCInteroperability.

GSMAcontributedwithasubsetofitsRCSIOTRCSev1.2testcases.

MSFcontributedtheVoLTEtestcases.

The event was conducted in two host sites at the Sintesio facility in Kranj, Slovenia and the China
Mobile Research Institute Laboratory in Beijing, China. Telekom Slovenia was a joint host at the
Sintesiosite.

Page 2

The event demonstrated that the GSMA technical recommendations, based on the 3GPP
specifications, for providing end to end communications services based on IMS infrastructure were
matureandinteroperable.
Highlightsoftheeventincluded:

MultivendorinteroperabilityofUEs/clients,networkinfrastructureandservices.

FullIPinterconnectbetweenthetwohostsitesviaIPXwasdemonstrated,

VoLTE and multimedia (voice/video) calls demonstrated together with multimedia


telephonyservicesaswellasconfigurationoftheseservices,

VoiceandvideocallswereestablishedwiththeappropriateQOS(qualityofservice)utilizing
thepolicyframework.DIAMETERRoutingAgents(DRAs)successfullyprovidedthecapability
to simplify the routing within the PLMN and between PLMNs when subscribers were
roaming.TheusageofDRAsgreatlyreducednetworkconnectionsandwerealsoshownto
provideinterworkingfunctionality.

RCSservicesweredemonstrated

InparallelwiththeIOT,aworkshoponthetopicNextGenerationServices:RCS,VoLTEandbeyond
wasorganizedbyETSI.Theworkshopcoveredagoodrangeofpresentationsandraisedaspectrumof
issues, from device clients, provisioning, media management and integration to network
interconnections.Withpositiveresultsoutoftheevent,thegeneralconclusionisthatRCSandVoLTE
are now well on their way to mass implementation with a good basis of clear standards,
interoperabilityguidelinesandcarrierscooperation.

Page 3

CONTENTS
Contents ......................................................................................................................... 4
Executive Summary ....................................................................................................... 5
Introduction ................................................................................................................ 5
Architecture................................................................................................................ 5
Key Objectives ........................................................................................................... 9
Key Statistics ............................................................................................................. 9
Introduction .................................................................................................................. 11
Part I: Participants and Planning .................................................................................. 13
Host Sites ................................................................................................................. 14
Participants ............................................................................................................... 15
Observing Companies / Organizations .................................................................... 18
Part II: The RCS VoLTE Interoperability Event 2012 Execution ............................... 19
The Network Test Scenarios .................................................................................... 22
Test scenario validation ........................................................................................... 23
Part III: Results and Observations ............................................................................... 25
Future Work ............................................................................................................. 28
Appendix A: The Test Scenarios ................................................................................. 29
RCS VoLTE in a Home/Single Network ................................................................. 29
RCS/VoLTE for Roaming & Interconnect .............................................................. 33
Appendix B: Additional Testing .................................................................................. 39
Appendix C: Interface References ............................................................................... 41
Appendix D: The Organisers ....................................................................................... 44
Appendix E: The Hosts ................................................................................................ 45
Appendix F: The Participants ...................................................................................... 46

Page 4

EXECUTIVESUMMARY
INTRODUCTION
TheRCSVoLTEInteroperabilityEvent2012wasdesignedtoteststandardscomplianceofLongTerm
Evolution(LTE)andIMSnetworkscenariosinsupportoftheprovisionofRichCommunicationSuite
(RCS)andVoiceoverLTE(VoLTE).SuchnetworkscenariosareofinteresttomajorServiceProviders,
and the event is intended to gauge vendor support for this technology. This event builds on the
previous MSF VoLTEInteroperabilityEventand ETSIIMSPlugtests.Itseeks tovalidateanumberof
GSMAtechnicalrecommendations,namely:

RCSeAdvancedCommunications:ServicesandClientSpecification:Version1.2.1

RichCommunicationSuite5.0AdvancedCommunications:ServicesandClientSpecification

PRDIR.65IMSRoamingandInterworkingGuidelines,

PRDIR.88LTERoamingGuidelines,

PRDIR.92IMSProfileforVoiceandSMS,

PRDIR.90RCSInterworkingGuidelines,

PRDIR.67DNS/ENUMGuidelinesforServiceProvidersandGRX/IPX,

PRDIR.58IMSProfileforVoiceoverHSPA,

PRDIR.94IMSProfileforConversationVideoService.

Interoperabilitytestingwasconductedin2labs;theSintesiofacilityinKranjandtheCMCCResearch
Lab in Beijing. The two labs were interconnected via an IPX. Conducting the tests in two
interconnected labs made it possible to test more vendor combinations, and also allowed realistic
testingofimportantroamingandinterconnectscenarios.
Atotalof210testcaseswerewrittenacross2testscenarios:

RCSVoLTEinasingle/homenetwork,

RCSVoLTEforRoaming&Interconnect.

During the event, there was also a background activity to perform SIP / DIAMETER conformance
criteriacheckingonthetracefilesgeneratedduringtheRCSVoLTEscenariosandvalidatinganumber
ofETSIInteroperabilityTestSpecifications.
Finally,aninterRATcalltransferfromLTE/IMStoGERAN/MSCServerwasdemonstrated.

ARCHITECTURE
TheRCSVoLTEarchitectureallowsuserstoconnecttothenetworkviatheLTEhighspeedwireless
access and access voice, video and RCS services provided by MultiMedia Telephony and RCS
ApplicationServersonanIMSframework.Thisway,accesstotheapplicationsandservicesrequested
by today's sophisticated users, benefits from the necessary Quality of Service management and
mobilityfunctions.
ThebasicRCSVoLTEarchitectureisshowninFigure1below:

Page 5


IMS Core

MMTel / RCS
Application
Servers

Ut
Sh

UE

GERAN

I
S
C

Cx

Mr

MRF
Mr

IMS UA
S4 SGSN

S6d

HSS

UE

Cx
Sh

P-CSCF

UTRAN

IMS UA

Mw

Mx

I/S-CSCF

Ici/Izi

S6a
ENUM

DRA
S6a

Rx
Gx
PCRF

S3

ENUM
Server

ENUM

Gx

MME
UE

IBCF/TrGW

Rx

IPX

Ici/Izi

S1-MME
SecGW

LTE-Uu

IMS UA

S11

ENUM

S1-U
eNodeB

S4

SGi
S-GW

S5

Other PLMN

P-GW

S12

FIGURE 1 BASIC RCS VOLTE ARCHITECTURE

NOTE: TheGminterface(UEtoPCSCF)isafocusfortestingalthoughnotexplicitlyshown
intheabovefigure.
ThemaincomponentsoftheArchitecturearedescribedbelow.

UE(UserEquipment).TheUserEquipmentthatisusedtoconnecttotheEPS,inthefigure
abovethisisanLTEcapableUEaccessingEPSviatheLTEUuradiointerface.

eNodeB.TheevolvedRAN(EUTRAN)consistsofasinglenode,theeNodeBthatinterfaces
withtheUE.TheeNodeBhoststhePhysical(PHY),MediumAccessControl(MAC),RadioLink
Control (RLC), and Packet Data Convergence Protocol (PDCP) layers that include the
functionalityofuserplaneheadercompressionandencryption.ItalsooffersRadioResource
Control (RRC) functionality corresponding to the control plane. It performs manyfunctions
including radio resource management, admission control, scheduling, enforcement of
negotiated UL QoS, cell information broadcast, ciphering/deciphering of user and control
planedata,andcompression/decompressionofDL/ULuserplanepackedheaders.

MME (Mobility Management Entity). The Mobility Management Entity (MME) is the key
controlnode for the LTE accessnetwork. It is responsible for idle mode UE tracking and
paging procedures including retransmissions. It is involved in the bearer activation /
deactivationprocessandisalsoresponsibleforchoosingtheSGW(seebelow)fortheUEat
theinitialattachandattimeofintraLTEhandoverinvolvingCoreNetworknoderelocation.
It is responsible for authenticating the user (in conjunction with the HSS). The NAS (Non
Access Stratum) signalling terminates at the MME which is also responsible for the
generation and allocation of temporary identities to the UEs. The MME validates the
permissionoftheUEtocampontheserviceprovidersPLMN(PublicLandMobileNetwork)
andenforcesUEroamingrestrictions.TheMMEistheterminationpointinthenetworkfor
ciphering/integrity protection for NAS signalling and handles security key management.
LawfulinterceptionofsignallingisalsoafunctionprovidedbytheMME.TheMMEprovides
the control plane function for mobility between LTE and 2G/3G access networks and
interfaceswiththehomeHSSforroamingUEs.

Page 6

SGW(ServingGateway).TheSGWroutesandforwardsuserdatapackets,whilealsoacting
asthemobilityanchorfortheuserplaneduringintereNodeBhandoversandastheanchor
formobilitybetweenLTEandother3GPPtechnologies(terminatingS4interfaceandrelaying
thetrafficbetween2G/3GsystemsandPDNGW).ForidlestateUE,theSGWterminatesthe
DLdatapathandtriggerspagingwhentheDLdataarrivesfortheUE.Itmanagesandstores
UEcontextsandperformsreplicationoftheusertrafficincaseoflawfulinterception.TheS
GWandPGWfunctionscouldberealizedasasinglenetworkelement.

PGW(PacketDatanetworkGateway).ThePGWprovidesconnectivitybetweentheUEand
externalpacketdatanetworks,itprovidestheentryandexitpointoftrafficfortheUE.AUE
mayhavesimultaneousconnectivitywithmorethanonePGWforaccessingmultiplePacket
Data Networks. The PGW performs policy enforcement, packet filtering for each user,
chargingsupport,lawfulinterceptionandpacketscreening.ThePGWalsoactsastheanchor
for mobility between 3GPP and non3GPP technologies such as WiMAX or DSL. The SGW
andPGWfunctionscouldberealizedasasinglenetworkelement.

PCRF(PolicyChargingandRulesFunction).ThePCRFprovidespolicycontroldecisionsand
flowbasedchargingcontrols.ThePCRFdetermineshowaservicedataflowshallbetreated
in the enforcement function (PGW in this case) and ensure that the user plane traffic
mappingandtreatmentisinaccordancewiththeusersprofile.

HSS (Home Subscriber Server). The HSS is a network database that holds both static and
dynamicdataelementsrelatedtosubscribers.TheHSSprovidesuserprofileinformationto
theMMEandIMScoreduringUEattachandIMSregistration.

S4SGSN(ServingGPRSSupportNode).TheSGSNsupportsthelegacyaccessforUTRANand
GERAN.IntheEPSarchitecture(3GPPrelease8)theSGSNisenhancedtosupporttheS4and
S3 interfaces (hence referred to as the S4 SGSN). The S4 interface provides control and
mobilitysupportbetweenGPRSCoreandthe3GPPAnchorfunctionoftheServingGW.The
S3 interface enables user and bearer information exchange for inter 3GPP access network
mobility.

PCSCF(ProxyCallSessionControlFunction).ThePCSCFistheinitialpointofcontactfor
session signaling for the IMSenabled VoLTE UE. The PCSCF behaves as a SIP proxy by
forwardingSIPmessagesbetweentheUEandtheIMSCoreNetwork,maintainsthesecurity
associations between itself and the VoLTE UE, and incorporates the Application Function
aspect of PCC to enable binding of the IMS session with the bearer for applying dynamic
policyandreceivingnotificationsofbearerlevelevents.

I/SCSCF (Interrogating/Serving Call Session Control Function). The ICSCF is the contact
point within an operator's network for all connections destined to a user of that network.
OnIMSRegistration,itinterrogatestheHSStodeterminewhichsuitableSCSCFtoroutethe

Page 7

requestforregistration.ForMobileTerminatingcalls,itinterrogatestheHSStodetermine
whichSCSCFtheuserisregisteredon.
TheSCSCFprovidessessionsetup,sessionteardown,sessioncontrolandroutingfunctions.
It generates records for billing purposes for all sessions under its control, and invokes
applicationsintheApplicationServers.TheSCSCFactsasSIPregistrarforVoLTEUE'sthat
theHSSandICSCFassigntoit.ItqueriestheHSSfortheapplicablesubscriberprofilesand
handles calls involving these end points once they have been registered. The SCSCF uses
subscription information to determine the appropriate onward routing for calls originating
throughit.

MMTelAS(MultimediaTelephonyApplicationServer).TheMMTelASisanIMSApplication
Server providing support for multimedia telephony services as defined by 3GPP e.g.
supplementaryservicefunctionality.

MRF(MediaResourceFunction).TheMRFisacommonmediaresourcefunction,foruseby
IMS Application Servers and I/SCSCFs, to provide media plane processing independent of
application types. Eg. The MRF provides multimedia transcoding, video share/calling,
multipartymultimediaconferencing,networkannouncements/tones,interactivevoice/video
services,etc.underthecontrolofIMSApplicationServers(MMtelASorRCSVideoServers)
aswellasbasicmediaprocessingfunctionstoCSCFs.ThecontrolplaneinterfacestoMRFs
are defined by the 3GPP references Mr, Mr, and Cr interfaces (SIP/SDP and XML encoded
media service requests) while the media plane interfaces to MRFs are defined by 3GPP
referenceMbforRTP/RTCPandMSRPmultimediatransport.

IBCF/TrGW (Interconnection Border Control Function / Transition Gateway). The


IBCF/TrGW is responsible for the control/media plan at the network interconnect point to
otherPLMNs.

RCSASs.TheRCSApplicationServersprovidesupportforRCSrelatedservicesandcomprise
thefollowingelements:
PresenceServer&XDMServer,
IM/ChatServer,
VideoShareApplicationServer.
FileTransfer,
ImageTransfer

SecGW (Security Gateway). The SecGW is used to originate and terminate secure
associations between the eNodeB and the Evolved Packet Core network. IPsec tunnels are
established with preshared security keys, which can take a number of different formats.
IPsectunnelsenforcetrafficencryption,foraddedprotection,accordingtotheparameters
exchanged between the two parties during tunnel setup. This enables secure
communicationsbetweentheeNodeBandEPCacrosstheS1MME,S1UandX2interfaces.

DRA(DiameterRoutingAgent).TheDiameterRoutingAgentdefinedby3GPPandGSMA,is
a new network element that controls Diameter signalling, enabling the seamless
communication and control of information between network elements within LTE or IMS
networksandacrossLTEnetworkborders.ADRAreducesthemeshofDiameterconnections
thatnegativelyimpactsnetworkperformance,capacityandmanagement.Forroamingcases,
theDRAmayalsoactasaDEA(DiameterEdgeAgent).

Page 8

ENUMServer.ThiselementprovidesadatabasefunctionalitytoenabletranslationofE164
numberstodomainnamestoenablemessageroutingofIMSsessions.Intheabovefigure,a
singleENUMServerisshownthatisaccessiblefromeitherPLMNaswellasIPX.

IPX. This is the IPExchange transit network providing an interconnect capability between
PLMNs.

KEYOBJECTIVES
It is vital that operators have confidence in the multivendor interoperability of LTE and IMS
componentsasasolidbasisforRCSVoLTEbeforevolumedeploymentcanbegin.Demonstratingthis
capabilityinactionwasakeyoverarchingobjectiveoftheRCSVoLTEInteroperabilityEvent2012.The
followingequipmenttypes(andassociatedvendorinstances)participatedintheevent:

InSlovenia,theequipmenttypesincludedLTEUE(1),VoiceClient(2),RCSClient(1),eNodeB
(1),EPC(MME/SGW/PGW)(1),PCRF(1),HSS(1),IMSCore(I/SCSCF)(2),PCSCF(3),MRF
(1),MMTELAS(2),RCSChatServer(1),RCSVideoServer(1),DRA(1),IBCF(2),ENUM(1),IPX
(1)andmonitoringequipment(1).

InChina,theequipmenttypesincludedLTEUE(1),VoiceClient(1),eNodeB(1),EPC(MME/S
GW/PGW)(1),PCRF(1),HSS(1),IMSCore(I/SCSCF)(1),PCSCF(1),MMTELAS(2),DRA(2),
IBCF(1),ENUM(1),IPX(1)andmonitoringequipment(1).

NBtherewasnoSecurityGWintheevent.
NB In some cases, a single vendor brought multiple instances of a given equipment to facilitate
additionalparalleltestingconfigurations.
Inaddition,theRCSVoLTEInteroperabilityEvent2012wasdesignedto:

ValidatethematurityofLTEnetworkinterfacestoenablemultivendorsupport.

Demonstrate that an LTE network can manage session control with an applied Quality of
Servicefordefaultanddedicatedbearersforvoice,videotelephonyandRCSservices.

ValidatethematurityofIMSnetworkinterfacestoenablemultivendorsupport,

Demonstratethesupportforuserroamingbetweendifferentnetworks.

ValidateVoLTE,MMTelandRCSservicesforbothhomeregisteredandroamingUEs,

ValidateVoLTE,MMTelandRCSservicesoverinterconnectedIMSnetworks,

DemonstratetheuseofDRAstosimplifyDIAMETERroutingwithinthePLMNandbetween
PLMNswhensubscriberswereroaming.

DemonstratetheuseofanIPXtoprovideinterconnectionbetweenseveralPLMNs,

DemonstratetheuseofENUMtoenableinterdomaincallrouting.

KEYSTATISTICS

Page 9

TheRCSVoLTEInteroperabilityEvent2012washeldfromSeptember24thtoOctober12th2012attwo
host sites; China Mobile Research Institute Laboratory in Beijing, China and the Sintesio facility in
Kranj,Slovenia.
Over 50 network components from 12 participating companies were tested by 51 test engineers
usingapproximately1200pagesoftestplansduringthis3weekevent.
Thetwotestscenariosincorporatedatotalof210testcases.Ofthe210definedtests,atotalof48
wereexecutedofwhich46testsweresuccessfullycompletedand2failed.Overall,acrossbothhost
sites,atotalof98testcaseswererecordedintheeventrecordingtool.Inthosecaseswheredefined
testswerenotrun,itwasduetoacombinationoflabconfigurationlimitations,equipmentlimitations
orlackoftime.AppendixAgivesadetailedsummaryofthetestresults.

KeyResults

MultivendorinteroperabilityofUE,eNodeB,EPC,IMSCore,AS,DRAandPCC.

Interaction with service layer (e.g. IMS) was successfully demonstrated, with binding of
Quality of Service to EPC bearers utilising Policy and Charging Control (PCC), providing
relevantQoSforsignallingandvoice/video/RCSServicesonthedefaultbeareranddedicated
bearersrespectively.

Voicecallsestablishedusingdedicatedbearer(QCI=1),

UsageofanumberofserviceswasdemonstratedviaMMTELAS.

Voice / Videocalls established using dedicated bearers (QCI=1&QCI=2),inclusive of video


beingadded/removedto/fromanexistingvoicesession.

GTPisstable.AsinthepreviousVoLTEIOTeventin2011,therewerenoissueswithGTP,

There were very few issues with DIAMETER, which was observed to be much more stable
than in the previous VoLTE IOT event in 2011. The use of a DRA reduced connections and
simplified Diameter message routing. DRAs were also shown to provide interworking
betweendifferenttransportlayerprotocolsandDIAMETERapplicationimplementations.

MMTELServiceconfigurationviaUtwasdemonstratedforanumberofservices.

Transcoding,transratingandDTMFcollectiondemonstratedviaMMTELASandMRF.

RCSChat&FT(FileTransfer)weredemonstrated,

Voice calls over a network interconnect were demonstrated via an IPX with SIP/RTP
traversingtheIPXGatewayandtheIBCF/TrGWsineachPLMN.

DIAMETER message routing was demonstrated for remote attachment of a roaming UE


wheretheDIAMETERmessagingtraversedtheDRAintheIPXandtheDEAsineachPLMN.

IMS(VoLTEandRCS)softclientsinterworkedwithanumberof3rdpartyLTEdatadonglesfor
LTEAttachand,additionally,withdifferentIMSCoreNetworkandMMTel/RCSAStoprovide
IMSservicestotheenduser.

Commercial test tools used provided uncompromising visibility to all End2End procedures
allowingrapidanalysis.

Page 10

INTRODUCTION
TheRCSVoLTEInteroperabilityEvent2012testenvironmentwasbasedon:
1.

ProvingmultivendorinteroperabilityofRCSVoLTEArchitectureforsingle/homenetworkand
Roaming&Interconnectscenarios;

2.

QoScontrolasanessentialunderpinningforservicesusingPCCarchitectureandbindingto
theapplicationlayerinIMS;

3.

ProvingVoLTEand Video Telephony, including MMTel services viaEPC andIMS,aswell as


interactionwiththePCCarchitecture;

4.

ProvingRCSservicesviaLTEandIMS,includinginteractionwiththePCCarchitecture;

5.

Roaming between LTE capable networks, including the proving of VoLTE, Video Telephony
(MMTel)andRCSServicesfortheroamingUE;

6.

Proving VoLTE, Video Telephony (MMTel) and RCS Services via the interconnect between
IMSnetworksoveranIPX;

7.

Proving interaction with an ENUM Server for interdomain call routing between IMS
networksviaanIPX.

OperatorsandEquipmentVendorsthatparticipateinInteroperabilityEventssuchasRCSVoLTE2012
learn how multivendor nextgeneration products and networks will interoperate in the real world.
Thisinsighttranslatesintoanumberofbenefits:

For vendors, a reduced time to market for deployment of interoperable solutions and
decreasedcostsandresourcestoresolveinteroperabilityissuesaswellasanopportunityto
demonstratetheircompetenceinagiventechnology.

For Operators, a better understanding of the maturity of a technology and an insight into
bestinclassproducts.

For the industry as a whole, a thoroughly evaluated architectural framework for


cooperatively designing endtoend networking solutions consistent with real world
deploymentscenarios.

In addition, publishing the results of the RCS VoLTE Interoperability Event 2012 provides valuable
feedback to the industry in general, including specific feedback to the Standards Development
Organizations (SDOs) when issues are encountered in the tested standards. This leads to improved
protocoldocumentationthroughclarificationsand/orcorrectionsoferrors.
Thiswhitepaperisorganizedintothreepartsandsixappendices:
PartI,describestheplanningoftheRCSVoLTEInteroperabilityEvent2012.
PartIIexplainshowthethreeweekeventwasrun,
PartIIIpresentsthekeyresultsobtainedfromtheRCSVoLTEInteroperability2012Event.
AppendixAprovidesdetailsonthemaintestscenarios;
AppendixBdescribesadditionaltestingduringtheevent;

Page 11

AppendixChighlightstheinterfacesthatweretested,
AppendixDprovidesabriefresumeoftheorganisers,
AppendixEprovidesabriefresumeofthehosts,
AppendixFprovidesabriefresumeoftheparticipatingcompanies.

Page 12

PARTI:PARTICIPANTSANDPLANNING
TheRCSVoLTEInteroperabilityEvent2012wasorganisedbyajointTaskForcecomprisingmembers
from the three partner organisations of MSF, ETSI and GSMA. Its goal was to test the current
capabilities of LTE and IMS products operating in real world Service Provider environments. In
particular,theeventfocussedonvalidatingRCSandVoLTEservices(RichCommunicationsSuiteand
VoiceoverLTE)baseduponGSMAtechnicalrecommendationsutilizing3GPPLTEaccesstechnology.
TheTaskForcedevelopedanumberoftestingscenariostovalidatecorenetworkinterfacestoensure
multivendordeploymentstrategiesforRCSVoLTE.
Thistestingallowedvendorstoimprovetheirproducts,ServiceProviderstoacceleratetheirservice
deploymentstrategies,andanystandardsshortfallstobehighlightedtotheappropriateSDO's.
Theeventcomprised3weeksoftestingprecededbyamandatory1weeksetupandinvolvedtwolab
sites interconnected via an IPX network, 12 participant companies, 51 engineers, 55 network
componentsand1200pagesoftestplans.
PlanningfortheRCSVoLTEInteroperabilityEvent2012beganinNovember2011byidentifying
scenariosandtestsfortheevent.ThescopeoftheeventisdefinedintheTestingScenariosdocument
whichispubliclyavailableattheeventwebsite
http://www.msforum.org/interoperability/RCSVoLTE.shtml.Atotalof5scenarioswereinitially
defined:_

RCSVoLTEinasingle/homenetwork,

RCSVoLTEforRoaming&Interconnect,

nonLTEaccesstoEPC,

Handover(intraLTEandLTE<>2G/3G)and

PriorityCallHandover(LTE/IMS<>OtherRAN/CS).

Eachofthe5mainscenariosincludedanumberofsubscenarios.Testplansweredevelopedforall
oftheidentifiedsubscenariosandweresourcedfromeachofthepartnerorganisations.
Duringtheeventplanning,itbecameclearthatcommercialequipmentwasunlikelytobeavailable
with the functionality required for all test scenarios. In addition, a test case survey was conducted
among registered participants to identify their main point of interest in the test scenarios.
Consideringthattherewerealargenumberoftestcasestoberungiventheplannedtimescale,the
effort was focussed on the highest priority scenarios and the numbers of tests to be run in those
scenarios reduced and prioritized to a more realistic overall total. This White Paper will therefore
onlydetailthetestscenariosthatwereexecutedduringtheRCSVoLTEInteroperabilityEvent2012.
Interlab testing was a key objective of the RCS VoLTE Interoperability Event 2012 with special
attention put to provide interlab connectivity reflecting real world deployment scenarios (i.e.
roamingandinterconnect).Inthatregard,thetwositeswereinterconnectedviaanintermediateIPX
networkwithalimitednumberofnetworkelements(i.e.DRA/IBCF)beingexposedtoit.
Theinitialactivityfocusedonlimiting(wherepossible)multivendorinteroperabilitytestingtothose
interfaces that reflect realistic deployment scenarios i.e. it was intended to test configurations
involving typical single vendor blocks of network elements and thereby limiting the number of
observedinterfacestothosebetweensuchblocks.Thefollowingequipmentgroupswereidentified:

UE,
eNodeB
EPC(MME,SGW,PGW),

Page 13

IMScore(P/I/SCSCF,HSS),
ApplicationServers,
MRF
BorderGatewayelements(IBCF/TrGWandPCSCF/IMSAGW),

To facilitate participation, vendor equipment was permitted to be located remotely from the host
site(s)subjecttocertainconstraints(i.e.UE,eNodeBandmonitoringequipmenthadtobelocatedin
the host lab and all relevant interfaces needed to be observable by the monitoring equipment).
RemotelylocatedkitwasconnectedintothehostsiteviaVPNsbasedontheL2TPprotocol.
Giventhecomplexityoftheeventandtohelpprioritizedemand,theeventTaskForcedevelopeda
testscheduletomaximiseintervendortestingandvendorparticipationforallsessions.Inparticular,
duetotheamountofequipmentintheSintesiosite,itwasdecidedtosplittheequipmentbetween
twologicalhalveswhichenabledmaximumuseoftheavailableequipmentattheSintesiosite(albeit
within a single PLMN) and also defining a number of different such configurations in response to
participant input to ensure that all permutations of multivendor testing were covered on the key
interfaces.
Testtraceswerecapturedbytheparticipatingtesttoolcompany(JDSU).AproprietaryETSIsourced
toolwasusedasaresultsrecordingtool.
Inadditiontotestplanning,hostsiteselection,preparationandnetworkinterconnectivityneededto
becompletedbeforethestartoftesting.AnumberofTaskForcemeetingswereheldandanumber
of vendor participation calls kept the participants informed of the preparation progress and their
neededinputsandactivities.The3weekeventwasprecededbyamandatorysetupweektoensure
thatthecomponentswereinstalledsothattestingcouldcommenceontimeintheeventproper.

HOSTSITES
Sintesio and CMCC provided host sites in Slovenia and China respectively, thereby allowing the
varioustests and scenarios to bedeployed in an environment that replicates a live global network.
Testingwasstructuredtoenablebothintrasiteandintersitetestingandatestschedulewasdevised
toenablestructuredtestingtobeperformedateachsiteaswellascoordinatingtheactivitybetween
thetwositesfortheroamingandinterconnectscenarios.
Thetwohostsiteswere:

Sintesio provided the host site at their facility in Kranj, Slovenia. This site was jointly hosted by
TelekomSlovenia.

ChinaMobileprovidedthehostsiteattheCMCCResearchLabinBeijing,China.

Page 14

PARTICIPANTS
TwelvecompaniesparticipatedintheRCSVoLTEInteroperabilityEvent2012.
Thenetworkequipmentvendorswere:

ThenetworkinfrastructureprovidersofIPXandENUMwere:

TheNetworkprotocolandcallflowanalysistestequipmentvendorwas:

Tables1and2showtheRCSVoLTEcomponentsprovidedbythevendorparticipantsattheSintesio
and Beijing sites respectively. In some cases, elements are tagged as Telecom Slovenia or CMCC,
indicatingelementsprocuredbythosehostsandsuppliedbyvendorcompaniesnotofficiallysigned
uptotheevent.AlsonotethatWiFiUEs,whilstnotafocusoftheevent,werealsopermittedtobe
usedinordertoprovideadditionalendpointsandincreasethelevelofparalleltesting.

Page 15

ElementType

Vendor(s)

LTEUE

Telecom
Slovenia

D2Tech

WiFiUE

Radisys

D2Tech

VoLTEClient

Radisys

D2Tech

RCSClient

D2Tech

eNodeB

Telekom
Slovenia

EPC(MME+SGW+PGW)

Cisco

HSS

PCRF

Tekelec

PCSCF/IMSALG

Cisco

Iskratel

I/SCSCF

Cisco

Iskratel

MMTelAS

Genband

Iskratel

MRF

Radisys

Iskratel

RCSVideoShareAS

Genband

RCSIM/ChatServer

Genband

IBCFTrGW

Iskratel

DRA

Ulticom

ENUM

Neustar

IPX

Aicent

MonitoringEquipment

JDSU

Table 1.
The RCS VoLTE
Sintesio host-site in Kranj, Slovenia

Iskratel

Metaswitch

Metaswitch

Interoperability

Page 16

vendor

participants

in

the

CMCC
LTE UE

CMCC

VoLTE Client

CMCC

RCS Client
eNodeB

CMCC

EPC (MME+SGW+PGW)

CMCC

HSS

CMCC

PCRF

CMCC

P-CSCF/IMS-ALG

Acme Packet

I/S-CSCF

Acme Packet

MMTel AS

CMCC

Tekelec

Genband

MRF
RCS Video Share AS

Genband

RCS IM/Chat Server

Genband

IBCF-TrGW

Acme Packet

DRA

Acme Packet

ENUM

Neustar

Monitoring Equipment

JDSU

Tekelec

Table 2. The RCS VoLTE Interoperability vendor participants in the China Mobile host-site in
Beijing, China.

Page 17

OBSERVINGCOMPANIES/ORGANIZATIONS
NonvendorcompanieswerepermittedtoattendRCSVoLTEInteroperabilityEvent2012asobservers.
InvitationswereextendedtoMSF/ETSI/GSMAnonvendormembersandpartnerfora/organizations.
Thefollowingcompanies/organisationsattendedtheeventasobservers:

Page 18

PARTII:THERCSVOLTEINTEROPERABILITYEVENT2012EXECUTION
TheRCSVoLTEInteroperabilityEvent2012involvedtwohostsites,theSintesiositeinKranj,Slovenia
and the China Mobile Research Institute Laboratory site in Beijing, China. The two labs were
interconnected via an IPX network. Both sites were connected to the IPXvia anIP Security (IPSec)
VirtualPrivateNetwork(VPN).AllintersiteconnectivitythustraversedtheIPXandmimickedreal
worlddeploymentwherebyPLMNsinterconnectviaanintermediateIPXnetwork.
Vendor equipment was permitted to be located remotely from the host site(s) subject to certain
constraints, namely that the UEs, eNodeBs and monitoring equipment needed to be located in the
hostlab.RemotelylocatedequipmentwasconnectedintothehostsiteviaVPNsbasedontheL2TPv3
protocol.Trafficonremoteobservedinterfaceswasroutedthroughacentralobservationpointatthe
hostsitesinordertoallowmonitoringequipmenttocaptureandanalyzeit.
Additional VPN connections enabled participants to have remote management access to any
equipment located in the host site, thereby enabling vendors to complement onsite staff with
personnel at home locations. The use of remotely located equipment enhanced flexibility and
reducedparticipationcostsforvendors.
Figure6presentsahighleveldiagramofthetestenvironmentusedfortheSintesio/TelekomSlovenia
hostsite.
.

Page 19

Figure6.TestenvironmentusedfortheSintesio/TelekomSloveniahostsite

Page 20

Figure7presentsahighleveldiagramofthetestenvironmentusedfortheChinaMobile,Beijinghostsite.

Page 21

THENETWORKTESTSCENARIOS
Figure8isahighlevelviewoftheEPCframework.TheEPCnetworkprovidescapabilitiestoattach
multiple access technologies into a single core network infrastructure. These include LTE, legacy
wireless access technologies (2G/3G), non3GPP wireless access and fixed access. The common
infrastructure provides a converged way to access a common service layer (e.g. Internet, IMS) and
applyaconsistentmethodofQualityofServicemanagementandmobilitymanagement.

IMS

Internet
SC

Policy

3GPP
Legacy
System

Evolved
Packet
Core

MM

Evolved

AAA

...

...

EUTRAN

Packet
Core

Non3GPP
Access
System

...

Figure8.TheEvolvedPacketCore
The Evolved Packet Core can be accessed using all mainstream wireline and wireless access
technologies,forconnectiontotheapplication/servicelayer(e.g.IMS,Internet).
ThishighlevelarchitectureformedthebasisofthescenariosfortheRCSVoLTEInteroperabilityEvent
2012.ThesescenariosfocusedonRCSVoLTEinthefollowingcases:
Home/SingleNetwork.InthisscenarioasingleinstanceoftheRCSVoLTEarchitecturewascreated
using components from different vendors. Testing included attachment and detachment from the
network, IPCAN session establishment, SIP registration (to IMS), SIP session establishment,
interactionwithIMSMultimediaTelephony,IMSConversationalVideoServicesandRCSservices.This
scenariofocusedontestinginteroperabilityofthefunctionalityasprofiledbyGSMAPRDsIR.92,IR.94,
IR.90,IR.67andtheRCSServicesandClientSpecification.
ThetestcasesforthisscenariowereextractedfromETSITS103029IMS&EPCInteroperability,a
numberofMSFTestPlansandasubsetofGSMAtestplansforRCSclientaccreditation.
Roaming & Interconnect. In this scenario, the local breakout model with visited PCSCF and home
operator applications was tested. The test set was the same as for the home/single network case,

Page 22

plussomeroamingspecificteststodemonstratethetransferofPolicyRulesbetweenhome/visited
networks,theusageofDiameterRoutingAgents,SessionBorderControllersanduseofENUM.This
scenariofocusedontestinginteroperabilityofthefunctionalityasprofiledbyGSMAPRDsIR.65,IR88,
IR.92,IR.94,IR.90,IR.67andtheRCSServicesandClientSpecificationThetestcasesforthisscenario
were extracted from ETSI TS 186 011 IMS Network to Network Interface Interoperability, TS
102901 IMS Network to Network Interface Interoperability for RCS and a number of MSF Test
Plans.
Outsideofthetwomainscenarios,thereweretwoadditionaltestingactivities:

abackgroundactivitytoperformSIP/DIAMETERconformancecriteriacheckingonthetrace
files generated during the RCS/VoLTE scenarios following ETSI Interoperability Test
Specifications:

aninterRATcalltransferfromLTE/IMStoGERAN/MSCServerwasdemonstrated.

ThemainscenariosaredescribedinmoredetailinAppendixAandtheadditionaltestingactivities
aredescribedinmoredetailinAppendixB.

TESTSCENARIOVALIDATION
JDSU
TheJDSUSignalingAnalyzersolution,inamultiusersetup,wasusedtovalidatethecompletedtest
scenarios at both the Sintesio and China Mobile Research Institute sites. This multiuser setup
provided the participants of the Interoperability Event a realtime end to end view of the test
scenariosastheywerebeingexecuted.
The Signaling Analyzer provides full support for all the requirements outlined in the major GSMA
technical recommendations for delivering Voice, Video services over LTE (V2oLTE) and Rich
CommunicationsSuite(RCS)servicesasspecifiedin5.0release.
TheSignalingAnalyzerprovidedanumberofkeycapabilities:

End to End EPC, Policy and Charging Control, IMS Core Network SubSystem, MMTel/RCS
ApplicationServersVisibility
RealTimeMultipleInterfaceendtoendCallSessionCorrelationandMeasurements
Realtimecontrolplaneanduserplanecorrelation
Access to common data source (probe) with the ability to perform independent
functions/operations
LTE/SAEsecurityEPSrealtimeNASEncryptiondeciphering
Generic file sharing of the test scenarios results (both in JDSU proprietary format and
Wireshark.pcapformat)

TheSignalingAnalyzersupportsanextensivesetofLTE/EPC/2G/3G/PCC/IMSCorenetworkinterfaces
and is able to validate the outcome of the test cases in realtime. After the validation of each
individualtestscenariothetracefilewassavedforpossiblefuturereferenceandtraceability.

TTCN3AutomaticConformanceReview
ETSI has developed an automatic tool to check recorded traces on conformance towards the base
standards. For this purpose recorded trace files were analyzed offline in accordance with the

Page 23

conformancecriteriadefinedinthetestspecifications.Thetesttoolspecificallyimplementedforthis
interoperabilityeventisbasedonthestandardizedtestinglanguageTTCN3(TestingandTestControl
Notation Version 3) and allowed automatic assignment of conformance test verdicts for message
flowscontainingSIPandDiametermessages.Theresultshavebeenfilledintothetestsessionreports
by ETSI representatives that had been present at the event for the purpose of running the TTCN3
tool.

Page 24

PARTIII:RESULTSANDOBSERVATIONS
The event demonstrated that the GSMA technical recommendations, based on the 3GPP
specifications,werematureandinteroperablefortheprovisionofVoLTE,VideoTelephonyandRCS
servicesoverLTEaccesstechnology.MultivendorinteroperabilityofUE,eNodeB,EPC,IMSCore,AS,
DRAandPCCwasdemonstrated.
ThetwohostsitesweresuccessfullyinterconnectedviaanIPX.VisibilityoftheIPXwaslimitedtothe
borderelementsi.e.IBCF/TrGWandDRA.DIAMETER,SIPandRTPtrafficwassuccessfullyrouted
betweenthehostsitesovertheIPX.
VoLTE was also demonstrated for interconnect via an IPX network with the SIP/RTP traversing the
IBCF/TrGWineachsiteandtheIPXGateway.
ThirdpartyregistrationofASswasdemonstrated.
MMTELServiceconfigurationandusagewasdemonstratedforVoLTEcalls.
Transcoding,transratingandDTMFdigitcollectionweredemonstratedviaanASandMRF.
RCS FT(FileTransfer) andRCS Chat were successfully demonstrated.However, these testcases did
notuseadedicatedbearerduetoissuesencounteredonRxbyaPCSCF.
RoamingwaslimitedtothetestingofSlovenianUEsroamingintheBeijingsite.Thiswasduetothe
availabilityofappropriateSIMcardsintheSintesiosite.WhilsttherewereHSSconfigurationissues
encountered during the attachment phase, the relevant S6a DIAMETER messages were correctly
routedfromtheCMCCMMEvialocalDRAviaIPXDRAtotheSintesioDRAandontotheSintesioHSS.
GTPwasstablewithnoissuesencountered.
The utilisation of Diameter Routing Agents provided optimisation of diameter routing within each
corenetwork/siteandacrosstheIPXbetweenthetwosites.WhilstmostDRAclientssupportedSCTP,
someonlysupportedTCPinwhichcasetheDRAprovidedthenecessaryinterworking.Whilstsome
implementationswereencounteredthatwerenotcompletelystandardscompliant,theDRAwasable
tomodify/deleteAVPstoenableinteroperability inmostcases.ThenetresultwasthatDIAMETER
wasgenerallystableandcausedmuchfewerproblemsthan hadbeen thecaseintheVoLTEIOTin
2011.
Interaction with the PCC/EPC was successfully demonstrated both for application binding to the
defaultbeareronIMSregistrationandforthecreationofdedicatedbearers.Dedicatedbearerswere
createdwiththeappropriateQCIvalueforvoiceandvideotelephonysessions.
Theapproachofdefiningstableconfigurationsandlimitingtestingtotypicaldeploymentgroupingsof
single vendor network nodes (e.g. single vendor EPC), resulted in configuration problems being
minimized.Inanycase,suchissuesarenotseenasaproblemfornetworkdeployments.
VoLTEsoftclientsinterworkedwithanumberof3rdpartyLTEdatadongles.
TheENUMServerwasconfiguredtosupporttheallocatedMSISDNsusedintheeventbutnoexternal
ENUMqueriesweregeneratedbyIBCFsorIPX.
TheShinterfacewasnotsupportedbyallASs.
Whilst the use of remotely located equipment facilitated participation, there was an impact on
sessionsetuptimesandmediaqualityduetotheincreasedlatencyinthetestnetwork.
AsintheVoLTEIOTeventin2011,thevastmajorityofimplementationsinthiseventwerebasedon
3GPPRelease8.

Page 25

RCS/VoLTEinaSingle/HomeNetwork:
In this scenario, intranetwork testing utilised a single RCS VoLTE architecture created using
components from different vendors. Testing included LTE attachment and detachment from the
network, SIP registration/deregistration (to/from IMS), SIP voice session establishment, SIP multi
media session establishment, SIP session teardown, MMTel Service Configuration, MMTel Service
usage and RCS services (both standalone and associated with a voice call) as specified by GSMA
IR.90,IR.92,IR.94andRCSservicesandclientspecification.

This test scenario demonstrated that VoLTE / Video Telephony calls and supplementary services,
basedonGSMAIR.92andIR.94,areaviablesolutionforprovidingvoice/videoservicesforLTEaccess.
Multivendor interoperability of UE, eNodeB, EPC, IMS Core, AS, DRA and PCC was demonstrated.
DedicatedbearerswithappropriateQCIweresetupforvoiceandvideotelephonycalls.
RCSFileTransferandRCSChatwerealsodemonstratedalthoughwithnodedicatedbearer.Thelack
ofadedicatedbearerwasduetoanRxissueononeofthePCSCFs.
MMTELserviceswereconfiguredandused.SomeoftheASsdidnotsupporttheShinterface.
Transcoding, transrating and DTMF collection was demonstrated via an AS and MRF. The DTMF
collection was used to enable authentication of a priority call attempt and to set the SIP Resource
PriorityHeader(RPH).
IMS Soft Clients interworked successfully with 3rd party LTE data dongles for LTE Attach and
additionallywiththeIMSCoreNetworkandMMTelAStoprovideIMSservicestotheenduser.
TheuseofaDRAsimplifiedDiameterroutingwithinthePLMNandreducedthenumberofrequired
connections. DRA's were also shown to provide interworking between different transport layer
protocols (i.e. SCTP to TCP)and also to be able to act as DIAMETER firewalls. Overall, DIAMETER
wasstableandcausedveryfewissues.
In some cases, SIP fragmentation issues were encountered when the MTU exceeded 1500 bytes.
ThesewereresolvedbyacombinationofreducingtheofferedcodecsformtheUEand/oruseofTCP
insteadofUDPtransport.
Issueswith3rdpartyregistrationofASswereencounteredduetoIFCs,butthesewereallresolved.
Subsequently,therewereissuesencounteredontheSUB/NOTIFYexchangefortheregistrationevent
packagebutthesewerealsosubsequentlyresolved.
SIPsyntaxerrorswereencounteredonsomeimplementationsforcertainSIPheaders.Relatedtothis,
itwasnotedthatdifferentimplementationsbehaveddifferentlyonreceiptofsuchsyntaxerrorsi.e.
somewererelativelytolerantinsomecases.
AppendixAprovidesmoredetailsonthetestresults.
Roaming&Interconnect:
The Roaming test scenario represents the test architecture where two subscribers of the same
Operator,performanendtoendcallwhilstonesubscriberisintheHPLMNandtheotherisroaming
inaVPLMN.Theroamingsubscriberattachesinthevisitednetworkwherelocalbreakoutisapplied,a
VisitedPCSCFandhomeIMSservicesasdefinedinGSMAIR.65andIR.88.
The Interconnect test scenario is where two subscribers, of different operators, perform an end to
endcallwhilstintheirrespectivePLMN'sasdefinedinGSMAIR.65.

Page 26

Roaming
Thistestscenariowasdesignedasanintersitetestwiththesubscriberroamingina'visitednetwork'.
TheLTEUE,eNodeB,MME,SGW,PGWandVPCRFwerephysicallyinthevisitednetworkwhilstthe
HPCRFandHSSwerephysicallylocatedintheHomeNetwork.WhilsttheIMSCorewasconfiguredin
thehomenetwork,thePCSCFwasconfiguredintheVisitedNetwork.Thisroamingmodelalignswith
GSMAspecificationsIR.65andIR.88.TwovariantsoftheRoamingscenarioweretestedtoreflecttest
planssourcedfromMSF&ETSIbothvariantsbeingequallyvalid.
ThefocusofthesetestswastoverifytheinterfacesbetweentheHPLMNandVPLMNrequiredfor
roaming with VoLTE/RCS. Specifically the utilisation of a DRA for routing Diameter messages
betweentheMMEinthevisitednetworkandtheHSSinthehomenetworkwithS6aandbetweenthe
visited PCRF to home PCRF interaction across the S9 interface both via IPX. Additional roaming
aspectsarethePCCinteractioninthevisitednetwork(RxandGxinterfaces)andtheSIPinterconnect
betweenthePCSCFinthevisitednetworktotheSessionBorderControllerinthehomenetwork(via
IPX).
ThisscenariotestsLTEattachmentanddetachmentofthevisitingUEaswellasIMSregistration,IMS
session establishment & teardown MMTel Service Configuration, MMTel Service usage and RCS
service usage; as specified in GSMA IR.90, IR.92, IR.94, IR.65, IR.88 and RCS services and client
specification.
DuetoalimitationofSIMcards,roamingwasonlyabletobetestedinonedirection,namelyfora
Slovenian UE roaming in the Beijing lab. HSS configuration issues were encountered during the
attachment phase, although the relevant S6a DIAMETER messages were correctly routed from the
CMCCMMEvialocalDRAviaIPXDRAtotheSintesioDRAandontotheSintesioHSS.Unfortunately,
thisissuewasunabletoberesolvedinthetimeavailable.Inthemeantime,asimulatorwasalsoused
totesttheroutingofSIPRegistermessagesfromtheCMCClaboverIPXtotheIMSCoreandHSSin
Sintesio.Onceagain,theunderlyinginfrastructuresuccessfullydeliveredthemessagebutissueswere
encounteredwiththeauthenticationwhichwerenotresolvedduringtheevent.
Insummary,whilsttheroamingscenario didnotresultinasuccessfulattachmentandregistration,
thesewereduetoHSSconfigurationissues.Onthepositiveside,theunderlyingRCSVoLTEroaming
architecturewasprovidedbyamultivendorconfigurationandenabledDIAMETERandSIPmessages
to be passed from then VPLMN to the HPLMN via IPX. Therefore, the RCS VoLTE roaming
architectureisaviablesolutionforprovidingvoice,multimediaandRCSservicesforLTEaccessfora
userwhilstinaroamingnetwork.
AppendixAprovidesmoredetailsonthetestresults.
Interconnect
ThistestscenariotestsIMSsessionestablishment(voice&multimedia),IMSsessionteardownplus
MMTelServiceConfiguration,MMTelServiceusageandRCSServiceusageforLTEUEsregisteredin
theirrespectivehomePLMNsandinteractingacrosstheIci/Izireferencepoints.Complianceagainst
GSMAPRDIR.65andRCSservicesandclientspecificationistested.
This test scenario demonstrated that theVoLTE architecture is a viable solution for providing voice
and RCS services for LTE access between users on different PLMN's. The setting consisted of
equipment from different infrastructure vendors in each site being interconnected via IPX over the
applicable3GPPstandardizedinterfaces.

Page 27

The two host sites were successfully interconnected via an IPX and voice calls were successfully
establishedwithSIP/RTPmessagestraversingtheIBCF/TrGWineachsiteandtheintermediateIPX
Gateway.MMTelservicesandvideotelephonywerenottestedduetoalackoftime.
RCStestswerenotabletoberunduetotherebeingnoRCSclientintheBeijingsite.
AppendixAprovidesmoredetailsonthetestresults.

FUTUREWORK
InteresthasbeenexpressedoncontinuingworkinthisareabywayofafutureRCSVoLTErelated
InteroperabilityEvent.
Thefocusofsuchaneventmayinitiallybeonthetestcasesthatwerenotabletobeexecutedin
thisevent.Theseareasfollows:

RCSPresence

ENUMInteraction

NonLTEAccessviaS4SGSN

NonLTEAccessvialegacySGSN

2G/3GPS(PacketSwitched)handoverviaS4SGSN

2G/3GPS(PacketSwitched)handovervialegacySGSN

Priority(MPS)CallHandover(LTE/IMS<>OtherRAN/CS)

Inaddition,thereareadditionalpotentialfeaturesthatcouldalsobepartofafutureIOTevent:

FurthertestingofRCSservicesalignedwiththeevolutionoftheRCSspecifications.

RCSforenterprisenetworks,

Quality measurements (MOS score, jitter, latency etc) for voice, video and real time
services,

SRVCC,

EmergencyCall,

LTEWiFiinterworking.

The timeframe of any future IOT event would be dependent on availability of UEs and network
nodes supporting the required functionality as well as Service Provider interest in seeing such
functionalitytestedinamultivendorenvironment.

Page 28

APPENDIXA:THETESTSCENARIOS
This appendix provides a detailed description of each of the test scenarios and presents the test
resultsonaperlab,perscenariobasis.Whenpresentingtheresults,thefollowingcategorytypesare
definedtodefinetheresultsofthetestcasesintheRCSVoLTEInteroperabilityEvent:

PassedTestcasewasscheduledtoberunandPassedthecriteriadefinedwithintheTest
Plan

Failed Test case was scheduled to be run and Failed the criteria defined within the Test
Plan

Not Run Test Case was scheduled to be run, however due to lack of time this was not
possible

N/ATestCasewasidentifiedtobenotapplicabletobescheduled(e.g.duplicationoftest
casefunctionality)

RestrictedTestCasewasscheduledtoberun,howeverduetoissueswithconfigurationor
otherlimitations(UEandequipmentrestrictions)itwasnotpossible.

RCSVOLTEINAHOME/SINGLENETWORK
Thistestscenariodemonstratedtheattachmentanddetachmentfromthenetwork,IPCANsession
establishment,SIPregistration(toIMS),SIPvoicesessionestablishment/termination,SIPMultiMedia
sessionestablishment/teardown,invocation/configurationofMMTelServicesandRCSServices(both
standaloneandincombinationwithavoicesession)..

Figure9Scenario1RCSVoLTEinaHome/SingleNetwork.

Page 29

NOTE: The Gm interface (UE to PCSCF) is a focus for testing although not shown in the above
figure.
ThenetworkarchitectureforVoLTEBasicInteroperabilityisshowninFigure5above.Theinterfaces
forwhichinteroperabilityweretestedareshowninred(i.e.S1MME,S1U,S5,S11,S6a,Gx,Rx,Gm,
Mw,ISC,andUt).
TestObjectives
1.

To demonstrate the ability to perform UE Attach (IPCAN Session Establishment) and UE


Detach (IPCAN Session Tear Down). This covers interworking between eNodeBEPC,
between the EPC elements, MMEHSS and PGWPCRF for creation of a default bearer for
IMSSignalling.

2.

TodemonstratetheabilitytoperformUEIMSRegistrationasacommonbasisforaccessing
IMSbasedvoice/multimedia/RCSservices.

3.

TodemonstrateIMSVoiceSessionEstablishment,IMSVoiceSessionTerminationasdefined
by GSMA IR.92. This covers interworking between UE, IMS Core Network, MMTel AS and
PCCforcreationofadedicatedbearerforvoice.

4.

To demonstrate IMS multimedia (voice/video) Session Establishment, IMS multimedia


SessionTerminationasdefinedbyGSMAIR.94.ThiscoversinterworkingbetweenUE,IMS
CoreNetwork,MMTelASandPCCforcreationofdedicatedbearersforvoice/video.

5.

To demonstrate the ability to perform MMTel Service Configuration over the Ut reference
pointforanattachedUE.

6.

To demonstrate interworking between the UE, IMS Core and IMSAS for MMTel Service
usageasdefinedbyGSMAIR.92.

7.

TodemonstrateinterworkingbetweentheUE,IMSCoreandRCSASsforRCSServiceusage
as defined by GSMA IR.90, including interaction with the PCC for creation of dedicated
bearersforRCSservices(e.g.filetransfer).

8.

To demonstrate the ability to provide an optimised solution for routing of Diameter


messageswithinthecorenetworkutilisingtheDRAfunctionality.

TestResultsandObservations
TheScenario1testplanincluded4subscenariosnamely:

1aAttachment&IMSRegistration,

1bIMSvoicesessionestablishment/teardownandconfiguration/usageofMMTELservices,

1cRCSServices(bothstandaloneandincombinationwithavoicesession).

1d IMS multimedia session establishment/teardown and configuration/usage of MMTEL


services,

There were a total of 102 defined test cases across the 4 subscenarios. Test case results were as
follows:

Page 30

Oftheteststhatwererun,theyweresometimesrunmultipletimes(e.g.paralleltestingorchangeof
configuration).ThefollowingtablesummarizestheScenario1testcoverage.
Scen.
1a

1b

1c

1d

NoRun

Passed

N/A

Failed

Restricted

19

14

38

12

53

10

Total

Lab

Kranj
Beijing

28

Kranj
Beijing

53

Kranj
Beijing

15

Kranj
Beijing

Table 3. RCS/VoLTE Scenario 1 Test Results


TheNoruntestcasesweremostlyduetolackoftimetoexecutethosetestcases.
The Restricted test cases were due to missing functionality that prevented the test case to be
executedandincludeacombinationoflackofequipment(e.g.PresenceServer),issueswithhandling
SIPOPTIONSinthecoreandthematurityoftheRCSclient.
TheFailedtestcaseswerelargelydueto:

FailureofanIMScoretohandleSIPOPTIONSmessageforRCSCapabilityExchange,

AHSSconfigurationissueforCallForwardingNotLoggedIn,

AnIMScoreissueresultinginatriggeringresponse(408,500,503)notbeingreceivedbythe
ASforCallForwardingNotReachableService.

TheScenario1testresultsdemonstratedthat:

Multivendor interoperability of UE, eNodeB, EPC, IMS/MMTEL, RCS AS, DRA and PCC
technology.

VoLTE calls and supplementary services, based on GSMA IR.92, are a viable solution for
providingvoiceservicesforLTEaccess.

Multimedia (voice/video) calls, based on GSMA IR.94, were demonstrated. This included
voice & video bearers established at the start of the session as well as the addition and
deletionofavideobearerto/fromanexistingsession.AnumberofMMTELserviceswere
alsodemonstratedformultimediacalls.

DedicatedbearerswithappropriateQCI(1forvoice,2forvideotelephony)wereestablished.

ApplicationbindingtothedefaultbearerwasdemonstratedatIMSregistration.

Ut configuration of a number of MMTEL services was demonstrated between the UE and


HSS.

Page 31

RCSFTandRCSChatweredemonstrated.However,adedicatedbearerwasnotusedforthe
MSRP/TCPsessionsastherewasanissuewiththePCSCFforthosetests(seebelow).

Transcoding, transrating and DTMF collection was demonstrated via an AS and MRF. The
DTMFcollectionwasusedtoenableauthenticationofaprioritycallattemptandtosetthe
SIPResourcePriorityHeader(RPH).

The IMS Soft Clients interworked successfully with the LTE data dongle for LTE Attach and
additionally with the IMS Core Network and MMTel AS to provide IMS services to the end
user.

GTPprotocolprovedtobematureandstablewithnoissuesidentified.

Diameter routing within the PLMN was greatly simplified by utilizing Diameter Routing
Agents. DRA's were also shown to provide interworking between different transport layer
protocols and to be able to act as a DIAMETER firewall to facilitate interoperability (e.g.
changingordeletingAVPs).DIAMETERwasgenerallyverystable.

SeveralissueswereencounteredduringthetestexecutionofScenario1:

PCCIssues

OnRxinterfaces,onePCSCFwasnotcompliant.

SomeAVPswereincorrectlypresentorincorrectlytaggedasmandatory.TheDRAlargely
fixedtheseissuesbyactingasaDIAMETERfirewall.

IMSIssues

The Sh interface was not supported on all implementations of Application Servers.


Instead,theuserserviceinformationwassetup/storedlocallyontheAS.

TheUtinterfacewasnotsupportedonallMMTelAS'sinordertoprovidesupplementary
serviceconfiguration.NotethatthisismandatorywithinGSMAPRDIR.92.

Issueswereencounteredon3rdPartyRegistrationrequestsduetotheIFCsbeingpassed
downfromtheHSS.Thesewereresolvedduringtheevent.

RCS Capability Exchange failed due to an IMS core not transiting the SIP OPTIONs
message.Thiswasfixedduringtheeventbuttimeranoutbeforeitcouldberetested.

SIPsyntaxerrors on some headers were encountered and it was also noted that some
implementationsweremoretolerantthanothersoftheseerrors.

IssueswithparsingSIPURIswasobservedonsomeASs.

Different PCSCFs were observed to have different TFT (Traffic Flow Template) filter
implementationsintermsofstrict/lenientdefinitionofthesourcehost/port.

TransportIssues

SCTP was not supported all DRA clients. Instead, TCP was the transport protocol
supported. The DRA provided transport layer interworking. It is noted that 3GPP
DiameterinterfacesarebasedonSCTPforthetransportprotocol.

FragmentationissueswereseenwhentheMTUsizeexceededthatspecifiedby3GPPfor
e.g.1500octetsinthetransportnetwork.ThiswassolvedbyreducingthesizeoftheSIP
INVITE'sbye.g.reducingthenumberofcodecsbeingofferedand(asamorepermanent
solution)usingTCPinplaceofUDPtransport.

Page 32

There was some difficultly experienced when reconfiguring the network components for
testing the differentmultivendor configurations. However,this was minimized duringthe
eventduetoconfigurationsbeingmostlystableandunchangedanditisnotseenasamajor
issuefornetworkdeployments.

RCS/VOLTEFORROAMING&INTERCONNECT
Thistestscenariodemonstratedthefollowing:
ForRoaming:

IPCANsessionestablishment/disestablishment,

SIPregistration(toIMS)whenroaming,

SIPvoicesessionestablishment/terminationandconfiguration/usageofMMTelServices,

RCSServices(bothstandaloneandincombinationwithavoicesession),and

SIP MultiMedia session establishment/teardown and configuration/usage of MMTel


Services.

ForInterconnect:

SIPvoicesessionestablishment/terminationandusageofMMTelServices,

RCSServices(bothstandaloneandincombinationwithavoicesession),and

SIPMultiMediasessionestablishment/teardownandusageofMMTelServices.

As in Scenario 1, this scenario was broken down into four similar subscenarios .In addition, 3
differentconfigurationsweredefinedofwhich2wererelatedtoroamingandoneforinterconnect.
The reason for having 2 different roaming configurations was related to the roaming test plan
documents that were written by MSF and ETSI respectively which were equally valid but covered
differentcallconfigurations.
Furtherdetailsareprovidedbelow.

Page 33

Roaming

FIGURE 10. SCENARIO 2 - CONFIG I - ROAMING (SAME HOME PLMN)

FIGURE 11 SCENARIO 2 - CONFIG II - ROAMING (DIFFERENT HOME PLMNS)

NOTE: The Gm interface (UE to PCSCF) is a focus for testing although not shown in the above
figures.
The network architecture for the Roaming test scenario is shown in Figures 10 and 11 above. The
interfacesforwhichinteroperabilityweretestedareshowninred(i.e.S6a,S9,Rx,Gx,Mw,Gm,Ut
andISC).
Objectives

Page 34

1.

TodemonstrateroamingwiththeUEinaVisitedNetwork(i.e.eNodeB,MME,SGW,PGW,
VPCRF and PCSCF in the VPLMN and the HSS, HPCRF and IMS core in the HPLMN).
Specifically,theabilitytoperforminterworkingbetweentheMMEandPCRFintheVPLMN
with the HSSandPCRF inthe HPLMN respectively,and thePCRF and PCSCF in thevisited
network by performing UE Attach (IPCAN Session Establishment) and UE Detach (IPCAN
Session Tear Down) to validate the Diameter roaming interfaces and DRA functionality for
S6aandS9asdefinedbyGSMAIR.88.

2.

TodemonstrateUEIMSRegistrationtothehomePLMNwhilstroaminginavisitednetwork.

3.

TodemonstrateIMSVoiceSessionEstablishment,IMSVoiceSessionTerminationasdefined
by GSMA IR.92 whilst roaming in a visited network, including interaction with the PCC for
creationofadedicatedbearerforvoice.

4.

To demonstrate IMS multimedia (voice/video) Session Establishment, IMS multimedia


SessionTerminationasdefinedbyGSMAIR.94whilstroaminginavisitednetwork,including
interactionwiththePCCforcreationofdedicatedbearersforvoice/video.

5.

TodemonstratestheabilitytoperformMMTelServiceConfigurationovertheUtreference
pointforanattachedUE,whilstroaminginavisitednetwork..

6.

To demonstrate interworking between the UE, IMS Core and IMSAS for MMTel Service
usageasdefinedbyGSMAIR.92,whilstroaminginavisitednetwork.

7.

TodemonstrateinterworkingbetweentheUE,IMSCoreandRCSASsforRCSServiceusage
asdefinedbyGSMAIR.90,whilstroaminginavisitednetwork,includinginteractionwiththe
PCCforcreationofdedicatedbearersforRCSservices(e.g.filetransfer).

TestingResultsandObservations
TheRoamingtestplanincluded4subscenarios(forConfigI&II)namely:

2aAttachment&IMSRegistration,

2bIMSvoicesessionestablishment/teardownandconfiguration/usageofMMTELservices,

2cRCSServices(bothstandaloneandincombinationwithavoicesession).

2d IMS multimedia session establishment/teardown and configuration/usage of MMTEL


services,

DuetoSIMcardissues,itwasonlypossibletotestroamingfromtheBeijinglab(i.e.SlovenianSIMin
China).
There were a total of 85 defined test cases across the 4 subscenarios. Test case coverage was as
follows:
Scen. NoRun

Passed

N/A

Failed

Restricted

Total

Lab

2a

Both

2b

22

22

Both

2c

41

41

Both

Page 35

2d

14

14

Both

Table 4. RCS/VoLTE Scenario 2 Roaming Test Results


TheNoruntestcaseswereduetothefailuretoperformanetworkattachandsubsequentrunning
outoftimewhichthenrestrictedfurthertestcases.
TheRestrictedtestcaseswereessentiallyduetotheattachmentfailurealthoughtherewasalso
somemissingfunctionalitythatwouldhavefurtherrestrictedsometestsintheeventofasuccessful
attachment(e.g.PresenceServer).
TheFailedtestcasewascausedbyaconfigurationissueintheHSS.WhentheroamingUEattached
in the visited network, the AIR/AIA interchange over S6a worked but the subsequent ULR/ULA
interchangefailed.
Roamingdemonstrated:

Despitetheattachmentfailure,theS6aDIAMETERmessagesweresuccessfullyroutedfrom
the MME in the VPLMN via the DRA in Beijing, the DRA in the IPX network, the DRA in
SintesioandontotheHSSintheHPLMN.Thisshowedthattheunderlyingarchitectureand
infrastructurewasabletosupporttheroutingofDIAMETERmessagesbetweenthe2PLMNs.
ItisalsonotedthattheIPXconfigurationwasdoneinamatterofdaysduetothatelement
joiningtheeventduringthesecondweek.

IssueswereencounteredduringthetestexecutionofRoaming:

ConfigurationissueontheHSSwhichcausetheULR/ULAexchangetofail.

Whilsttopologyhidingisnotamandatoryfunctionality,itwasalsotestedaspartoftheIOT
eventfortheroamingscenario.Diameterroutingwasperformedonahopbyhopbasis
betweenDEAsontheedgeoftheVisitedandHomeNetworks.Itshouldbenotedthatthe
OriginHostandtheOriginRealmoftheMMEinthevisitednetworkwerestoredintheHSS,
toenablemessagesinitiatedbytheHSStoberoutedtothecorrectMMEinthevisited
network.Iffulltopologyhidingwasimplemented(OriginHostmaskedacrossthe
interconnectbythevisitedDEA),thevisitedDEAwouldberequiredtoperformamappingof
thereceivedUserNametotherelevantMMEinordertobeabletoroutetheincoming
DiameterrequestfromtheHSS.Thismappingisseenasanintensivefunctionalitythatisnot
recommended,furthermoreadditionalsecuritycanbeprovidedutilisingIPSecis
recommended..)

Page 36

Interconnect

IMS Core
MMTel / RCS
Application
Servers

Ut

Mr

MRF

Sh
I
S
C

Cx

HSS

Cx
Sh

P-CSCF

Mw

Mr

I/S-CSCF

Mx

IBCF/TrGW

Rx

PLMN-A

S6a
DRA
S6a

Rx

Ici/Izi

ENUM

Gx
PCRF
Gx

MME

ENUM
Server

IPX
ENUM

S1-MME

UE

SecGW

LTE-Uu

IMS UA

S11
S1-U

PLMN-A

S-GW

eNodeB

S5

P-GW

ENUM

SGi

PLMN-B

Ici/Izi

IMS Core
MMTel / RCS
Application
Servers

Ut

Mr

PLMN-B

MRF

Sh
I
S
C

Cx

HSS

Cx
Sh

P-CSCF

Mw

I/S-CSCF

Mr

Mx

IBCF/TrGW

Rx
S6a
DRA
S6a

Rx
Gx
PCRF
Gx

MME
S1-MME

UE

SecGW

LTE-Uu

IMS UA

S11
S1-U

eNodeB

S-GW

S5

P-GW

SGi

Figure12.Scenario2ConfigIII(Interconnect)
NOTE: The Gm interface (UE to PCSCF) is a focus for testing although not shown in the above
figure.
The network architecture for Interconnect is shown in Figure 11 above. The interfaces for which
interoperabilityweretestedareshowninred(i.e.Mw,Mx,Gm,Ut,ISCandIci/Izi).
Objectives
1.

TodemonstrateinterconnectbetweentwoUE'sregisteredintheirrespectivehomePLMN's.
Specifically,theabilitytoperforminterworkingbetweentheIBCF/TrGW'sintherespective
PLMN'svalidatingtheIci/IziinterfacesandGSMAIR.65.

2.

To demonstrate IMS Voice Session Establishment and IMS Voice Session Termination as
defined by GSMA IR.92 and IR.65, with voice sessions established with a subscriber in a
differentPLMN.

3.

TodemonstrateIMSMultimedia(voice/video)SessionEstablishmentandIMSMultimedia
Session Termination as defined by GSMA IR.94 and IR.65, with multimedia sessions
establishedwithasubscriberinadifferentPLMN.

Page 37

4.

TodemonstratetheusageofMMTelServicesasdefinedbyGSMAIR.92,acrossanetwork
tonetworkinterconnectvalidatingIci/Izi.

5.

TodemonstratetheusageofRCSServicesasdefinedbyGSMAIR.90,acrossanetworkto
networkinterconnectvalidatingIci/Izi.

TestingResultsandObservations
TheInterconnecttestplanincluded3subscenarios(forConfigIII)namely:

2bIMSvoicesessionestablishment/teardownandconfiguration/usageofMMTELservices,

2cRCSServices(bothstandaloneandincombinationwithavoicesession).

2d IMS multimedia session establishment/teardown and configuration/usage of MMTEL


services,

There were a total of 64 defined test cases across the 3 subscenarios. Test case coverage was as
follows:
Scen. NoRun

Passed

N/A

Failed

Restricted

Total

Lab

2b

11

Both

2c

41

41

Both

2d

11

12

Both

Table5. RCS/VoLTE Scenario 2 Interconnect Test Results


TheNoruntestcaseswerelargelyduetolackoftimetoexecutethosetestcases.
TheRestrictedtestcaseswereduetomissingfunctionalitythatdidnotenablethetestcasetobe
executed(lackofequipmentand/ormissingfunctionalityonanAS).
Interconnectdemonstrated:

VoLTEcalls,basedonGSMAIR.92andIR.65,areaviablesolutionforprovidingvoiceservices
forLTEaccessbetweenMobileNetworkOperators.

The two host sites were successfully connected via an IPX with SIP/RTP traversing the
IBCF/TrGWineachsiteandtheintermediateIPXGateway.

MultivendorinteroperabilityofIBCF/TrGW'sandIPXwasachieved.Itisalsonotedthatthe
IPXconfigurationwasdoneinamatterofdaysduetothatelementjoiningtheeventduring
thesecondweek.

IssueswereencounteredduringthetestexecutionofInterconnect:

RCStestswerenotrunduetotherebeingnoRCSclientintheBeijinglab.

MMTelserviceswerenottestedduetoalackoftime.

Multimediacallswerenottestedduetoalackoftime.

TheexternalENUMServerwasnotusedbyanyoftheIBCFsnorIPX.

Page 38

APPENDIXB:ADDITIONALTESTING
Thisappendixprovidesdetailsofadditionaltestingthatwascarriedout(inadditiontothatdescribed
inAppendixA)intheRCSVoLTEInteroperabilityEvent2012.
InterRATCallTransfer
ThistestwasrelatedtotheoriginalScenario5bwhichdemonstratedinterRAThandoverofapriority
callbetweenLTEandGERAN/UTRANwithalegacyMSC.Thearchitectureforthistestcaseisshownin
figure13below:

IMS Core

Sh

MSC Server
ISUP
(RAN)

MSC Server
(VCC)

Sh

MMTel AS

Mw

Mr

ISC

GERAN UE

ISC

Cx

GERAN
Sv

P-CSCF
(ATCF/ATGW )

HSS
S6a

Mw

I/S-CSCF

Mr

MRF

Simulator

Rx

S1-MME

MME

PCRF

S11

Gx

UE

VCC AS

ISUP/SIP

IMS UA

Gm

WiFi UE

LTE-Uu
S-GW

S5

S1-U

P-GW /
GGSN

SGi

eNodeB

FIGURE13INTERRATCALLTRANSFER(LTETOGERAN)

In the event proper, there was no MME supporting the required Sv reference point. Instead, a
simulatorwasused.TheremainingrequiredelementsforSRVCCweresuppliedasshownintable6
below.

ElementType

Vendor

MSCServer(RAN)

Telekom
Slovenia

GERAN

Telekom
Slovenia

MSCServer(VCC)

Iskratel

ATCF/ATGW

Iskratel

VCCAS

Iskratel

I/SCSCF

Iskratel

Table 6. Inter-RAT Call Transfer Related Equipment

Page 39

Initially,acallwasestablishedbetweenaLTEUEandaWiFiUE.ThesimulatortheninvokedtheSv
referencepointandthecallwastransferredtoarealmobilephoneattachedtotheMSCServerin
theCSdomainandviaGERAN.ThefinalconnectionwasbetweentheWiFiUEandtheCSattached
mobilephone,thusdemonstratingtransferofavoicecallbetweenLTEandGERANRATs.
ConformanceCriteriaChecking
This was a background activity during the event to perform SIP / DIAMETER conformance criteria
checkingontracefilescapturedwhilefollowingtheETSITSduringtheRCSVoLTEtesting.
ThisactivitybuildsontheworkofETSISTF450tovalidateETSIConformanceTestSuitesTS1015803
(Rx) & TS 101 6013 (Gx). The STF developed tools to enable automatic conformance checking of
tracestakenduringtheIOT.
As a further activity, tools previously developed by other STFs were also used to enable automatic
conformancecheckingofSIPmessages.
TwoSTFexpertswereinattendanceattheeventtocheckconformanceon:

SIP(Mw,Ici,ISC)fortestcasesinTS186011

DIAMETER(Rx)fortestcasesinTS103029

Tracecapturesofthemanualinteroperabilitytestexecutionswererecordedindependently.Forthe
offlineanalysisofthesetracecapturestwoconformancecriteriaverificationtesttoolinstanceswere
usedinparallel.EachtesttoolinstancewasfirstconfiguredwithIPaddressandportinformationofall
participatingnetworkequipmentanduserequipment.Thenrecordedtracecaptureswereanalyzed
byexecutingthecorrespondingtestcase.Thetracewasacceptedincasethefinalverdictwasapass.
Inthecaseofafailverdict,eachtestexecutionwascheckedinordertodetermineifthereasonfor
thefailurewasindeedcausedbynonconformantbehaviourorifitwascausedbyaprobleminthe
testsystem.ThetestengineersusedthesameTTCN3testsuitebutexecuted itwithtwodifferent
commercialTTCN3tools.
Here,thePassverdicthasbeengivenincasesthattheanalysisofthetestexecutiontraceshows
that all components participating in a test fulfilled all of the verdict criteria specified in the test
specification for that test. The Fail verdict has been given in cases that the analysis of the test
executiontraceshowthatatleastoneentityparticipatinginatestviolatedoneormoreoftheverdict
criteria specified in the test specification for that test. The Inconclusive verdict was assigned in
cases were some nonconformant condition had been observed which was either not part of the
verdict criteria, e.g., the test never got to through its preamble, or could not be performed in its
totality, e.g., a user equipment was not able to add and drop media streams to an existing SIP
dialogue.Soinbothcasestheverdictcriteriacannotbecheckedthereforethetestisassignedan
Inconclusiveverdict.
TheresultsshowedseveralsyntaxerrorsinSIPheadersexchangedbetweendifferentequipmentsuch
as missing < and > characters in PAssociatedURI headers and the use of superfluous space
charactersattheendofSIPmessagelines.Thoseresultswerereportedtothevendorsinvolved.
Diametersignallingmessagesturnedouttobesyntacticallycorrectandnocodingerrorscausedthe
conformancereviewsoftwaretoassignFailverdictsbasedontheanalysisoftheexchangedDiameter
messages.OnlytheDiameterproceduresthatarerelevanttotheinteroperabilitytestscoveringUE
attachment,deattachment,registrationandderegistrationwereconsideredastheETSItest
specificationTS103029focusesonthoseprocedures.

Page 40

APPENDIXC:INTERFACEREFERENCES
LTEUu(UEeNodeB)
3GPPTS36.300(EUTRANprotocol)
S1MME(UEMME)
3GPPTS24.301(NonAccessStratum)
S1AP(eNodeBMME)
3GPPTS36.413(S1ApplicationProtocol)
S1U(eNodeBSGW)
3GPPTS29.281(GTPv1U)
X2(eNodeBeNodeB)
Signaling3GPPTS36.423(X2ApplicationProtocol).
UserPlane3GPPTS29.281(GTPv1U)
S3(S4SGSNMME)
3GPPTS29.274(GTPv2C)
S4(S4SGSNSGW)
ControlPlane3GPPTS29.274(GTPv2C).
UserPlane3GPPTS29.281(GTPv1U).
S5(SGWPGW)
UserPlane3GPPTS29.281(GTPv1U)
ControlPlane3GPPTS29.274(GTPv2C)
S6a(HSSMME)
3GPPTS29.272(Diameter)
S6b(PGW3GPPAAA)
3GPPTS29.273(Diameter)
S6d(HSSS4SGSN)
3GPPTS29.272(Diameter)
S8(SGWPGW)
UserPlane3GPPTS29.281(GTPv1U)
ControlPlane3GPPTS29.274(GTPv2C)

Page 41

S9(PCRFPCRF)
3GPPTS29.215(Diameter).
S10(MMEMME)
3GPPTS29.274(GTPv2C).
S11(MMESGW)
3GPPTS29.274(GTPv2C)
S12(UTRANSGW)
3GPPTS29.281(GTPv1U,utilizedfordirecttunnelmodel).
Gx(PCRFPGW)
3GPPTS29.212(Diameter).
Rx(PCRFIPApplication[PCSCFforIMS])
3GPPTS29.214(Diameter).
Gr(SGSNHSS)
3GPPTS29.002(MAP)
Gn(SGSNMME/SGSNPGW)
ControlPlane3GPPTS29.060(GTPv1C)
UserPlane3GPPTS29.281(GTPv1U)
Gm(UEPCSCF)
3GPPTS24.229(IMSSIP)
Mw(xCSCFxCSCF)
3GPPTS24.229(IMSSIP)
Mx(xCSCFIBCF)
3GPPTS24.229(IMSSIP)
ISC(SCSCFAS)
3GPPTS24.229(IMSSIP)
Mr(CSCFMRF)
3GPPTS24.229(IMSSIP)
Mr(ASMRF)
3GPPTS24.229(IMSSIP)

Page 42

Cr(ASMRF)
3GPPTS24.229,24.147,27.247(IMSSIP)
Ut(UEAS)
3GPPTS24.623(XCAP)
SGi(EPCbasedPLMNandanotherpacketdatanetwork)
3GPPTS29.061(IP)
ENUM
IETFRFC6116(ENUM)
S102(MME1xCSIWS)
3GPP29.277(3GPP2A21)
Ici(IBCFIBCF)
3GPP29.165(IMSSIP)
Izi(TrGWTrGW)
3GPP29.165(RTP/MSRP)
Mb(MRFUE)
3GPP23.002,29.163(RTP)
Sv(MMEMSC)
3GPP29.280(GTPv2C)

Page 43

APPENDIXD:THEORGANISERS
AbouttheMSF
The MultiService Forum (www.msforum.org) is a global association of service providers, system
suppliers and test equipment vendors committed to developing and promoting openarchitecture,
multiservice Next Generation Networks. Founded in 1998, the MSF is an openmembership
organization comprised of the world's leading telecommunications companies. The MSF's activities
include developing Implementation Agreements, promoting worldwide compatibility and
interoperability of network elements, and encouraging input to appropriate national and
internationalstandardsbodies.
AboutGSMA
The GSMA represents the interests of mobile operators worldwide. Spanning more than 220
countries, the GSMA unites nearly 800 of the worlds mobile operators, as well as more than 200
companies in the broader mobile ecosystem, including handset makers, software companies,
equipment providers, Internet companies, and media and entertainment organizations. The GSMA
alsoproducesindustryleadingeventssuchastheMobileWorldCongressandMobileAsiaExpo.For
moreinformation,pleasevisittheGSMAcorporatewebsiteatwww.gsma.comorMobileWorldLive,
theonlineportalforthemobilecommunicationsindustry,atwww.mobileworldlive.com.
AboutETSI
ETSIproducesgloballyapplicablestandardsforInformationandCommunicationsTechnologies(ICT),
including fixed, mobile, radio, converged, aeronautical, broadcast and internet technologies and is
officially recognized by the European Union as a European Standards Organization. ETSI is an
independent,notforprofitassociationwhosemorethan700membercompaniesandorganizations,
drawn from 62 countries across 5 continents worldwide, determine its work programme and
participate directly in its work. For more information please visit: www.etsi.org ETSI Plugtests are
interoperability test events that cover a wide range of telecommunications, Internet, broadcasting
andmultimediaconvergingstandards.Formoreinformation,pleasevisit:www.etsi.org/plugtests

Page 44

APPENDIXE:THEHOSTS
AboutCMCC
China Mobile Communications Corporation (" China Mobile "), established on April 20, 2000, is a
GSM/TDSCDMA/TDLTEmobilecommunicationoperatorwiththeworld'slargestnetworkscaleand
almost 650 million customers. The business of China Mobile includes mobile voice, mobile data,
enterprise, multimedia services and Internet global interworking. In addition China Mobile also
providevariousvalueaddedservicessuchasfax,dataandIPtelephony.In2011,ChinaMobileranked
87onFortunemagazine'sworldtop500,withoutstandingbrand valueamongtheforefrontofthe
globaltelecombrands.Itwasalsolistedamongtheworld'stop50mostinnovativeenterprises.
Formoreinformation,pleasevisit:www.chainamobileltd.com.
AboutSintesio
Sintesio is an open, notforprofit foundation, cofounded by the European Telecommunications
Standards Institute (ETSI), Slovenian Institute for Standardization (SIST), and Iskratel, a Slovenian
telecommunicationvendor.TheaimoftheFoundationistopromoteopenstandards,interoperability
in multivendor/multioperator environments, to support standardization efforts and to facilitate
vendorscollaborationintheareaofNGNtelecommunicationtechnologiesandstandardization.The
Foundation set up the interoperability test lab, located in Kranj, Slovenia, with the purpose to test
andvalidateinteroperabilityofmultivendorICTproducts,aswellastovalidatethequalityofopen
ICT standards, especially in the NGN and IMS domain. For more information, please visit:
www.sintesio.org.
AboutTelekomSlovenia
TheTelekomSlovenijeGroupisSlovenia`sleadingandmostadvancedtelecommunicationsoperator
in all key segments of the welldeveloped and highly competitive Slovenian market, delivering a
comprehensiveportfoliooffixed,mobile,Internetandstateoftheartintegratedtelecommunication
solutions via its modern proprietary network. Beyond its clear number of presence in Slovenia,
Telekom Slovenije Group is present in several high growth markets in Southeast Europe, in
Macedonia, Bosnia and Herzegovina, Kosovo and Albania. The Groups acquisition of 50% stake in
Gibtelecom,Gibraltarsdominantfixed,mobileandInternetoperator,representsfurtherstepsinthe
strategy to extend Telekom Slovenijes geographic footprint into selected Southeast European and
Mediterraneanmarkets.

Page 45

APPENDIXF:THEPARTICIPANTS
ThisappendixprovidesabriefresumeoftheparticipantcompaniesintheLTEInteroperabilityEvent:

Aicent
Servingmorethanthreebillionmobileusersaroundtheworld,Aicent,Inc.isaleadingIPXproviderof
datanetworkservicesandsolutionsforglobalmobileoperators.Toenableinteroperabilitybetween
Aicentcustomersandothernetworks,Aicentoperatesoneoftheworld'slargestmobileIPXnetwork
exchanges connecting to over 200 operators, including nine of the worlds ten largest. Through
extensive peering arrangements and Diameter Routing Platforms located in NA, Europe, and Asia,
Aicentsnetworkreachesnearlyall3Gand4GLTEoperatorsaroundtheworld.Thecompany'sglobal
IPX network operates an integrated mobile messaging exchange, value added data roaming and
global reach infrastructure services, including the worlds first and largest multimedia messaging
exchange, designed to help carriers maximize revenue opportunities. For more information, visit
www.aicent.com.

AcmePacket
AcmePacket,theleaderinsessiondeliverynetworksolutions,enablesthetrusted,firstclassdelivery
ofnextgenerationvoice,video,dataandunifiedcommunicationsservicesandapplicationsacrossIP
networks. Our NetNet product family fulfills demanding security, service assurance and regulatory
requirements in service provider, enterprise and contact center networks. Based in Bedford,
Massachusetts,AcmePacketdesignsandmanufacturesitsproductsprimarilyintheUSA,sellingthem
through over 309 reseller partners worldwide. More than 1,850 customers in 109 countries have
deployedover20,000AcmePacketsystems,including89ofthetop100serviceprovidersand48of
theFortune100.
These solutions enable new services such as VoLTE, RCS and SIP trunking and reduce total cost of
ownership with simplified IMS, Diameter routing and SIP interconnects. Acme Packet experience,
expertise and solution portfolio enables service providers and enterprises to successfully transform
theirbusinessandsucceedintheallIPworld.
Formoreinformationvisitwww.acmepacket.com.

Cisco
TheNextGenerationofMobileVoiceandVideo
Mobileoperatorshavebegunmigratingtofourthgeneration(4G)architecturesbasedontheLong
TermEvolution(LTE)standard;includingtheEvolvedPacketCore(EPC)architecturedefinedbythe
3rdGenerationPartnershipProject(3GPP).TooffervoiceandvideooveranLTEstandardnetwork,
operatorsmustmigratefromcircuitswitchedvoicetopacketvoice.Thisrequiresanarchitectural
visionthatsupportsvoiceandshortmessageservice(SMS)usingtheexistingthirdgeneration(3G)
network,whileprovidingaclearpathtonetworksbasedonSessionInitiationProtocol(SIP).This
architectureenablesnewerservices,suchasoptimizedconversationalvideo,presence,andinstant
messaging.Cisco'sV2oLTEsolutionmeets3GPPstandards,providesseamlesscontinuitywithinthe
IMSandcircuitdomains,andiscostoptimizedforperformance.Becausevideoisthefastestgrowing
componentofmobiletraffic,CiscohasmadevideoacentralpartoftheinitialIMSoffering.

VoiceandVideooverLTEandIMS:OneVoiceSolution
CiscoprovidesacompletesolutionforV2oLTEbasedonthe3GPPIMSsolutionmeetingtheOneVoice
Initiative'sprofilerequirements.TheCiscoASR5000SeriessupportsahighperformanceIMSCSCF
core(P/I/S/ECSCF,PCRF,andBGCF).Thisfunctionalitycanbeprovidedasasetofstandalone
functionsorcanbeintegratedwithEPCfunctionstoprovidealowertotalcostofownership(TCO)for

Page 46

systemoperators.Additionalbenefitsofthesolutionincludehighavailability,supportforbothRFC
3261andIMSbasedSIPendpoints,fullregulatorysupport(suchaslocalnumberportability,
emergencycalling,andlawfulintercept),thehighestperformanceintheindustry,andIPmobility.
FormoreinformationontheCISCOV2oLTEsolution,pleaserefertothispage:
http://www.cisco.com/en/US/solutions/collateral/ns341/ns973/solution_overview_c22643109.html

D2Technologies
D2isarecognizedleaderinVoIPandconvergedIPcommunicationssoftwarefordevicesusedin4G
andnextgenerationnetworksthatdeliveradvancedcommunicationservices,suchasVoIPandvideo
over LTE (VoLTE) and IMSbased Rich Communications Suite (RCS). Manufacturers and service
providers rely on D2 software to deliver carriergrade IP communications across any network (LTE,
WiMAX,cellular,WiFi,broadband,PSTN),service(voice,video,IMchat,SMS,presence/status,etc.)
and system (carrier, IPPBX, UC, OTT, social network, etc.) for a broad range of fixed and mobile
devices.FromprocessingbillionsofVoIPminuteseachmonthtoaddingenhancedIPcommunications
for Android, learn how D2 software is converging communications at www.d2tech.com or follow
thecompanyonTwitter@D2Tech.

Genband
GENBANDisagloballeaderofIPinfrastructuresolutions,enablingserviceprovidersandenterprises
around the world to evolve communications networks through IP innovation. The Company offers
marketleadingSwitching,Applications,NetworkingandServicesolutions,withproductsdeployedin
over600customernetworksspanningmorethan80countries.GENBANDisheadquarteredinFrisco,
Texas,andhasvastresourcesinR&D,salesandsupportspanningmorethan50countries.Tolearn
more,visitusonthewebatwww.GENBAND.com.

Iskratel
With 60 years of experience in telecommunications, Iskratel belongs to the leading hightech
companies in the world, and develops integrated telecommunications solutions for the future
information society. The company provides integrated telecommunications solutions for fixed and
mobiletelephony,fornextgenerationnetworks,andfortelecommunicationsnetworkmanagement.
LinkingexperienceandintellectualcapitalwithcreativityandinnovationisdemonstratedinIskratel's
ability to successfully build telecommunications and next generation networks, and implement
advanced products, applications and solutions that are based on the emerging IMS/Tispan
technology.Thecompanyhasover1100employees,with300moreworkinginaffiliatedcompaniesin
20 countries. The direct presence of Iskratel's employees in foreign countries ensures full
harmonization of network solutions that we provide with the national telecommunications
requirementsaswellasourpartners'needs.
www.iskratel.com

JDSU
JDSUistheworldsleadingnetworkandserviceenablementcompany,transitioningfromtraditional
testandmeasurementtoprovideanintegratedportfoliothathelpsourcustomersdealwithsoaring
growthoftraffic,devicesandapplications.With2400employees,30salesandR&Dsites,4300
customersglobally,and$800Minannualrevenue,JDSUcommunicationstestandmeasurement
solutionssetanewstandardfornetworkandserviceenablement.Byreducingoperatingcostsand
deploymenttime,weoffervaluebasedsolutionsthatcreatenewrevenueopportunitiesaswellas
servicedifferentiation.JDSUMobilitysolutionsensureagileoperationbyemployingintelligentprobes

Page 47

andproductsthatcanbefullyintegratedtofitavarietyofapplicationsfromR&Dthroughnetwork
monitoring,fromthecoretoaccessdevices,andinlaboratorysettingsorlivenetworks.OnlyJDSUis
uniquelyqualifiedtoaddressyourwirelesschallengesinsuchacomprehensivefashion.
www.jdsu.com.

MetaswitchNetworks
MetaswitchNetworkspowersover600networkoperatorsworldwideandisaleadingproviderofthe
technologiesandsolutionsthatareempoweringthemigrationofcommunicationsnetworkstoopen,
nextgenerationarchitectures.Forover30years,Metaswitchhasbeeninnovatingsolutionsto
simplifycommunications,addnextgenfunctionalityandservices,whileaddressingthechallengesof
convergingnetworksanddevices.
http://www.metaswitch.com/

Neustar
Neustar,Inc.,(NYSE:NSR)isatrusted,neutralproviderofrealtimeinformationandanalysistothe
Internet, telecommunications, entertainment and marketing industries throughout the world.
Neustar applies its advanced, secure technologies in routing, addressing and authentication to its
customers data to help them identify new revenue opportunities and network efficiencies, and
institutecybersecurityandfraudprotectionmeasures.
Neustar is responsible for operating of the GSMAs PathFinder service, providing Carrier ENUM to
support addressing for IPX interconnect, global service provider discovery and number portability
resolution.
http://www.neustar.biz

Radisys
Radisys is a leading provider of embedded wireless infrastructure solutions for telecom, aerospace,
defense and public safety applications. Radisys' marketleading ATCA, IP Media Server (MRF) and
COM Express platforms coupled with worldrenowned Trillium software, services and market
expertise enable customers to bring highvalue products and services to market faster with lower
investment and risk. For 4G/LTE mobile deployments, Radisys media servers provide the MRF in a
3GPP IMS architecture, delivering scalable IP media processing required for Voice over LTE (VoLTE)
with HD audio, video streaming, mobile HD video conferencing, IPtoIP transcoding, multimedia
valueadded services (VAS) and other revenuegenerating LTE mobile services. Additional Radisys
solutionsincludeawidevarietyof3G&4G/LTEmobilenetworkapplicationsincluding:RadioAccess
Networks (RAN) solutions from Femtocells to Picocells and Macrocells, wireless core network
applications, WiFi & LTE Security Gateway, Deep Packet Inspection (DPI) and policy management.
http://www.radisys.com.

Tekelec
Tekelecs intelligent mobile broadband solutions enable service providers to manage and monetize
mobile data and evolve to LTE and IMS. We are the architects of the new Diameter network, the
foundationforsession,policyandsubscriberdatamanagement.Morethan300serviceprovidersuse
our marketleading solutions to deliver cloud, machinetomachine and personalized services to
consumersandenterprises.Formoreinformationvisitwww.tekelec.com.

Page 48

Ulticom
Ulticom, a Platinum Equity Company, is a leader in high performance mission critical products that
evolve information delivery. With over 6,000 deployments worldwide, the companys flagship
product,Signalware,isthepremierplatformforthedeploymentofapplicationsandserviceswithin
wireless,IP,andwirelinenetworks.
For over 35 years, Ulticom has delivered carriergrade solutions that are robust and reliable, all
backedbythecompanysunmatchedserviceandsupport.
Mobile Network Operators (MNO), Signaling Hub Providers (IPX, GRX), Telecom Equipment
Manufacturers(TEM)andSystemsIntegrators(SI)trustUlticomsolutionstooptimizeinformationand
applicationdeliverywithincreasedefficiencyandsecurity.
Formoreinformation,pleasevisitwww.ulticom.com.

Page 49

Potrebbero piacerti anche