VoLTE/ViLTE interconnection Common issues and the way … · -S8HR VoLTE Roaming architecture 8...

VoLTE/ViLTEinterconnectionCommonissuesandthewayforward

MartinBrand

ViceChairmanofETSITCINT,RapporteurofQ11/11andCo-RapporteurofQ2/11

Content

• General info about IMS interconnection

• Draft Recommendation ITU-T Q.30xx_VoLTE_Interconnection_FW “Framework of interconnection of VoLTE/ViLTE-based networks”

• NGN testing methods

• Recommendation ITU-T Q.3940 NGN/IMS interconnection tests between network operators at the IMS 'Ic' interface and NGN NNI/SIP-I

• Draft Recommendation ITU-T Q.VoLTE_INT_TEST“VoLTE/ViLTE interconnection testing for interworking and roaming scenarios including relevant QoS/QoE testing”

2

GeneralinfoaboutIMSinterconnection

• The project VoLTE/ViLTE interconnection requirements and testing is a joint project between ITU-T SG11 and ETSI TC INT

• Published Recommendations and Standards – Recommendation ITU-T Q.3940: NGN/IMS

interconnection tests between network operators at the IMS 'Ic' interface and NGN NNI/SIP-I

– ETSI TS 101 585-1 IMS interconnection tests at the IcInterface

• In development: – Draft Recommendation ITU-T

Q.30xx_VoLTE_Interconnection_FW “Framework of interconnection of VoLTE/ViLTE-based networks”

- Draft Recommendation ITU-T Q.VoLTE_INT_TEST“VoLTE/ViLTE interconnection testing for interworking and roaming scenarios including relevant QoS/QoE testing”

3

Draft Recommendation ITU-T Q.30xx_VoLTE_Interconnection_FW “Framework of interconnection of

VoLTE/ViLTE-based networks”• Key issues of interconnection

– different options for signalling protocols used for Inter-IMS interconnection, which can support all existing services (basic call and supplementary services);

– different options for roaming scenarios (there are no strict requirements for operators and no default option);

– charging (e.g. roaming charges, calls using interconnection networks);

– numbering/addressing (e.g. ENUM resolution, ITU-T E.164 à SIP-URI conversion);

– floating delay (problem of providing legacy services and applications, e.g. Fax/Modem over IP);

– Lawful interception– Data retention – Emergency services (e.g. emergency call 112)

4

Q.30xx_VoLTE_Interconnection_FWE2E scenarios in terms of interconnection and

roaming

VoLTE– IMS/MMTel interconnectionscenarios

VoLTE– Legacynetworkinterconnectionscenarios

VoLTE/ViLTE– VoLTE/ViLTEinterconnectionscenarios5

Q.30xx_VoLTE_Interconnection_FWE2E scenarios in terms of interconnection and

roaming

No. Scenario Description Roamingoptions

VoLTE– IMSinterworkingscenarios

1 Scenario1 TheuserUE1(a)isintheIMSnetworkA,UE2(a)inHPMN(a)

2 Scenario1A TheuserUE1(a)isintheIMSnetworkA,UE2(a)inHPMN(a)withCSFB(circuitswitchedfallback)

3 Scenario1B TheuserUE1(a)isintheIMSnetworkA,UE2(a)inHPMN(a)ismovingfrom4Gto3GcoveragewithSRVCC

4 Scenario1C TheuserUE1(a)isanomadicuserintheIMSnetworkB,UE2(a)inHPMN(a)

5 Scenario1D TheuserUE1(a)isanomadicuserintheIMSnetworkB,UE2(a)inHPMN(a)withCSFB(circuitswitchedfallback)

6 Scenario1E TheuserUE1(a)isanomadicuserintheIMSnetworkB,UE2(a)inHPMN(a)movingfrom4Gto3GcoveragewithSRVCC

7 Scenario2 TheuserUE1(a)isintheIMSnetworkA,UE2(a)roamedinVPMN(b)

- LocalBreakoutVPMNRoutingarchitecture(LBO-VR)- LBOHomeRoutingarchitecture(LBO-HR)- S8HRVoLTERoamingarchitecture

