Download - Imtcvoltetestcasesv1.2 21603 1
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 1 of 53
IMS
Activity Group
Test Cases - IMS Profile for Voice and SMS
Version 1.2
4 October 2013
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 2 of 53
History Version Date Name Reason
1.0 15-08-2011 Bo Jönsson Version 0.12 and CR 3, 4, 5, 26, 27, 32, 33, 35 and 36.
1.1 21-02-2013 Bo Jönsson CR 37, 46, 47, 48, 49, 54, 55, 56, 67, 68, 69 and 70.
1.2 18-06-2013 Bo Jönsson CR 57, 58, 59, 60 and 71.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 3 of 53
Table of Contents
1 Introduction ........................................................................................................................... 5
1.1 Scope .......................................................................................................................................... 5
1.2 How to Read the Test Cases ....................................................................................................... 5
1.2.1 Defining Test Cases ................................................................................................. 5
1.3 Abbreviations and Definitions .................................................................................................... 5
1.3.1 Definitions ............................................................................................................... 5
1.3.2 Abbreviations .......................................................................................................... 6
1.4 Default Endpoint Settings ........................................................................................................... 6
1.5 Test Case Number Representation .............................................................................................. 6
1.5.1 Test Case Number ................................................................................................... 6
1.6 How to Use Test Cases ............................................................................................................... 6
2 Interoperability Tests ............................................................................................................. 7
2.0 Test Procedures ........................................................................................................................... 7
2.0.1 Minimum Passing Criteria ....................................................................................... 7
2.1 Registration & Authentication .................................................................................................... 7
Test Case 2.1.1 – ISIM based UE authentication to IMS core network, using IMS-AKA ................ 7
Test Case 2.1.2 – USIM based UE authentication to IMS core network, using IMS-AKA ............... 8
Test Case 2.1.3 – UE de-registration from IMS core network ........................................................... 9
2.2 Call establishment and termination .......................................................................................... 10
Test Case 2.2.1 – Originating - Voice call set-up ............................................................................. 10
Test Case 2.2.2 – Terminating - Voice call set-up ............................................................................ 11
Test Case 2.2.3 – Terminating - video call set-up to a UE which only supports audio .................... 12
Test Case 2.2.4 – Terminating – audio to video upgrade to a UE which only supports audio ......... 13
Test Case 2.2.5 – Originating - Voice call set-up (SIP precondition not used in network) .............. 13
Test Case 2.2.6 – Terminating - Voice call set-up (SIP precondition not used in network) ............ 15
Test Case 2.2.8 – UE originated call to Home-Local Number ......................................................... 16
Test Case 2.2.9 – UE originated call to Geo-Local Number ............................................................ 17
2.3 Supplementary Services Test Cases ......................................................................................... 17
Test Case 2.3.1 – Originating Identification Presentation not subscribed ........................................ 17
Test Case 2.3.2 – Originating Identification Presentation subscribed .............................................. 18
Test Case 2.3.3 – Originating Identification Restriction .................................................................. 18
Test Case 2.3.4 – Terminating Identification Presentation subscribed............................................. 19
Test Case 2.3.4A – Terminating Identification Presentation not subscribed .................................... 20
Test Case 2.3.5 – Terminating Identification Restriction ................................................................. 20
Test Case 2.3.6 – Communication Forwarding unconditional ......................................................... 21
Test Case 2.3.7 – Originating – Communication HOLD .................................................................. 22
Test Case 2.3.8 – Terminating – Communication HOLD ................................................................. 23
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 4 of 53
Test Case 2.3.9 – Communication Forwarding on no Reply: limited ringing duration ................... 24
Test Case 2.3.10 – Originating – Creating a conference .................................................................. 25
Test Case 2.3.11 – Terminating – Joining a conference after receiving an invitation ....................... 27
Test Case 2.3.12 – Communication forwarding on busy................................................................... 29
Test Case 2.3.14 – Barring of All Incoming Calls ........................................................................... 29
Test Case 2.3.15 – Barring of All Outgoing Calls ............................................................................ 30
Test Case 2.3.16 – Barring of Outgoing International Calls ............................................................ 31
Test Case 2.3.17 – Barring of Incoming Calls when Roaming ........................................................ 32
Test Case 2.3.18 – Communication forwarding on not Reachable .................................................. 33
Test Case 2.3.19 – Communication Waiting .................................................................................... 33
2.4 SMS over IP.............................................................................................................................. 34
Test Case 2.4.1 – Originating – SMS over IP .................................................................................. 34
Test Case 2.4.2 – Terminating – SMS over IP ................................................................................. 35
Test Case 2.4.3 – Originating – SMS over IP (more than 160 characters) ........................................ 36
Test Case 2.4.4 – Terminating – SMS over IP (more than 160 characters) ...................................... 37
Test Case 2.4.5 – Originating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. Delivery report is sent to originating UE. 39
Test Case 2.4.6 – Terminating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. .......................................................... 40
2.5 SMS over SGs .......................................................................................................................... 42
Test Case 2.5.1 – Originating – SMS over SGs during EMM-IDLE state ........................................ 42
Test Case 2.5.2 – Originating – SMS over SGs during EMM-CONNECTED state ......................... 43
Test Case 2.5.3 – Terminating – SMS over SGs during EMM-IDLE state ...................................... 44
Test Case 2.5.4 – Terminating – SMS over SGs during EMM-CONNECTED state ....................... 45
2.6 DTMF ....................................................................................................................................... 45
Test Case 2.6.1 – Originating - DTMF sending over RTP payload ................................................. 45
2.7 Emergency Service ................................................................................................................... 46
Test Case 2.7.1 – Emergency call...................................................................................................... 46
Test Case 2.7.2 – Emergency call in limited service ......................................................................... 47
2.8 SRVCC ..................................................................................................................................... 48
Test Case 2.8.1 – SRVCC from E-UTRAN to GERAN without DTM support .............................. 48
3 References ........................................................................................................................... 53
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 5 of 53
1 Introduction This document describes the Test cases for IMS Client Application interoperability tests for terminal interoperability validation. This includes common scenarios for compliance testing. The optional tests section might be enhanced by additional tests of the testing parties as only the most probable test cases are described here.
For further terminal compliance test cases, please refer to the document “Test Cases – Compliance”.
1.1 Scope The present document defines terminal interoperability test cases for VoLTE as defined by the GSMA PRD IR.92.
The present document is applicable to:
- The interface between the User Equipment (UE) and the Call Session Control Function (CSCF);
- The interface between the User Equipment (UE) and an Application Server (AS);
1.2 How to Read the Test Cases Test Number: Identifies each of the Test Cases by its unique number.
Priority: Indicates if the test case is mandatory or optional if not indicated by a document section.
Objective: Provides background information description about the test case.
Reference: Indicates corresponding section of recommendation or specification for the test case.
UE Setup: Specifies all required UE settings for the named test case.
NW Setup: Specifies required network settings for the named test case.
Precondition: Specifies settings and environment required before conducting the test case.
Procedure: Describes how to conduct the test case.
Miscellaneous: Provides additional information such as illustrations on message sequences and expected header parameters.
Pass Criteria: Defines the Pass Criteria of the test case. Sub results to be performed successfully are listed. Verification of the correct behaviour may be visual, together with the aid of logging facilities available from the testing terminals.
1.2.1 Defining Test Cases When defining a test case, all of the above fields shall be included except those that indicate “optional”. When there is no information to be provided to a non-optional field, the field shall be filled with “None”.
By the time the Test Case document is updated, some fields may not have been updated and are marked with TBA. These fields are expected to be filled in in later versions of this test case document.
1.3 Abbreviations and Definitions
1.3.1 Definitions
For the purposes of the present document the following definitions apply: FFS
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 6 of 53
1.3.2 Abbreviations
For the purposes of the present document the following abbreviations apply:
3GPP - Third Generation Partnership Project
HTTP - HyperText Transfer Protocol
IMS - IP Multimedia Subsystem
MTSI - Multimedia Telephony Service for IMS
OIP - Originating Identity Presentation
OIR - Originating Identity Restriction
TC - Test Case
UE - User Equipment
URI - Uniform Resource Identifier
XCAP - eXtensible markup language Configuration Access Protocol
1.4 Default Endpoint Settings Two types of default endpoint settings are defined, which are Default Test Terminal Settings and Default Test Tool Settings. Default Test Terminal Settings are for UEUTs, which are not expected to change configurations. Default Test Tool Settings are for test reference tools, which are capable of varying a wide range of terminal configurations.
1.5 Test Case Number Representation Test case number representation shall be used for test score sheet reporting purpose.
1.5.1 Test Case Number Each Test Case is represented by a unique number.
If a new test case needs to be added for feature grouping purpose in between two existing test cases with consecutive test case numbers, a hyphen with a number is added to the test case number, e.g. Test Case 29-1 is inserted in between Test Case 29 and Test Case 30.
Cancelled Test Case number will not be reused for tests different from the original context.
If the terminal settings are identical for both Terminal A and Terminal B, the unique number itself is sufficient to represent the Test Case, e.g. Test Case 1.
When the terminal settings are different, the test case number should be added with a postfix letter ‘a’ or ‘b’ according to the terminal settings used, e.g. Test Case 2a and Test Case 2b.
1.6 How to Use Test Cases This test case document can be used according to the need of a company. It forms the basis for all kinds of IMS client application interoperability test events hosted by IMTC and IMTC IMS AG. It may be adopted by external parties according to their needs.
It is recommended all mandatory test cases should be conducted for every test event. All optional test cases are tested by priority as agreed by the two testing parties.
Test cases are regarded as successful when both testing terminals follow the testing procedure and the expected behaviour is observed.
All test results are recorded into test score sheet.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 7 of 53
2 Interoperability Tests
2.0 Test Procedures All tests shall be performed in that way that the device is not reset (removal of battery, shutdown) in between performing the following described tests.
2.0.1 Minimum Passing Criteria In each test case, the following criteria shall be satisfied for passing the test case unless otherwise stated: The pass criteria are specified in each test case.
2.1 Registration & Authentication
Test Case 2.1.1 – ISIM based UE authentication to IMS core network, using IMS-AKA Priority: Mandatory TC
Objective: Verify UE authentication to IMS Core network using ISIM-AKA procedure.
Reference: TS 24.229
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 provisioned for VoLTE Application.
2. UICC provisioned with ISIM.
Procedure: 1. Insert UICC in UE_1.
2. Power up UE_1 (device).
Miscellaneous: Messages Sequence
UE1 CSCF
REGISTER
401 Unauthorized
[1]
[2]
LTE attach / PDN Connection establishment / P-CSCF discovery
REGISTER
200 OK
[3]
[4]
Successful IMS registration
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 8 of 53
Header/parameter
[1] REGISTER (Request-URI) SIP/2.0
Authorization: (credentials)
Expires: (value)
[3] REGISTER (Request-URI) SIP/2.0
Authorization: (credentials)
Expires: (value)
Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Note: UE_1 may display an IMS Registered Icon.
Test Case 2.1.2 – USIM based UE authentication to IMS core network, using IMS-AKA Priority: Mandatory TC
Objective: Verify UE authentication to IMS Core network using USIM-AKA procedure.
Reference: TS 24.229
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 provisioned for VoLTE Application
2. UICC provisioned with USIM only
Procedure: 1. Insert UICC in UE_1.
2. Power up UE_1 (device).
Miscellaneous: Messages Sequence
UE1 CSCF
REGISTER
401 Unauthorized
[1]
[2]
LTE attach / PDN Connection establishment / P-CSCF discovery
REGISTER
200 OK
[3]
[4]
Successful IMS registration
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 9 of 53
Header/parameter
[1] REGISTER (Request-URI) SIP/2.0
Authorization: (credentials)
Expires: (value)
[3] REGISTER (Request-URI) SIP/2.0
Authorization: (credentials)
Expires: (value)
Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Note: UE_1 may display an IMS Registered Icon.
Test Case 2.1.3 – UE de-registration from IMS core network Priority: Mandatory TC
Objective: Verify UE Initiated De-Registration from IMS core network.
Reference: TS 24.229
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: UE_1 is connected and Registered to IMS network.
Procedure: Make UE_1 initiate IMS de-registration.
Miscellaneous: Messages Sequence
UE1 CSCF
REGISTER (Expires: 0)
200 OK
[1]
[2]
IMS Registered
Successful IMS De-registration
Header/parameter
[1] REGISTER (Request-URI) SIP/2.0
Expires: 0
Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 10 of 53
Note: UE may indicate that it is not IMS Registered on the display.
2.2 Call establishment and termination
Test Case 2.2.1 – Originating - Voice call set-up Priority: Mandatory TC
Objective: Verify that an originating IMS voice call is established.
Reference: TS 24.173, TS 24.229 and TS 26.114
UE_1 Setup: -
UE_2 Setup: -
NW Setup: SIP preconditions enabled.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
3. UE_1_and UE_2 support SIP preconditions and reliable provisional responses.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
Header/parameter
[1] INVITE (Request-URI) SIP/2.0
Supported: 100rel, precondition
Contact: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 11 of 53
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS:0 b=RR:0 a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220 a=rtpmap:(payload type) telephone-event a=ptime:20 a=maxptime:240 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos optional remote sendrecv
Pass Criteria: The voice call is established and successful speech between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.2.2 – Terminating - Voice call set-up Priority: Mandatory TC
Objective: Verify that a terminating IMS voice call is established.
Reference: TS 24.173, TS 24.229 and TS 26.114
UE_1 Setup: -
UE_2 Setup: -
NW Setup: SIP preconditions enabled.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
3. UE_1_and UE_2 support SIP preconditions and reliable provisional responses.
Procedure: 1. UE_2: dial a voice call to UE_1.
2. UE_1: answer call.
3. Speech.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 12 of 53
UE1 UE2
IMS registration IMS registration
INVITE
180 Ringing/200 OK
Media exchange in PS domain
[1]
[n]
Header/parameter
[n] SIP/2.0 200 OK or 180 Ringing
Contact: (addr-spec)
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS: (bandwidth-value) b=RR: (bandwidth-value) a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220 a=curr:qos local sendrecv a=curr:qos remote sendrecv a=des:qos mandatory local sendrecv a=des:qos mandatory remote sendrecv
Pass Criteria: The voice call is established and successful speech between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
NOTE: A 200 OK might be the response to the INVITE or an UPDATE.
Test Case 2.2.3 – Terminating - video call set-up to a UE which only supports audio Priority: Optional TC
Objective: Verify that a terminating audio-only UE is able to accept a video call request and downgrade it to audio-only call.
Reference: TS 24.173, TS 24.229, TS 26.114
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_2 supports audio and video.
3. UE_1 supports only audio.
Procedure: 1. UE_2: dial a video call to UE_1.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 13 of 53
2. UE_1: answer call.
3. UE_1: release call.
Miscellaneous: -
Pass Criteria: UE_1 accepts the video call request and replies with 200 OK response where the media port for video is set to zero. Successful audio call is established between UE_1 and UE_2.
Test Case 2.2.4 – Terminating – audio to video upgrade to a UE which only supports audio Priority: Optional TC
Objective: Verify that the audio-only UE will accept the re-INVITE request to update the session from audio to video.
Reference: TS 24.173, TS 24.229, TS 26.114
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports only audio.
3. UE_2 supports audio and video.
Procedure: 1. UE_2: dial an audio call to UE_1.
2. UE_1: answer audio call.
3. Speech.
4. UE_2: adds a video to existing call.
5. Speech.
6. UE_1: release call.
Miscellaneous: -
Pass Criteria: First, a successful audio call is established between UE_1 and UE_2. When UE_1 receives a re-INVITE to add video to the session, UE_1 accepts the video call request and replies with 200 OK response where the media port for video is set to zero. Audio session remains active.
Test Case 2.2.5 – Originating - Voice call set-up (SIP precondition not used in network) Priority: Mandatory TC
Objective: Verify that an originating IMS voice call is established.
Reference: TS 24.173, TS 24.229, TS 26.114
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 14 of 53
UE_1 Setup: -
UE_2 Setup: -
NW setup: SIP preconditions disabled.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
3. UE_1_and UE_2 support SIP precondition and 100Rel (reliable provisional responses).
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer call.
3. Speech
Miscellaneous: Messages Sequence
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
Header/parameter
[1] INVITE (Request-URI) SIP/2.0
Supported: 100rel, precondition
Contact: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS:0 b=RR:0 a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220 a=rtpmap:(payload type) telephone-event a=ptime:20 a=maxptime:240 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos optional remote sendrecv
Pass Criteria: The voice call is established and successful speech between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 15 of 53
section of this test case shall be verified.
Test Case 2.2.6 – Terminating - Voice call set-up (SIP precondition not used in network) Priority: Mandatory TC
Objective: Verify that a terminating IMS voice call is established.
Reference: TS 24.173, TS 24.229, TS 26.114
UE_1 Setup: -
UE_2 Setup: -
NW Setup: SIP preconditions disabled.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
3. UE_1_and UE_2 support SIP precondition and 100Rel (reliable provisional responses).
Procedure: 1. UE_2: dial a voice call to UE_1.
2. UE_1: answer call.
3. Speech
Miscellaneous: Messages Sequence
UE1 UE2
IMS registration IMS registration
INVITE
180 Ringing/200 OK
Media exchange in PS domain
[1]
[n]
Header/parameter
[n] SIP/2.0 200 OK or 180 Ringing
Contact: (addr-spec)
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS: (bandwidth-value) b=RR: (bandwidth-value) a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220
Pass Criteria: The voice call is established and successful speech between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 16 of 53
section of this test case shall be verified.
NOTE: A 200 OK might be the response to the INVITE or an UPDATE.
Test Case 2.2.8 – UE originated call to Home-Local Number Priority: Mandatory TC
Objective: Verify UE originated call to Home-Local Number.
Reference: TS 24.229
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Network must support the local numbers as defined in Alternative 2 in Sections 5.1.2A.1.3 and 5.1.2A.1.5 in TS 24.229.
2. A home-local address to UE_2 must be provisioned in the network.
Precondition: UE_1 and UE_2 are registered to an IMS network.
Procedure: 1. UE_1: dial a voice call to UE_2 using UE_2’s home-local number.
2. UE_2: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 UE2
INVITE
200 OK
[1]
[n]
IMS registration
Media exchange in PS domain
IMS registration
Header/parameter
[1] INVITE sip:(local-number-digits);phone-context=(domainname)@(domainname);user=phone SIP/2.0
Pass Criteria: The voice call is established and successful speech between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 17 of 53
Test Case 2.2.9 – UE originated call to Geo-Local Number Priority: Optional TC
Objective: Verify UE originated call to Geo-Local Number.
Reference: TS 24.229
UE_1 Setup: UE must support Geo-Local Number.
UE_2 Setup: -
NW Setup: 1. Network must support the local numbers as defined in Alternative 2 in Sections 5.1.2A.1.3 and 5.1.2A.1.5 in TS 24.229.
2. A geo-local address to UE_2 must be provisioned in the network.
Precondition: UE_1 and UE_2 are registered to an IMS network.
Procedure: 1. UE_1: dial a voice call to UE_2 using UE_2’s geo-local number.
2. UE_2: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 UE2
INVITE
200 OK
[1]
[n]
IMS registration
Media exchange in PS domain
IMS registration
Header/parameter
[1] INVITE sip:(local-number-digits);phone-context=(domainname)@(domainname);user=phone SIP/2.0
2.3 Supplementary Services Test Cases
Test Case 2.3.1 – Originating Identification Presentation not subscribed Priority: Optional TC
Objective: Verify UE behaviour when originating identification presentation is not subscribed
Reference: TS 24.607
UE_1 Setup: UE_1 subscription does not contain the Originating Identification
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 18 of 53
Presentation service
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.2.
Miscellaneous: -
Pass Criteria: Successful restriction of the UE_2 identity in UE_1.
Test Case 2.3.2 – Originating Identification Presentation subscribed Priority: Optional TC
Objective: Verify UE behaviour when originating identification presentation is subscribed
Reference: TS 24.607
UE_1 Setup: UE_1 subscription contains the Originating Identification Presentation service
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.2.
Miscellaneous: -
Pass Criteria: Successful presentation of the UE_2 identity in UE_1.
Test Case 2.3.3 – Originating Identification Restriction Priority: Mandatory TC
Objective: Verify originating identification restriction.
Reference: TS 24.607
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Originating Identification Restriction service is provisioned for UE_1 in a temporary mode, with a default value “presentation not restricted”. Originating Identification Presentation service is provisioned for UE_2.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 19 of 53
2. UE_1 and UE_2 support speech.
Procedure: 1. UE_1: dial a voice call with originating identification restriction to UE_2.
2. UE_2: answer call.
Miscellaneous: Messages Sequence
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
Header/parameter
[1] INVITE (Request-URI) SIP/2.0
From: "Anonymous" <sip:[email protected]>;tag= (value)
Privacy: id
Pass Criteria: Successful restriction of the UE_1 identity in UE_2.
The message sequence and order in the miscellaneous section of this test case shall be verified.
Test Case 2.3.4 – Terminating Identification Presentation subscribed Priority: Mandatory TC
Objective: Verify UE behaviour when terminating identification presentation is subscribed.
Reference: TS 24.608
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Terminating Identification Presentation service is provisioned for UE_1.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.1.
Miscellaneous: -
Pass Criteria: The voice call is established and identity information of UE_2 is present at
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 20 of 53
UE_1.
Test Case 2.3.4A – Terminating Identification Presentation not subscribed Priority: Mandatory TC
Objective: Verify UE behaviour when terminating identification presentation is not subscribed.
Reference: TS 24.608
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Terminating Identification Presentation service is not provisioned for UE_1.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.1.
Miscellaneous: -
Pass Criteria: The voice call is established and identity information of UE_2 is not present at UE_1.
Test Case 2.3.5 – Terminating Identification Restriction Priority: Mandatory TC
Objective: Verify terminating identification restriction.
Reference: TS 24.608
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Terminating Identification Restriction service is provisioned for UE_1 in a temporary mode, with a default value “presentation not restricted”. Terminating Identification Presentation service is provisioned for UE_2.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. UE_2: dial a voice call to UE_1.
2. UE_1: answer call with terminating identification restriction.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 21 of 53
UE1 UE2
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE2 UE1
IMS registration IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
Header/parameter
[n] SIP/2.0 200 OK
Privacy: id
Pass Criteria: The voice call is established and identity information of UE_1 is not present at UE_2.
The message sequence and order in the miscellaneous section of this test case shall be verified.
Test Case 2.3.6 – Communication Forwarding unconditional Priority: Mandatory TC
Objective: Verify communication forwarding unconditional.
Reference: TS 24.604
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration.
UE_2 Setup: -
UE_3 Setup: -
NW Setup: -
Precondition: 1. UE_1, UE_2 and UE_3 are connected and registered to an IMS network.
2. UE_1, UE_2 and UE_3 support speech.
Procedure: 1. UE_1: activate communication forwarding unconditional to UE_3.
2. UE_2: dial a voice call to UE_1.
3. UE_3: answer call.
4. Speech.
5. UE_2 hangs up.
6. UE_1: deactivate communication forwarding.
7. Perform a voice call according test case 2.2.2.
Miscellaneous: -
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 22 of 53
Pass Criteria: 1. The voice call is established between UE_2 and UE_3.
2. The voice call is established between UE_2 and UE_1.
Order: 1,2
Test Case 2.3.7 – Originating – Communication HOLD Priority: Mandatory TC
Objective: Verify originating communication hold.
Reference TS 24.610
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.1.
2. UE_1: put call on hold.
3. Speech.
4. UE_1: resume call.
5. Speech.
Miscellaneous: Messages Sequence
200 OK
UE1 UE2
IMS registration IMS registration
INVITE/UPDATE
Media exchange in PS domain
INVITE/UPDATE
200 OK
[1]
[n]
[o]
[p]
Header/parameter
[1] INVITE or UPDATE (Request-URI) SIP/2.0
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=RS: (bandwidth-value > 0)
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 23 of 53
b=RR: (bandwidth-value > 0)
a=sendonly
[o] INVITE or UPDATE (Request-URI) SIP/2.0
Content-Type: application/sdp
Content-Length: (value) m=audio (transport port) RTP/AVP (fmt) b=RS:0 b=RR:0
a=sendrecv or not present
Pass Criteria: 1. Speech is not present in UE_2.
2. Successful speech between UE_1 and UE_2.
Order: 1,2
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.3.8 – Terminating – Communication HOLD Priority: Mandatory TC
Objective: Verify terminating communication hold.
Reference TS 24.610
UE_1 Setup: -
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.1.
2. UE_2: put call on hold.
3. Speech.
4. UE_2: resume call.
5. Speech.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 24 of 53
200 OK
UE1 UE2
IMS registration IMS registration
INVITE/UPDATE
Media exchange in PS domain
[1]
INVITE/UPDATE
200 OK
[n]
[o]
[p]
Header/parameter
[n] SIP/2.0 200 OK
Contact: (addr-spec)
Content-Type: application/sdp
Content-Length: (value)
a=recvonly or inactive
[p] SIP/2.0 200 OK
Contact: (addr-spec)
Content-Type: application/sdp
Content-Length: (value)
Pass Criteria: 1. Speech is not present in UE_2.
2. Successful speech between UE_1 and UE_2.
Order: 1, 2
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.3.9 – Communication Forwarding on no Reply: limited ringing duration Priority: Mandatory TC
Objective: Verify communication forwarding on no Reply: limited ringing duration.
Reference: TS 24.604
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration.
UE_2 Setup: -
UE_3 Setup: -
NW Setup: NoReplyTimer
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 25 of 53
Precondition: 1. UE_1, UE_2 and UE_3 are connected and registered to an IMS network.
2. UE_1, UE_2 and UE_3 support speech.
Procedure: 1. UE_1: activate communication forwarding on no reply to UE_3.
2. UE_2: dial a voice call to UE_1.
3. Wait for the NoReplyTimer to expire.
4. UE_3: answer call.
5. Speech.
6. UE_2: hang up.
7. UE_1: deactivate communication forwarding.
8. Perform a voice call according test case 2.2.2.
Miscellaneous: -
Pass Criteria: 1. The voice call is established between UE_2 and UE_3.
2. The voice call is established between UE_2 and UE_1.
Order: 1,2
Test Case 2.3.10 – Originating – Creating a conference Priority: Mandatory TC
Objective: Verify that a conference can be created
Reference TS 24.147
UE_1 Setup: A Conference Factory URI shall be configured
UE_2 Setup: -
UE_3 Setup: -
NW Setup: The IMS core network shall support the conferencing procedures defined in 3GPP TS 24.605 with the clarifications in GSMA PRD IR.92 specification.
Precondition: 1. UE_1, UE_2 and UE_3 are connected and registered to the current IMS network.
2. UE_1, UE_2 and UE_3 support speech.
Procedure: 1. Perform a voice call according to TC 2.2.1
2. UE_1: Put UE_2 on hold.
3. UE_1: Dial a voice call to UE_3.
4. UE_3: Answer call
5. UE_1: Create a conference
6. UE_1: Invite UE_2 to the conference, by sending REFER to the conference focus
7. UE_2: Accept the invitation.
8. UE_1: Invite UE_3 to the conference
9. UE_3: Accept the invitation
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 26 of 53
Miscellaneous: Messages Sequence
[1]INVITE/UPDATE
Test Case 2.2.1
MRFC/AS
IMS registration
INVITE [o]
UE1
200 OK
INVITE
[o+p]
[q]
[q+r]
UE2 UE3
IMS registration IMS registration
200 OK
[n] 200 OK
202 Accepted [s+n]
REFER
REFER [s]
[t]
[t+u] 202 Accepted
Header/parameter
[1] INVITE or UPDATE (Request-URI) SIP/2.0
Content-Type: application/sdp
Content-Length: (value)
a=sendonly
[o] INVITE (Request-URI) SIP/2.0
Contact: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS: (bandwidth-value) b=RR: (bandwidth-value) a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220 a=ptime:20
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 27 of 53
a=maxptime:240
[q] INVITE (Request-URI to conference factory) SIP/2.0
Contact: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port) RTP/AVP (fmt) b=AS: (bandwidth-value) b=RS: (bandwidth-value) b=RR: (bandwidth-value)
a=rtpmap:(payload type) AMR/8000/1 a=fmtp:(format) mode-change-capability=2; max-red=220 a=ptime:20 a=maxptime:240
[s] REFER (Request-URI) SIP/2.0
Refer-To: <addr-spec?Replaces=(dialog-id)>
Referred-By: <addr-spec>
[t] REFER (Request-URI) SIP/2.0
Refer-To: <addr-spec?Replaces=(dialog-id)>
Referred-By: <addr-spec>
Pass Criteria: A conference session is established between UE_1 and the conference device.
Successful speech between UE_1, UE_2 and UE_3
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.3.11 – Terminating – Joining a conference after receiving an invitation Priority: Mandatory TC
Objective: Verify that a new user can be invited to an ongoing conference.
Reference 3GPP TS 24.147
UE_1 Setup: -
UE_2 Setup: -
NW Setup: The IMS core network shall support the conferencing procedures defined in 3GPP TS 24.605 with the clarifications in the GSMA PRD IR.92 specification.
Precondition: 1. UE_1 and UE_2 are connected and registered to the current IMS network.
2. UE_1 and UE_2 are voice capable.
Procedure: 1. UE_2: Perform a voice call to UE_3 according TC 2.2.1 (UE_2 act as UE_1, UE_3 act as UE_2)
2. UE_2: Put UE_3 on hold.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 28 of 53
3. UE_2: Dial a voice call to UE_1
4. UE_1: Answer call
5. UE_2: Create a conference
6. UE_2: Invite UE_3 to the conference.
7. UE_3: Accept the invitation
8. UE_2: Invite UE_1 to conference.
9. UE_1: Accept the conference invitation from UE_2.
Miscellaneous: Messages Sequence
MRFC/AS
IMS registration
200 Ok [y+z]
UE1
INVITE [y]
UE2 UE3[1]INVITE/UPDATE
Test Case 2.2.1
INVITE [o]
200 OK
INVITE
[o+p]
[q]
[q+r]200 OK
[n] 200 OK
202 Accepted [s+n]
REFER
REFER [s]
[t]
[t+u]202 Accepted
[1]INVITE/UPDATE
Test Case 2.2.1
INVITE [o]
200 OK
INVITE
[o+p]
[q]
[q+r] 200 OK
[n] 200 OK
202 Accepted [s+t]
REFER
REFER [s]
[w]
[w+x] 202 Accepted
IMS registration IMS registration
200 Ok [u+v]
INVITE [u]
Header/parameter
-
Pass Criteria: Successful speech between UE_1, UE_2 and other participants in the conference call.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 29 of 53
Test Case 2.3.12 – Communication forwarding on busy Priority: Mandatory TC
Objective: Verify communication forwarding on busy
Reference TS 24.604
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration.
UE_2 Setup: -
UE_3 Setup: -
UE_4 Setup: -
NW Setup: -
Precondition: 1. UE_1, UE_2, UE_3 and UE_4 are connected and registered to the current IMS network.
2. UE_1, UE_2, UE_3 and UE_4 support speech.
Procedure: 1. UE_1: activate communication forwarding on busy to UE_3.
2. UE_1: Perform a voice call to UE_2 according test case 2.2.1.
3. UE_4: while UE_1 is still engaged in the voice call of the previous bullet, dial a voice call to UE_1.
4. UE_3: answer call from UE_4 that was diverted from UE_1.
5. Speech
6. UE_3 hangs up
7. UE_1: deactivate communication forwarding.
Miscellaneous: -
Pass Criteria: The voice call is established between UE_1 and UE_2.
The voice call is established between UE_4 and UE_3.
Test Case 2.3.14 – Barring of All Incoming Calls Priority: Mandatory TC
Objective: Verify Barring of all incoming calls
Reference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration
UE_2 Setup: -
NW Setup: -
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 30 of 53
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. UE_1 activate Incoming Call Barring service
2. UE_2 perform a voice call towards UE_1.
3. UE_1 deactivate Incoming Call Barring service
4. UE_2 perform a voice call towards UE_1 according to the test case 2.2.2.
Miscellaneous: -
Pass Criteria: After activating Incoming Call Barring service, the voice call is not established between UE_1 and UE_2.
After de-activating Incoming Call Barring service, the voice call is established between UE_1 and UE_2.
Test Case 2.3.15 – Barring of All Outgoing Calls Priority: Mandatory TC
Objective: Verify Barring of all outgoing calls
Reference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration.
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. UE_1: activate Outgoing Call Barring service
2. UE_1: perform a voice call towards UE_2.
3. UE_1: deactivate Outgoing Call Barring service
4. UE_1: perform a voice call towards UE_2 according to the test case 2.2.1.
Miscellaneous: Messages Sequence for procedure 2
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 31 of 53
UE1
IMS registration
INVITE
603
[1]
[n]
UE1 TAS (Originating Network) IMS registration
INVITE
603 Response
[1]
[n]
Pass Criteria: After activating Outoing Call Barring service, the voice call is not established between UE_1 and UE_2
After de-activating Outoing Call Barring service, the voice call is established between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.3.16 – Barring of Outgoing International Calls Priority: Mandatory TC
Objective: Verify Barring of outgoing international calls
Reference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration.
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_2 is connected and registered to other IMS network which is located in different country.
3. UE_1 and UE_2 support speech.
Procedure: 1. UE_1: activate Outgoing International Call Barring service
2. UE_1: perform a voice call towards UE_2.
3. UE_1: deactivate Outgoing International Call Barring service
4. UE_1: perform a voice call towards UE_2.
Miscellaneous:
Messages Sequence for procedure 2
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 32 of 53
UE1
IMS registration
INVITE
603
[1]
[n]
UE1 TAS (Originating Network) IMS registration
INVITE
603 Response
[1]
[n]
Pass Criteria: After activating Outoing International Call Barring service, the voice call is not established between UE_1 and UE_2
After de-activating Outoing International Call Barring service, the voice call is established between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified
Test Case 2.3.17 – Barring of Incoming Calls when Roaming Priority: Mandatory TC
Objective: Verify Barring of incoming calls when roaming
Reference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration
UE_2 Setup: -
NW Setup: -
Precondition: 1. UE_1 is connected and registered via other IMS network than home IMS network.
2. UE_2 is connected and registered to IMS network. UE_1 and UE_2 support speech.
Procedure: 1. UE_1: activate Incoming Call Barring service when roaming.
2. UE_2: perform a voice call towards UE_1.
3. UE_1: deactivate Incoming Call Barring service when roaming.
4. UE_2: perform a voice call towards UE_1 according to the test case 2.2.2.
Miscellaneous: -
Pass Criteria: After activating Incoming Call Barring service when roaming, the voice call is not established between UE_1 and UE_2
After de-activating Incoming Call Barring service when roaming, the voice call is established between UE_1 and UE_2.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 33 of 53
Test Case 2.3.18 – Communication forwarding on not Reachable Priority: Mandatory TC
Objective: Verify Communication Forwarding on not Reachable.
Reference: TS 24.604
UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary service configuration
UE_2 Setup: -
UE_3 Setup: -
NW Setup: IMS core network must support the SIP procedures in TS 24.604 for Communication Diversion (CDIV).
Precondition: 1. UE_1, UE_2 and UE_3 are registered to an IMS network
2. UE_1, UE_2 and UE_3 support speech.
Procedure: 1. UE_1: activate communication forwarding on not reachable to UE_3
2. UE_1: make unreachable
3. UE_2: dial a voice call to UE_1
4. UE_3: answer call
5. Speech
6. UE_1: deactivate communication forwarding on not reachable
7. Perform a voice call according test case 2.2.2
Miscellaneous: -
Pass Criteria: 1. The voice call is established between UE_2 and UE_3.
2. The voice call is established between UE_2 and UE_1.
Order: 1,2
Test Case 2.3.19 – Communication Waiting Priority: Mandatory TC
Objective: Verify Communication Waiting.
Reference: TS 24.615
UE_1 Setup: The UE_1 shall support Alert-Info.
UE_2 Setup: -
UE_3 Setup: -
NW Setup: IMS core network must support the terminal based service, as described in TS 24.615.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 34 of 53
Precondition: 1. UE_1, UE_2 and UE_3 are registered to an IMS network
2. UE_1 and UE_2 are connected in a voice call.
Procedure: 1. UE_3: dial a voice call to UE_1.
2. UE_1: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 UE3
IMS registration
Media Exchange in PS domain
UE2
IMS registration IMS registration
Media Exchange in PS domain
INVITE [1]
[n]
200 OK [n+m]
Possibility for UE1 to react: Release session, invoke HOLD
180 Ringing
Header/parameter
[n] SIP/2.0 180 Ringing
Alert-Info: <urn:alert:service:call-waiting>
Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
2.4 SMS over IP
Test Case 2.4.1 – Originating – SMS over IP Priority: Mandatory TC
Objective: Verify an originating SMS over IP.
Reference: TS 24.341
UE_1 Setup: Configured to send SMS over IP.
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 supports the role of SM-over-IP sender.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 35 of 53
Procedure: 1. UE_1: send a SMS to UE_2 with up to 160 characters.
Miscellaneous: Messages Sequence
UE1 IP-SM-GW
IMS registration
MESSAGE
202 Accepted
[1]
[2]
MESSAGE [n]
[n+1 200 OK
Header/parameter
[1] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
[n+1] SIP/2.0 200 OK
Pass Criteria: The SMS has been successfully received by UE_2.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
Note: The step [n] is the submit report.
Test Case 2.4.2 – Terminating – SMS over IP Priority: Mandatory TC
Objective: Verify a terminating SMS over IP.
Reference: TS 24.341
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW and to deliver SMS over IP.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 is registered as SM-over-IP receiver.
Procedure: 1. UE_2: send a SMS to UE_1 with up to 160 characters.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 36 of 53
UE1 IP-SM-GW
IMS registration
MESSAGE [1]
[2] 200 OK
Header/parameter
[2] SIP/2.0 200 OK
Pass Criteria: The SMS has been successfully received by UE_1.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.4.3 – Originating – SMS over IP (more than 160 characters) Priority: Mandatory TC
Objective: Verify an Originating – SMS over IP (more than 160 characters).
Reference TS 24.341
UE_1 Setup: Configured to send SMS over IP.
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 supports the role of SM-over-IP sender.
Procedure: 1. UE_1: send a SMS to UE_1 with more than 160 characters.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 37 of 53
UE1 IP-SM-GW
MESSAGE [1]
IMS registration
Sent next SMS since Message length >160 Characters
MESSAGE [n]
200 OK [n+1]
[5]
MESSAGE [p]
200 OK [p+1]
MESSAGE [m]
[2] 202 Accepted
[m+1] 202 Accepted
Header/parameter
[1] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
[n+1] SIP/2.0 200 OK
[m] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
[p+1] SIP/2.0 200 OK
Pass Criteria: The SMS has been successfully received by UE_2. The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified. Note: The step [n and p] is the submit report.
Test Case 2.4.4 – Terminating – SMS over IP (more than 160 characters) Priority: Mandatory TC
Objective: Verify Terminating SMS over IP
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 38 of 53
Reference TS 24.341
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW and to deliver SMS over IP.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 is registered as SM-over-IP receiver.
Procedure: 1. UE_2: send a SMS to UE_2 with more than 160 characters.
Miscellaneous: Messages Sequence
UE1 IP-SM-GW
MESSAGE
200 OK
[1]
[2]
IMS registration
Received next SMS since Message length >160 Characters
MESSAGE [m]
200 OK [m+1]
MESSAGE (SMS-DELIVER-REPORT)
[n+1] 202 Accepted
[o]
[o+1]
[n]
MESSAGE (SMS-DELIVER-REPORT)
202 Accepted
Header/parameter
[2] SIP/2.0 200 OK
[n] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
[m+1] SIP/2.0 200 OK
[o] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
Pass Criteria: The SMS has been successfully received by UE_1.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 39 of 53
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified. Note: The step [n and o] is the delivery report.
Test Case 2.4.5 – Originating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. Delivery report is sent to originating UE. Priority: Mandatory TC
Objective: Verify an Originating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. Delivery report is sent to originating UE.
Reference TS 24.341
UE_1 Setup: Configured to send SMS over IP.
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW.
Precondition: 1. UE_1 to be configured for delivery report.
2. UE_1 is connected and registered to an IMS network.
3. UE_1 supports the role of SM-over-IP sender.
Procedure: 1. UE_2: make unreachable.
2. UE_1: send a SMS to UE_2.
3. UE_2: make reachable before TP-Validity-Period expires.
Miscellaneous: Messages Sequence
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 40 of 53
UE1 IP-SM-GW
MESSAGE [1]
IMS registration
Destination UE becomes reachable, stored SMS is delivered within TP-Validity-Period
MESSAGE (RP-ACK) [n]
200 OK [n+1]
MESSAGE (RP-DATA) [p]
200 OK [p+1]
[2] 202 Accepted
Header/parameter
[1] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
[n+1] SIP/2.0 200 OK
[p+1] SIP/2.0 200 OK
Pass Criteria: The SMS has been successfully received by UE_2. The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified. Note: The step [n] is the submit report and step [p] is the delivery report.
Test Case 2.4.6 – Terminating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. Priority: Mandatory TC
Objective: Verify Terminating –SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered.
Reference TS 24.341
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 41 of 53
UE_1 Setup: -
UE_2 Setup: -
NW Setup: Configured with an IP-SM-GW and to deliver SMS over IP.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 is registered as SM-over-IP receiver.
Procedure: 4. UE_1: make unreachable.
5. UE_2: send a SMS to UE_1.
6. UE_1: make reachable before TP-Validity-Period expires.
Miscellaneous: Messages Sequence
UE1 IP-SM-GW
MESSAGE
200 OK
[1]
[2]
Destination UE becomes reachable, stored SMS is delivered within TP-Validity-Period
MESSAGE (SMS-DELIVER-REPORT)
[n+1] 202 Accepted
[n]
UE is unreachable
UE reachability notification
Header/parameter
[2] SIP/2.0 200 OK
[n] MESSAGE (Request-URI) SIP/2.0
Content-Type: application/vnd.3gpp.sms
Content-Length: (value)
Pass Criteria: The SMS has been successfully received by UE_1.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Note: The step [n] is the delivery report.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 42 of 53
2.5 SMS over SGs
Test Case 2.5.1 – Originating – SMS over SGs during EMM-IDLE state Priority: Optional TC
Objective: Verify an originating SMS over SGs during EMM-IDLE state.
Reference TS 24.301
UE_1 Setup: UE_1 is configured to send SMS over SGs.
UE_2 Setup: -
NW Setup: Configured with MSC, SMS-IWMSC, and with SC.
Precondition: FFS
Procedure: 1. UE_1: sends a SMS over SGs to UE_2 with up to 160 characters.
Miscellaneous: Messages Sequence
Downlink NAS Transport
Uplink NAS Transport
UE1 MME
Combined Registration
EMM idle mode
SERVICE REQUEST
Uplink NAS Transport
Downlink NAS Transport
[1]
[2]
[5]
[4]
[3]
Header/parameter
[1] SERVICE REQUEST
[2] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-DATA
Message Type RP-DATA (MS to Network)
TP-MTI: SMS-SUBMIT
TP-User-Data: (sms text)
[5] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-ACK
Pass Criteria: The SMS has been successfully received by UE_2.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 43 of 53
Test Case 2.5.2 – Originating – SMS over SGs during EMM-CONNECTED state Priority: Optional TC
Objective: Verify an originating SMS over SGs during EMM-CONNECTED state.
Reference TS 24.301
UE_1 Setup: UE_1 is configured to send SMS over SGs.
UE_2 Setup: -
NW Setup: Configured with MSC, SMS-IWMSC and with SC.
Precondition: FFS
Procedure: 1. UE_1: sends a SMS over SGs to UE_2 with up to 160 characters.
Miscellaneous: Messages Sequence
Downlink NAS Transport
Uplink NAS Transport
UE1 MME
Combined Registration
EMM connected mode
Uplink NAS Transport
Downlink NAS Transport
[1]
[4]
[3]
[2]
Header/parameter
[1] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-DATA
Message Type RP-DATA (MS to Network)
TP-MTI: SMS-SUBMIT
TP-User-Data: (sms text)
[4] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-ACK
Pass Criteria: The SMS has been successfully received by UE_2.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 44 of 53
Test Case 2.5.3 – Terminating – SMS over SGs during EMM-IDLE state Priority: Optional TC
Objective: Verify a terminating SMS over SGs during EMM-IDLE state.
Reference TS 24.301
UE_1 Setup: UE_1 is configured to receive SMS over SGs
UE_2 Setup: -
NW Setup: Configured with MSC, SMS-GMSC and with SC
Precondition: FFS
Procedure: 1. UE_2: sends a SMS to UE_1 with up to 160 characters.
Miscellaneous: Messages Sequence
Uplink NAS Transport
MME UE1
Combined Registration
EMM Idle mode
Paging
SERVICE REQUEST
Downlink NAS Transport
[1]
[2]
[5]
Uplink NAS Transport [4]
[3]
Downlink NAS Transport [6]
Header/parameter
[2] SERVICE REQUEST
[4] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-ACK
[5] DTAP Short Message Service Message Type: CP-DATA
Message Type RP-ACK (MS to Network)
Pass Criteria: The SMS has been successfully received by UE_1.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 45 of 53
Test Case 2.5.4 – Terminating – SMS over SGs during EMM-CONNECTED state Priority: Optional TC
Objective: Verify a terminating SMS over SGs during EMM-CONNECTED state.
Reference TS 24.301
UE_1 Setup: UE_1 is configured to receive SMS over SGs
UE_2 Setup: -
NW Setup: Configured with MSC, SMS-GMSC and with SC
Precondition: FFS
Procedure: 1. UE_2: sends a SMS to UE_1 with up to 160 characters.
Miscellaneous: Messages Sequence
Uplink NAS Transport
UE1 MME
Combined Registration
EMM Connected mode
Downlink NAS Transport
[3]
Uplink NAS Transport [2]
Downlink NAS Transport [4]
[1]
Header/parameter
[2] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-ACK
[3] Uplink NAS Transport
DTAP Short Message Service Message Type: CP-DATA
Message Type RP-ACK (MS to Network)
Pass Criteria: The SMS has been successfully received by UE_1.
The message sequence, order, and header/parameters in the miscellaneous section of this test case shall be verified.
2.6 DTMF
Test Case 2.6.1 – Originating - DTMF sending over RTP payload Priority: Mandatory TC
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 46 of 53
Objective: Verify sending of DTMF events over RTP payload.
Reference: 3GPP TS 26.114 (Annex G), 3GPP TS 24.229
UE_1 Setup: -
UE_2 Setup: UE_2 is configured to support DTMF events over RTP payload.
NW setup: DTMF events over RTP payload must be supported by the network.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 and UE_2 support speech.
Procedure: 1. Perform a voice call according the test case 2.2.1.
2. UE_1: initiate DTMF digits ‘0-9’, and ‘*’, ‘#’.
Miscellaneous: -
Pass Criteria: UE_2 receives all DTMF events which are sent by UE_1.
2.7 Emergency Service
Test Case 2.7.1 – Emergency call Priority: Mandatory TC
Objective: Verify that an IMS emergency call is established.
Reference: TS 24.229 clauses 5.1.6.2 and 5.1.6.8.3 and TS 24.301
UE_1 Setup: -
UE_2 Setup: -
NW Setup: IMS emergency service is supported.
Precondition: 1. UE_1 is connected and registered to an IMS network.
2. UE_1 supports IMS emergency call.
Procedure: 1. UE_1: dial an emergency call number.
2. PSAP: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 PSAP
IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE1 PSAP
IMS registration
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 47 of 53
Header/parameter
[1] INVITE urn.service.sos SIP/2.0
From: "Anonymous"
To: urn.service.sos
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port)
Pass Criteria: The emergency call is established and successful speech between UE_1 and PSAP.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
Test Case 2.7.2 – Emergency call in limited service Priority: Mandatory TC
Objective: Verify that an IMS emergency call in limited service mode is established.
Reference: TS 24.229 clause 5.1.6.8.2 and TS 24.301
UE_1 Setup: -
UE_2 Setup: -
NW Setup: IMS emergency service in limited service mode is supported.
Precondition: 1. UE_1 no valid USIM is present.
2. UE_1 supports IMS emergency call.
Procedure: 1. UE_1: dial an emergency call number.
2. PSAP: answer call.
3. Speech.
Miscellaneous: Messages Sequence
UE1 PSAP
INVITE
200 OK
[1]
[n]
Media exchange in PS domain
UE1 PSAP
Media exchange in PS domain
Header/parameter
[1] INVITE urn.service.sos SIP/2.0
From: "Anonymous"
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 48 of 53
To: urn.service.sos
Content-Type: application/sdp
Content-Length: (value)
m=audio (transport port)
Pass Criteria: The emergency call is established and successful speech between UE_1 and PSAP.
The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.
2.8 SRVCC
Test Case 2.8.1 – SRVCC from E-UTRAN to GERAN without DTM support
Priority: Optional TC
Objective: Verify a PS-to-CS voice handover for the E-UTRAN subscribers in the SRVCC architecture.
Reference: TS 23.216 session 6.2.2.1
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Support of E-UTRAN and GERAN
2. E-UTRAN supports determining that the target is GERAN without DTM support or that the UE is without DTM support
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports SRVCC, E-UTRAN and GERAN.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer the call.
3. Speech.
4. Network: initiate SRVCC handover of UE_1 from E-UTRAN to GERAN.
5. Speech.
Miscellaneous: The call flow can be refered in TS 23.216 Figure 6.2.2.1-1
Pass Criteria: The voice call is established. Speech is successful and continuous.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 49 of 53
Test Case 2.8.2 – SRVCC from E-UTRAN to GERAN with DTM but without DTM HO support
Priority: Optional TC
Objective: Verify a PS-to-CS voice handover for the E-UTRAN subscribers in the SRVCC architecture.
Reference: TS 23.216 session 6.2.2.1A and session 6.2.2.1
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Support of E-UTRAN and GERAN
2. E-UTRAN supports determining that the target is GERAN with DTM but without DTM HO support and that the UE is supporting DTM.
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports SRVCC, E-UTRAN and GERAN.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer the call.
3. Speech.
4. Network: initiate SRVCC handover of UE_1from E-UTRAN to GERAN.
5. Speech.
Miscellaneous: The call flow can be refered in TS 23.216 Figure 6.2.2.1-1
Pass Criteria: The voice call is established. Speech is successful and continuous.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 50 of 53
Test Case 2.8.3 – SRVCC from E-UTRAN to GERAN with DTM HO support
Priority: Optional TC
Objective: Verify a PS-to-CS voice handover for the E-UTRAN subscribers in the SRVCC architecture.
Reference: TS 23.216 session 6.2.2.2
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Support of E-UTRAN and GERAN
2. E-UTRAN supports determining the target is GERAN with DTM support and the UE is supporting DTM
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports SRVCC, E-UTRAN and GERAN.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer the call.
3. Speech.
4. Network: initiate SRVCC handover of UE_1 from E-UTRAN to GERAN.
5. Speech.
Miscellaneous: The call flow can be refered in TS 23.216 Figure 6.2.2.2-1
Pass Criteria: The voice call is established. Speech is successful and continuous.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 51 of 53
Test Case 2.8.4 – SRVCC from E-UTRAN to UTRAN without PS HO Priority: Optional TC
Objective: Verify a PS-to-CS voice handover for the E-UTRAN subscribers in the SRVCC architecture.
Reference: TS 23.216 session 6.2.2.1 and session 6.2.2.1a
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Network support of E-UTRAN and UTRAN
2. E-UTRAN supports determining that the target is UTRAN without PS HO support
3. The target UTRAN doesn’t support PS HO
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports SRVCC, E-UTRAN and UTRAN.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer the call.
3. Speech.
4. Network: initiate SRVCC handover of UE_1 from E-UTRAN to UTRAN.
5. Speech.
Miscellaneous: The call flow can be refered in TS 23.216 Figure 6.2.2.1-1
Pass Criteria: The voice call is established. Speech is successful and continuous.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 52 of 53
Test Case 2.8.5 – SRVCC from E-UTRAN to UTRAN with PS HO support Priority: Optional TC
Objective: Verify a PS-to-CS voice handover for the E-UTRAN subscribers in the SRVCC architecture.
Reference: TS 23.216 session 6.2.2.2
UE_1 Setup: -
UE_2 Setup: -
NW Setup: 1. Network support of E-UTRAN and UTRAN
2. The target UTRAN supports PS HO
Precondition: 1. UE_1 and UE_2 are connected and registered to an IMS network.
2. UE_1 supports SRVCC, E-UTRAN and UTRAN.
Procedure: 1. UE_1: dial a voice call to UE_2.
2. UE_2: answer the call.
3. Speech.
4. Network: initiate SRVCC handover of UE_1 from E-UTRAN to UTRAN.
5. Speech.
Miscellaneous: The call flow can be refered in TS 23.216 Figure 6.2.2.2-1
Pass Criteria: The voice call is established. Speech is successful and continuous.
Test Cases - IMS Profile for Voice and SMS
IMTC_Test_Cases IMTC IMS AG Page 53 of 53
3 References [GSMA PRD IR.92] IMS Profile for Voice and SMS
[TS 24.229] Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3, 3GPP
[TS 24.173] IMS multimedia telephony communication service and supplementary services; Stage 3
[TS 26.114] IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction
[TS 24.604] Communication Diversion (CDIV); Protocol specification
[TS 24.607] Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification
[TS 24.608] Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification
[TS 24.610] Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification
[TS 34.229-1] Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification
[TS 24.341] Support of SMS over IP networks
[TS 36.523-1] Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception
[TS 24.301] Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)