Presentation on theme: "Giulio Maggiore E2NA#4 26-30 November Sophia Antipolis."— Presentation transcript:
Giulio Maggiore E2NA#4 26-30 November Sophia Antipolis
Background & Scope Event Details Results Overview Next Steps
RCS VoLTE IOT builds on previous IOT Events MSF LTE/EPC IOT in March 2010 & VoLTE IOT in September 2011 ETSI IMS Plugtests MSF partnered with ETSI & GSMA to jointly organise this event Reflects the common focus of all 3 partners in VoLTE & RCS Endorses a number of GSMA PRDs Joint Task Force, comprising members from the partner organizations, formed to oversee all aspects of the event Event web site at: http://www.msforum.org/interoperability/RCSVoLTE.shtml http://www.msforum.org/interoperability/RCSVoLTE.shtml
IOT Scope Two main scenarios: Scenario 1 – RCS VoLTE in Home/Single N/W GSMA PRDs IR.92, IR.94, IR.90, IR.67 and the RCS Services and Client Specification Scenario 2 – RCS VoLTE for Roaming & Interconnect GSMA PRDs IR.65, IR 88, IR.92, IR.94, IR.90, IR,67 and the RCS Services and Client Specification See Testing Scenarios document at http://www.msforum.org/interoperability/RCS%20V oLTE%20Scenarios%202012-07-16.pdf http://www.msforum.org/interoperability/RCS%20V oLTE%20Scenarios%202012-07-16.pdf
Sub-Scenarios & Test Plans (1/2) Scenario1 – Home/Single Network a - Attachment & Registration b - VoLTE & MMTEL services c - RCS services d – Multimedia & MMTEL services TS 103 029
Sub-Scenarios & Test Plans (2/2) Scenario 2 - Roaming and Interconnect a - Attachment & Registration Conf I Roaming I (Same PLMN) Conf II Roaming II (Diff. PLMN) Conf III Interconnect b - VoLTE & MMTEL Services c - RCS Services d – Multimedia & MMTEL services TS 186 011 TS 102 901 (Tested w/ Scenario 1)
Host Sites Sponsors
Observers: Participants :
Multi-vendor interoperability of UE, eNodeB, EPC, IMS/MMTEL, RCS AS, DRA and PCC technology. Attachment and registration following ETSI TS 103 029 VoLTE calls, based on GSMA IR.92, were demonstrated, including MMTEL services. Multimedia (voice/video) calls, based on GSMA IR.94, were demonstrated, including MMTEL services. Ut configuration of MMTEL services was demonstrated. Dedicated bearers with appropriate QCI were established for both voice & video connections.
RCS FT and RCS Chat were demonstrated. The IMS Soft Clients interworked successfully with 3 rd party LTE data dongles for attachment IMS services. No issues with GTP. Transcoding, transrating and DTMF collection was demonstrated via an AS and MRF DRAs greatly simplified Diameter routing and provided interworking between different transport layer protocols and Diameter application implementations.
PCC Issues On Rx interfaces, one P-CSCF was not compliant. Some AVPs were incorrectly present or incorrectly tagged as mandatory. These issues were fixed by the DRA. IMS Issues Fragmentation issues were seen when the MTU size exceeded that specified by 3GPP (e.g. 1500 octets in the transport network).
IMS Issues (continued) The Sh interface was not supported on all implementations of Application Servers. The Ut interface was not supported on all MMTel AS's. RCS Capability Exchange failed due to an IMS core not transiting the SIP OPTIONs message. Some SIP syntax errors observed – and also a difference in tolerance of such errors between implementations.
Transport Issues SCTP was not supported all DRA clients, TCP was the transport protocol supported by some of them. ENUM was not used.
2 PLMNs connected via an IPX. DIAMETER message routing via V-PLMN MME and H-PLMN HSS was proven to work via DEA/DRA in each lab and IPX DRA. HSS DRA/DEA IPX DRA DEA/DRA MME H-PLMNV-PLMNIPX
SIM Card Issues Roaming could only be tested one way Attachment Failure Despite DIAMETER routing working between the chain of DRAs and MME/HSS, the attachment did fail which then blocked further tests being able to be run... …however, there was a successful registration using a soft client attached to the IPX. DRA/DEA Topology Hiding Topology hiding was also tested.
The two host sites were successfully connected via an IPX with SIP/RTP traversing the IBCF/TrGW in each site and the intermediate IPX Gateway. Multi-vendor interoperability of IBCF/TrGW's and IPX was achieved. VoLTE calls, based on GSMA IR.92 and IR.65, are a viable solution for providing voice services for LTE access between Mobile Network Operators.
RCS tests were not run due to there being no RCS client in the Beijing lab. MMTel services were not tested due to a lack of time. Multi-media calls were not tested due to a lack of time. The external ENUM Server was not used by any of the IBCFs nor IPX.
Additional background activity to perform SIP / DIAMETER conformance criteria checking during IOT tests and validating ETSI Diameter /SIP Conformance Test Suites using ETSI tools to enable automatic conformance checking of Diameter / SIP messages captured during the IOT The Diameter signalling messages turned out to be syntactically correct. The SIP conformance criteria checking showed several syntax errors in SIP headers exchanged between different equipment, such as: missing characters (,...) in some headers unexpected superfluous space characters detected at the end of some SIP messages
Next Generation Services: RCS, VoLTE & Beyond Organized by ETSI and hosted by Iskratel, in parallel with the IOT Included a visit to the IOT lab and some demos Workshop details & presentations available at http://www.etsi.org/plugtests/RCS-VOLTE/Workshop.htm http://www.etsi.org/plugtests/RCS-VOLTE/Workshop.htm
White Paper launch: 14 th November Available at http://www.msforum.org/interoperability/RCSVoLTE.sht ml http://www.msforum.org/interoperability/RCSVoLTE.sht ml Liaison Statements sent to partner fora
Tests that were not run this time: RCS Presence / Cap Ex / In Call Services / Multi-Tasking Services Non-LTE Access via S4-SGSN Non-LTE Access via legacy SGSN 2G/3G handover via S4-SGSN 2G/3G handover via legacy SGSN Priority Call Handover (LTE/IMS Other RAN/CS) Other testing: Further RCS testing (ref. GSMA accreditation tests) Enterprise RCS LTE-Wi-Fi Interworking Emergency call SRVCC