8 Scenario2A TheUE1(a)isanomadicuserintheIMSnetworkB,UE2(a)roamedinVPMN(b)


9 Scenario2B TheuserUE1(a)isintheIMSnetworkA,UE2(a)roamedinVPMN(b)withCSFB(circuitswitchedfallback)


10 Scenario2C TheuserUE1(a)isintheIMSnetworkA,UE2(a)roamedinVPMN(b)movingfrom4Gto3GcoveragewithSRVCC


• Ittherecommendationarelisted36E2Escenarios(seeexample)

6

Q.30xx_VoLTE_Interconnection_FWVoLTE Considerations

• EPC Consideration• EPC Configuration Requirements• Device and U/ISIM consideration

– Multi-Mode and Multi-band Terminal– General Requirements for VoLTE Terminal– RAN Features– IMS function on control plane– IMS function on media plane– Services Requirements

7

3TypesofIMSroamingarchitectures

8

ComparisonofVoLTERoamingArchitectures

9

Item Option1LBO-VR

(TargetIMSroamingsolution,IMSisrequiredinboth

VPLMNandHPLMN)

Option2,LBO-HR(Datalocalbreakout,

butIMShomerouted,IMSisnotneededinVPLMN)

Option3S8HRDataandIMSarebothhomerouted,IMSisnotneededinVPLMN

HPLMNwithVoLTEimplementation

Required Required Required

VPLMNwithVoLTEimplementation

Required Notrequired Notrequired

IMSserviceoverGRX Notrequired Required RequiredChargingdependingonEvolvedPacketCore(EPC)

Optional(ChargeonIMSservicelayer)

Required Required

Policyandchargingcontrolmode

HPLMNhPCRF cancontroll theVPLMNvPCRF viaS9Interface

(S9interfaceisoptional)

HPLMNhPCRFcontrolsVPLMNvPCRFviaS9Interface,S9interfaceismandatory

HPLMNhPCRFcontrolsHPLMNPGW,2/3GdataroamingviaS8

SingleRadioVoiceCallContinuity(SRVCC)supportcapability

FullySupported Supported Partiallysupported

VoLTElocalemergencycall

Supported Supported Notsupported

VoLTElocalLI Supported Supported NotsupportedLBOwithOptimalMediaRouteing(OMR)

Supported Notsupported Notsupported

IMSRoamingandInterworkingGuidelinesLocalBreakoutVPMNRoutingarchitecture

(LBO-VR)(Ref.IR.65)(Option1)

10

IMSRoamingandInterworkingGuidelinesLBOHomeRouting

architecture(LBO-HR)(Option2)(Ref.IR.65)

11

Roamingarchitectureforlocalbreakout,withhomeoperator'sapplication

functionsonly(Option2)

12

IMSRoamingandInterworkingGuidelinesS8HRVoLTERoamingarchitecture(Ref.b-IR.65)

(Option3)

SGW

MME

E- UTRAN

HSS

PGW

P-CSCF

S-CSCF

B- PARTY

VPLMNofA-Party H PLMNofA-PartyIPX

IBCF/BGCF/MGCF

TAS

PCRF

TDMorIPXControlPlane(SIP)UserPlane(RTPmedia)

IMSAGW/TrGW

13

Roamingarchitecturescenariowithhomeroutedtraffic(Option3)

14

Servicesfore2eVoLTE/ViLTEinterconnectionscenarios

# Service ITU-TRecommendation

RelevantstandarddevelopedbyotherSDO

Status

1. Basiccall(voiceandvideosessions)

Q.3403v.1 ETSITS124.229 M

Supplementaryservices

1. TIP/TIR Q.3617v.1 ETSITS124.608 O

1. OIP/OIR Q.3618v.1 ETSITS124.607 M

1. HOLD Q.3619v.1 ETSITS124.610 O

1. CDIV Q.3620v.1 ETSITS124.604 O

1. CONF Q.3621v.1 ETSITS124.605 O

1. CW Q.3622v.1 ETSITS124.615 O

1. ECT Q.3623v.1 ETSITS124.629 O

1. MCID Q.3624v.1 ETSITS124.616 O

1. CC Q.3625v.1 ETSITS124.642 O

1. MWI Q.3626v.1 ETSITS124.606 O

1. CUG Q.3627v.1 ETSITS124.654 M

1. ACR-CB Q.3628v.1 ETSITS124.611 O15

Protocolimplementationstatement(PICS)

SELECTIONEXPRESSION: Support SupportNetworkA NetworkB

NetworkcapabilitiesSE1: Theoriginatingnetwork(NetworkA)sendstheP-Charging-Vectorheader?SE2: Theoriginatingnetwork(NetworkA)sendsasubsetofparametersintheP-Charging-Vectorheader?

SE3: TheP-Early-Mediaheaderissupported?SE4: OverlapprocedureusingmultipleINVITEmethodissupported?SE5: Overlapsendingusingin-dialogmethodissupported?SE6: NetworkAsupportsthePSTNXMLschema?

SE7: Theresourcereservationprocedureissupported?SE8: Doesthenetworkperformthe“Fallback”procedure(PSTNor MGCF)?SE9: Thenetworkisuntrusted?SE10: Originatingnetworkdoesnothaveanumberportabilitydatabase,thenumberportabilitylookupisdoneintheinterconnectednetwork?

SE11: ThenetworksupportstheREFERmethod?SE12: TheNetworksupportsthe3partycallcontrolprocedure(REFERinterworking)?

SE13: TheNumberPortabilityissupported?SE14: CarrierSelectionisperformed?SE15: TheNetworkisaLongdistancecarrier?SE16: SIPSupportofChargingissupported?SE17: TheinterworkingISUP- SIPIisperformedinthenetwork?

Supplementaryservices16

ExampleofthePICS

NGNtestingmethods

• Conformance testing or type testing – The purpose of conformance testing is to determine to

what extent a single implementation of a particular standard conforms to the individual requirements of that standard.

• Interoperability testing – Interoperability testing is the activity of proving that

end-to-end functionality between (at least) twocommunicating systems is as required by those basesystems' standards.

NGN testing methods

18

• Network Integration Tests • End-to-End Tests • QoS Tests • Roaming Tests • Interconnection Tests• Functional tests/Real Equipment Tests• Emergency call tests• Benchmark / Load Tests• Security Tests

NGN - Interoperability testing methods

Content of the latest generation of interconnection tests

19

Functional TestingReal Equipment Tests

Load & StressTesting

Type acceptance:Functional testing +Load & stress

Interconnection Tests

Network monitoringQoS surveillanceRoaming Tests

Test

ing

met

hod

Supplier‘s business

Operator‘s business

Interoperability Testing

20

Combining Interoperability and Conformance Testing§ Conformance and Interoperability

Ø both important and useful approaches to the testing of standardized protocol implementationsØ although it is unlikely that one will ever fully replace the other

§ Conformance testingØ able to show that a particular implementation complies with all of the protocol requirements specified in the associated base standardØ difficult for such testing is to be able to prove that the implementation will interoperate with similar implementations in other products

21

Recommendation ITU-T Q.3940: NGN/IMS interconnection tests

between network operators at the IMS 'Ic' interface and NGN

NNI/SIP-I

22

ITU-TQ.3940,NGN/IMSinterconnectiontestsbetweennetworkoperatorsatthe

IMS'Ic'interfaceandNGNNNI/SIP-I

– The Recommendation Q.3940 defines interconnection tests between national and international network operators, at the IMS interconnection (Ic) interface and NGN network-to-network interface (NNI)/SIP-I.

– Such tests have been developed to verify the overall compatibility of the session initiation protocol (SIP), the integrated services digital network (ISDN) and the non-ISDN (public switched telephone network (PSTN) over the national or international NGNs, with regard to the use of end devices in the relevant networks (recommended by the network operator).

23

RecommendationITU-TQ.3940Referenceconfigurationfortheinterconnectiontest

24

RecommendationITU-TQ.3940ControlPlaneInterfaces

25

RecommendationITU-TQ.3940Control/UserPlaneInterfaces

26

RecommendationITU-TQ.3940Enddevicesusedintherelevantnetwork

NetworkA NetworkB0 0

SIP-VoIPPOTSISDNGSMVoUMTSVoLTEPSTN

Highlightcolor Refernce

TS124229

TS183043

TS183036

ITU-TQ.761-Q764TS129163ITU-TQ.1912.5

TheuserequipmentisaSIPhardphoneoraSIPsoftclientonaPCinthefixednetworkTheuserequipmentisa4GmobiledeviceinanLTEnetworkTheuserequipmentisa3GmobiledeviceinanUMTSnetwork

Theuserequipmentisanintegratedenddeviceinthefixednetwork-accessviaalegacyanaloguedevice

Theuserequipmentisa2GmobiledeviceinanGSMnetwork.SS7/SIPinterworkingappliesTheuserequipmentislocatedinafixedSS7network(analogueorISDN)

Explanation

Theuserequipmentisanintegratedenddeviceinthefixednetwork-accessviaalegacyISDNdevice

27

DraftRecommendationITU-TQ.VoLTE_INT_TEST“VoLTE/ViLTEinterconnectiontestingfor

interworkingandroamingscenariosincludingrelevantQoS/QoEtesting”

28

DraftRecommendationITU-TQ.VoLTE_INT_TEST

Generalinfo• The draf Q.VoLTE_INT_TEST is based on the ITU-T Q.3940• The Recommendation Q.3940 has been extended with the

requirements defined in ITU-T Q.30xx_VoLTE_Interconnection_FW “Framework of interconnection of VoLTE/ViLTE-based networks”– E2E scenarios in terms of interconnection and roaming– IMS Roaming and Interconnection Guidelines– with QoS/QoE tests

29

E2Escenariosexamplesintermsofinterconnectionandroaming

No. Scenario Description Roaming options Calling options VoLTE – IMS interworking scenarios

1 Scenario 1 The user UE1 (a) is in the IMS network A , UE2 (a) in HPMN (a) The test shall be performed in both directions

2 Scenario 1A The user UE 1 (a) is in the IMS network A , UE2 (a) in HPMN (a) with CSFB (circuit switched fallback)

The test shall be performed in both directions

3 Scenario 1B The user UE1 (a) is in the IMS network A , UE2 (a) in HPMN (a) is moving from 4G to 3G coverage with SRVCC


4 Scenario 1C The user UE1 (a) is a nomadic user in the IMS network B, UE2 (a) in HPMN (a)


5 Scenario 1D The user UE1 (a) is a nomadic user in the IMS network B, UE2 (a) in HPMN (a) with CSFB (circuit switched fallback)


6 Scenario 1E The user UE1 (a) is a nomadic user in the IMS network B, UE2 (a) in HPMN (a) moving from 4G to 3G coverage with SRVCC


7 Scenario 2 The user UE1 (a) is in the IMS network A , UE2 (a) roamed in VPMN (b)

- Local Breakout VPMN Routing architecture (LBO-VR) - LBO Home Routing architecture (LBO-HR) - S8HR VoLTE Roaming architecture


8 Scenario 2A The UE1 (a) is a nomadic user in the IMS network B, UE2 (a) roamed in VPMN (b)



9 Scenario 2B The user UE1 (a) is in the IMS network A , UE2 (a) roamed in VPMN (b) with CSFB (circuit switched fallback)



30

QoSUserPlaneTests

• The latest generation of interconnection tests includes QoS user plane tests

• For VoLTE interconnect and roaming with QoE and QoS Tests are following KPI mandatory:– call set-up time (Post Dialling Delay)– Listening speech quality– End-to-end audio delay, – End-to-end audio delay variation– Early media

31

Thankyou!

[email protected]

VoLTE/ViLTE interconnection Common issues and the way … · -S8HR VoLTE Roaming architecture 8...

Documents

Transcript of VoLTE/ViLTE interconnection Common issues and the way … · -S8HR VoLTE Roaming architecture 8...