2 GSMA Compliance

This chapter describes Oracle Communications Evolved Communications Application Server's compliance with GSMA standards.

The GSMA standard compliance statements are:

FCM01 Compliance

Table 2-1 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document FCM01, "VoLTE Service Description and Implementation Guide (Version 1.1)."

Table 2-1 GSMA_FCM01 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

Noted

1.1

Overview

7.0.0

Noted

1.2

Relationship to Standards

7.0.0

Noted

1.3

Scope

7.0.0

Noted

1.4

Definition of Terms

7.0.0

Noted

1.5

Document Cross-References

7.0.0

Noted

2

VoLTE Architecture

7.0.0

Noted

2.1

VoLTE Functional Node Description

7.0.0

Noted

2.1.1

VoLTE UE (User Equipment)

7.0.0

Noted

2.1.2

Evolved Universal Terrestrial Access Network (E-UTRAN)

7.0.0

Noted

2.1.2.1

eNodeB

7.0.0

Noted

2.1.3

Evolved Packet Core

7.0.0

Noted

2.1.3.1

MME (Mobility Management Entity)

7.0.0

Noted

2.1.3.2

SGW (Serving Gateway)

7.0.0

Noted

2.1.3.3

PGW (Packet Data Network Gateway)

7.0.0

Noted

2.1.3.4

HSS (Home Subscriber Server)

7.0.0

Noted

2.1.3.5

PCRF (Policy Charging and Rules Function)

7.0.0

Noted

2.1.4

IMS

7.0.0

Noted

2.1.4.1

P-CSCF (Proxy Call Session Control Function)

7.0.0

Noted

2.1.4.2

I-CSCF (Interrogating Call Session Control Function)

7.0.0

Noted

2.1.4.3

S-CSCF (Serving Call Session Control Function)

7.0.0

Noted

2.1.4.4

Telephony Application Server (TAS)

7.0.0

NA

2.1.4.5

MRF (Media Resource Function)

7.0.0

Noted

2.1.4.6

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

7.0.0

Noted

2.1.4.7

IMS-ALG/IMS-AGW (IMS Application Level Gateway/IMS Access Gateway)

7.0.0

Noted

2.1.4.8

MGCF/IMS-MGW (Media Gateway Control Function / IMS Media Gateway)

7.0.0

Noted

2.1.4.9

BGCF (Breakout Gateway Control Function)

7.0.0

Noted

2.1.5

Additional Network Functionality

7.0.0

Noted

2.1.5.1

ENUM

7.0.0

Noted

2.1.5.2

IPX

7.0.0

Noted

2.1.5.3

Diameter Agent

7.0.0

Noted

2.1.5.4

SEG (Security Gateway)

7.0.0

Noted

2.2

VoLTE Interface Description

7.0.0

Noted

2.2.1

LTE-Uu Interface (UE - eNodeB)

7.0.0

Noted

2.2.2

S1-MME Interface (UE - MME)

7.0.0

Noted

2.2.3

S1AP Interface (eNodeB - MME)

7.0.0

Noted

2.2.4

S1-U Interface (eNodeB - SGW)

7.0.0

Noted

2.2.5

X2 Interface (eNodeB - eNodeB)

7.0.0

Noted

2.2.6

S5 Interface (SGW - PGW)

7.0.0

Noted

2.2.7

S6a Interface (HSS - MME)

7.0.0

Noted

2.2.8

S9 Interface (H-PCRF - V-PCRF)

7.0.0

Noted

2.2.9

S10 Interface (MME - MME)

7.0.0

Noted

2.2.10

S11 Interface (MME - SGW)

7.0.0

Noted

2.2.11

Gx Interface (PCRF - PGW)

7.0.0

Noted

2.2.12

Rx Interface (PCRF - P-CSCF)

7.0.0

Noted

2.2.13

SGi Interface (PGW - P-CSCF)

7.0.0

Noted

2.2.14

Cx Interface (I/S-CSCF - HSS)

7.0.0

Noted

2.2.15

Sh Interface (VoLTE AS - HSS)

7.0.0

See "3GPP_TS_29.328 Compliance" and "3GPP_TS_29.329 Compliance" PICS statements.

2.2.16

Gm Interface (UE - P-CSCF)

7.0.0

Noted

2.2.17

Ut Interface (UE - TAS)

7.0.0

XCAP not supported.

2.2.18

Mx Interface (x-CSCF - IBCF)

7.0.0

Noted

2.2.19

Mw Interface (x-CSCF - x-CSCF)

7.0.0

Noted

2.2.20

Mg Interface (xCSCF - MGCF)

7.0.0

Noted

2.2.21

Mi Interface (xCSCF - BGCF)

7.0.0

Noted

2.2.22

Mj Interface (BGCF - MGCF)

7.0.0

Noted

2.2.23

ISC Interface (S-CSCF - TAS)

7.0.0

NA

2.2.24

Mr Interface (S-CSCF - MRF)

7.0.0

Noted

2.2.25

Mr Interface (TAS - MRF)

7.0.0

NA

2.2.26

Cr Interface (TAS - MRF)

7.0.0

See "3GPP_TS_24.147 Compliance" PICS

2.2.27

Mb Interface (media bearer)

7.0.0

Noted

2.2.28

Ici Interface (IBCF - IBCF)

7.0.0

Noted

2.2.29

Izi Interface (TrGW - TrGW)

7.0.0

Noted

2.3

Related GSMA Permanent Reference Documents

7.0.0

Noted

3

VoLTE Implementation - Single PMN

7.0.0

NA

3.1

General

7.0.0

NA

3.2

VoLTE Basic Call Flows

7.0.0

NA

3.2.1

VoLTE UE Attachment and IMS Registration

7.0.0

NA

3.2.1.1

General

7.0.0

NA

3.2.1.2

Message Sequence

7.0.0

NA

3.2.1.3

Detailed Description

7.0.0

NA

3.2.1.3.1

VoLTE UE Attach

7.0.0

NA

3.2.1.3.2

VoLTE UE Initial IMS Registration

7.0.0

A SIP SUBSCRIBE message is never sent by the TAS. (OCECAS does not need to know about changes to the public user identity)

3.2.2

VoLTE UE Initiated Detach and IMS Deregistration

7.0.0

NA

3.2.2.1

General

7.0.0

NA

3.2.2.2

Message Sequence

7.0.0

NA

3.2.2.3

Detailed Description

7.0.0

NA

3.2.2.3.1

IMS Deregistration

7.0.0

NA

3.2.2.3.2

VoLTE UE Detach

7.0.0

NA

3.2.3

Basic VoLTE UE to VoLTE UE Voice Call Establishment - Originating Side

7.0.0

NA

3.2.3.1

General

7.0.0

NA

3.2.3.2

Message Sequence

7.0.0

NA

3.2.3.3

Detailed Description

7.0.0

NA

3.2.4

Basic VoLTE UE to VoLTE UE Voice Call Establishment - Terminating Side

7.0.0

NA

3.2.4.1

General

7.0.0

NA

3.2.4.2

Message Sequence

7.0.0

NA

3.2.4.3

Detailed Description

7.0.0

NA

3.2.5

Basic VoLTE UE to VoLTE UE Voice Call Clearing - Initiated

7.0.0

NA

3.2.5.1

General

7.0.0

NA

3.2.5.2

Message Sequence

7.0.0

NA

3.2.5.3

Detailed Description

7.0.0

NA

3.2.6

Basic VoLTE UE to VoLTE UE Voice Call Clearing - Received

7.0.0

NA

3.2.6.1

General

7.0.0

NA

3.2.6.2

Message Sequence

7.0.0

NA

3.2.6.3

Detailed Description

7.0.0

NA

3.2.7

Basic VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Establishment - Originating Side

7.0.0

NA

3.2.7.1

General

7.0.0

NA

3.2.7.2

Message Sequence

7.0.0

NA

3.2.7.3

Detailed Description

7.0.0

NA

3.2.8

Basic VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Establishment - Terminating Side

7.0.0

NA

3.2.8.1

General

7.0.0

NA

3.2.8.2

Message Sequence

7.0.0

NA

3.2.8.3

Detailed Description

7.0.0

NA

3.2.9

Basic VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Clearing - Initiated

7.0.0

NA

3.2.9.1

General

7.0.0

NA

3.2.9.2

Message Sequence

7.0.0

NA

3.2.9.3

Detailed Description

7.0.0

NA

3.2.10

Basic VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Clearing - Received

7.0.0

NA

3.2.10.1

General

7.0.0

NA

3.2.10.2

Message Sequence

7.0.0

NA

3.2.10.3

Detailed Description

7.0.0

NA

3.2.11

Basic VoLTE UE to VoLTE UE - Adding a video media stream - Originating Side

7.0.0

NA

3.2.11.1

General

7.0.0

NA

3.2.11.2

Message Sequence

7.0.0

NA

3.2.11.3

Detailed Description

7.0.0

NA

3.2.12

Basic VoLTE UE to VoLTE UE - Adding a video media stream - Terminating Side

7.0.0

NA

3.2.12.1

General

7.0.0

NA

3.2.12.2

Message Sequence

7.0.0

NA

3.2.12.3

Detailed Description

7.0.0

NA

3.2.13

Basic VoLTE UE to VoLTE UE - Removing a video media stream - Originating Side

7.0.0

NA

3.2.13.1

General

7.0.0

NA

3.2.13.2

Message Sequence

7.0.0

NA

3.2.13.3

Detailed Description

7.0.0

NA

3.2.14

Basic VoLTE UE to VoLTE UE - Removing a video media stream - Terminating Side

7.0.0

NA

3.2.14.1

General

7.0.0

NA

3.2.14.2

Message Sequence

7.0.0

NA

3.2.14.3

Detailed Description

7.0.0

NA

3.3

VoLTE-CS Interworking

7.0.0

NA

3.3.1

Basic VoLTE UE to CS Call Establishment - Originating Side

7.0.0

NA

3.3.1.1

General

7.0.0

NA

3.3.1.2

Message Sequence

7.0.0

NA

3.3.1.3

Detailed Description

7.0.0

NA

3.3.2

Basic VoLTE UE to CS Call Establishment -- Terminating Side

7.0.0

NA

3.3.2.1

General

7.0.0

NA

3.3.2.2

Message Sequence

7.0.0

NA

3.3.2.3

Detailed Description

7.0.0

NA

3.3.3

Basic VoLTE UE to CS Call Clearing - Initiated

7.0.0

NA

3.3.3.1

General

7.0.0

NA

3.3.3.2

Message Sequence

7.0.0

NA

3.3.3.3

Detailed Description

7.0.0

NA

3.3.4

Basic VoLTE UE to CS Call Clearing - Received

7.0.0

NA

3.3.4.1

General

7.0.0

NA

3.3.4.2

Message Sequence

7.0.0

NA

3.3.4.3

Detailed Description

7.0.0

NA

3.4

Supplementary Services

7.0.0

NA

3.4.1

General

7.0.0

XCAP is not supported.

See relevant PICS for individual service compliance.

3.5

ENUM/DS

7.0.0

NA

3.5.1

General

7.0.0

NA

3.5.2

Number Portability

7.0.0

NA

3.5.3

IP Service Routing

7.0.0

NA

3.5.4

Number Resolution

7.0.0

NA

3.5.5

ENUM

7.0.0

Note that ECAS 7.0.0 does not provide an ENUM service (or ENUM client).

3.5.5.1

ENUM Network Impact

7.0.0

NA

3.5.5.2

ENUM Functionality

7.0.0

NA

3.5.5.3

ENUM Registry Architecture

7.0.0

NA

3.5.5.4

Internal ENUM Registries

7.0.0

NA

3.6

Diameter Signalling

7.0.0

NA

3.6.1

General

7.0.0

See "RFC 3588 Compliance".

3.6.2

Diameter Agents

7.0.0

NA

3.6.3

Diameter Transport

7.0.0

NA

3.6.4

Diameter Peer Discovery

7.0.0

Only manual configuration of peers is supported.

3.6.5

Diameter Capability Exchange

7.0.0

NA

3.6.6

Diameter Routing

7.0.0

NA

3.7

Traffic Management and Policy

7.0.0

Note that ECAS 7.0.0 is not a PCRF or PCEF

3.7.1

General

7.0.0

NA

3.7.2

Policy and Charging Control

7.0.0

NA

3.7.3

DiffServ

7.0.0

NA

3.7.4

Mapping between QCI and DiffServ

7.0.0

NA

3.8

Session Border Controllers

7.0.0

NA

3.9

Emergency Call

7.0.0

NA

3.10

Lawful Intercept

7.0.0

NA

3.11

Security

7.0.0

NA

3.11.1

General

7.0.0

NA

3.11.2

Security Gateway

7.0.0

NA

3.11.3

IMS Media Plane Security

7.0.0

NA

3.12

SMS over IP

7.0.0

Not supported

3.13

Support of Legacy Proprietary CS Services

7.0.0

NA

3.14

Complementing VoLTE with 2G/3G Voice

7.0.0

NA

3.14.1

SRVCC

7.0.0

See IR 64 PICS

3.14.2

PS Handover

7.0.0

Not supported

3.14.3

IMS Service Centralization and Continuity

7.0.0

See IR 64 PICS (and note that Ut is not supported)

3.15

Charging

7.0.0

See "3GPP_TS_32.260 Compliance" PICS.

3.16

Codecs

7.0.0

NA

3.17

IP Version & Transport

7.0.0

NA

3.18

Home eNodeB (HeNB)

7.0.0

NA

3.19

Interworking with CAMEL/IN Services

7.0.0

A legacy CAP based interface is not supported.

4

VoLTE Implementation - Interconnect

7.0.0

NA

4.1

General

7.0.0

Ut interface is not supported

4.2

VoLTE Interconnect

7.0.0

NA

4.2.1

Basic VoLTE UE to Peer IMS Voice Call Establishment - Originating Side

7.0.0

NA

4.2.1.1

General

7.0.0

NA

4.2.1.2

Message Sequence

7.0.0

NA

4.2.1.3

Detailed Description

7.0.0

NA

4.2.2

Basic VoLTE UE to Peer IMS Voice Call Establishment - Terminating Side

7.0.0

NA

4.2.2.1

General

7.0.0

NA

4.2.2.2

Message Sequence

7.0.0

NA

4.2.2.3

Detailed Description

7.0.0

NA

4.2.3

Basic VoLTE UE to Peer IMS Voice Call Teardown - Initiated

7.0.0

NA

4.2.3.1

General

7.0.0

NA

4.2.3.2

Message Sequence

7.0.0

NA

4.2.3.3

Detailed Description

7.0.0

NA

4.2.4

Basic VoLTE UE to Peer IMS Voice Call Teardown - Received

7.0.0

NA

4.2.4.1

General

7.0.0

NA

4.2.4.2

Message Sequence

7.0.0

NA

4.2.4.3

Detailed Description

7.0.0

NA

4.2.5

Basic VoLTE UE to Peer IMS Multimedia (Voice/Video) Call Establishment - Originating Side

7.0.0

NA

4.2.5.1

General

7.0.0

NA

4.2.5.2

Message Sequence

7.0.0

NA

4.2.5.3

Detailed Description

7.0.0

NA

4.2.6

Basic VoLTE UE to Peer IMS Multimedia (Voice/Video) Call Establishment - Terminating Side

7.0.0

NA

4.2.6.1

General

7.0.0

NA

4.2.6.2

Message Sequence

7.0.0

NA

4.2.6.3

Detailed Description

7.0.0

NA

4.2.7

Basic VoLTE UE to Peer IMS Multimedia (Voice/Video) Call Clearing - Initiated

7.0.0

NA

4.2.7.1

General

7.0.0

NA

4.2.7.2

Message Sequence

7.0.0

NA

4.2.7.3

Detailed Description

7.0.0

NA

4.2.8

Basic VoLTE UE to Peer IMS Multimedia (Voice/Video) Call Clearing - Received

7.0.0

NA

4.2.8.1

General

7.0.0

NA

4.2.8.2

Message Sequence

7.0.0

NA

4.2.8.3

Detailed Description

7.0.0

NA

4.2.9

Basic VoLTE UE to Peer IMS - Adding a video media stream

7.0.0

NA

4.2.9.1

General

7.0.0

NA

4.2.9.2

Message Sequence

7.0.0

NA

4.2.9.3

Detailed Description

7.0.0

NA

4.2.10

Basic VoLTE UE to Peer IMS - Removing a video media stream

7.0.0

NA

4.2.10.1

General

7.0.0

NA

4.2.10.2

Message Sequence

7.0.0

NA

4.2.10.3

Detailed Description

7.0.0

NA

4.3

Bi-lateral Interconnect

7.0.0

NA

4.3.1

Physical Configuration of Bi-lateral Interconnect

7.0.0

NA

4.3.2

Usage of ENUM/DS

7.0.0

OCECAS does not have an ENUM client. However, Sh and REST/SOAP queries are available (for E.164/URI translation) during call control.

4.3.3

Usage of Session Border Controllers

7.0.0

NA

4.3.3.1

General

7.0.0

NA

4.3.3.2

Control Plane

7.0.0

NA

4.3.3.3

Media Plane

7.0.0

NA

4.4

IPX-Based Interconnect

7.0.0

NA

4.4.1

Configuration of IPX-based Interconnect

7.0.0

NA

4.4.2

Usage of ENUM/DS

7.0.0

Note that OCECAS does not provide an ENUM service (or ENUM client).

4.4.3

Usage of Session Border Controllers

7.0.0

NA

4.4.3.1

General

7.0.0

NA

4.4.3.2

Control Plane

7.0.0

NA

4.4.3.3

Media Plane

7.0.0

NA

4.5

CS Interconnect

7.0.0

NA

4.6

Charging

7.0.0

NA

5

VoLTE Implementation - Roaming

7.0.0

NA

5.1

General

7.0.0

Ut interface is not supported

5.2

VoLTE Roaming Basic Call Flows

7.0.0

NA

5.2.1

Roaming VoLTE UE Attachment and IMS Registration

7.0.0

NA

5.2.1.1

General

7.0.0

NA

5.2.1.2

Message Sequence

7.0.0

A SIP SUBSCRIBE message is never sent by the TAS. (OCECAS does not need to know about changes to the public user identity)

5.2.1.3

Detailed Description

7.0.0

NA

5.2.1.3.1

Roaming VoLTE UE Attach

7.0.0

NA

5.2.1.3.2

Roaming VoLTE UE Initial IMS Registration

7.0.0

NA

5.2.2

Roaming VoLTE UE Initiated Detach and IMS Deregistration

7.0.0

NA

5.2.2.1

General

7.0.0

NA

5.2.2.2

Message Sequence

7.0.0

NA

5.2.2.3

Detailed Description

7.0.0

NA

5.2.2.3.1

IMS Deregistration (Roaming)

7.0.0

NA

5.2.2.3.2

Roaming VoLTE UE Detach

7.0.0

NA

5.2.3

Roaming VoLTE UE to VoLTE Voice Call Establishment - Originating Side

7.0.0

NA

5.2.3.1

General

7.0.0

NA

5.2.3.2

Message Sequence

7.0.0

NA

5.2.3.3

Detailed Description

7.0.0

NA

5.2.4

Roaming VoLTE UE to VoLTE UE Voice Call Establishment - Terminating Side

7.0.0

NA

5.2.4.1

General

7.0.0

NA

5.2.4.2

Message Sequence

7.0.0

NA

5.2.4.3

Detailed Description

7.0.0

NA

5.2.5

Roaming VoLTE UE to VoLTE UE Voice Call Clearing - Initiated

7.0.0

NA

5.2.5.1

General

7.0.0

NA

5.2.5.2

Message Sequence

7.0.0

NA

5.2.5.3

Detailed Description

7.0.0

NA

5.2.6

Roaming VoLTE UE to VoLTE Voice Call Clearing - Received

7.0.0

NA

5.2.6.1

General

7.0.0

NA

5.2.6.2

Message Sequence

7.0.0

NA

5.2.6.3

Detailed Description

7.0.0

NA

5.2.7

Roaming VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Establishment - Originating Side

7.0.0

NA

5.2.7.1

General

7.0.0

NA

5.2.7.2

Message Sequence

7.0.0

NA

5.2.7.3

Detailed Description

7.0.0

NA

5.2.8

Roaming VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Establishment - Terminating Side

7.0.0

NA

5.2.8.1

General

7.0.0

NA

5.2.8.2

Message Sequence

7.0.0

NA

5.2.8.3

Detailed Description

7.0.0

NA

5.2.9

Roaming VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Clearing - Initiated

7.0.0

NA

5.2.9.1

General

7.0.0

NA

5.2.9.2

Message Sequence

7.0.0

NA

5.2.9.3

Detailed Description

7.0.0

NA

5.2.10

Roaming VoLTE UE to VoLTE UE Multimedia (Voice/Video) Call Clearing - Received

7.0.0

NA

5.2.10.1

General

7.0.0

NA

5.2.10.2

Message Sequence

7.0.0

NA

5.2.10.3

Detailed Description

7.0.0

NA

5.2.11

Roaming VoLTE UE to VoLTE - Adding a video media stream

7.0.0

NA

5.2.11.1

General

7.0.0

NA

5.2.11.2

Message Sequence

7.0.0

NA

5.2.11.3

Detailed Description

7.0.0

NA

5.2.12

Roaming VoLTE UE to VoLTE - Removing a video media stream

7.0.0

NA

5.2.12.1

General

7.0.0

NA

5.2.12.2

Message Sequence

7.0.0

NA

5.2.12.3

Detailed Description

7.0.0

NA

5.2.13.3.1

Video Stream removed by roaming UE

7.0.0

NA

5.2.13.3.2

Video Stream removed by other party

7.0.0

NA

5.3

Roaming Architecture for Voice over IMS with Local break-out (RAVEL)

7.0.0

NA

5.4

Optimal Media Routing

7.0.0

NA

5.5

Diameter Signalling

7.0.0

Only manual configuration of peers is supported.

5.6

Traffic Management and Policy

7.0.0

NA

5.7

Session Border Controllers

7.0.0

NA

5.8

IMS Emergency Call

7.0.0

NA

5.9

Lawful Intercept

7.0.0

NA

5.10

Security

7.0.0

NA

5.11

Charging

7.0.0

NA

6

Intra LTE Handover

7.0.0

NA

6.1

General

7.0.0

The TAS (OCECAS) is not involved in these flows.

6.2

Intra LTE HO

7.0.0

NA

6.2.1

X2 Based Handover - no SGW relocation

7.0.0

NA

6.2.1.1

General

7.0.0

NA

6.2.1.2

Message Sequence

7.0.0

NA

6.2.1.3

Detailed Description

7.0.0

NA

6.2.2

X2-based HO - SGW relocation

7.0.0

NA

6.2.2.1

General

7.0.0

NA

6.2.2.2

Message Sequence

7.0.0

NA

6.2.2.3

Detailed Description

7.0.0

NA

6.2.3

S1 based HO - no SGW/MME relocation

7.0.0

NA

6.2.3.1

General

7.0.0

NA

6.2.3.2

Message Sequence

7.0.0

NA

6.2.3.3

Detailed Description

7.0.0

NA

6.2.4

S1 based HO - SGW relocation

7.0.0

NA

6.2.4.1

General

7.0.0

NA

6.2.4.2

Message Sequence

7.0.0

NA

6.2.4.3

Detailed Description

7.0.0

NA

6.2.5

S1 based HO - MME relocation

7.0.0

NA

6.2.5.1

General

7.0.0

NA

6.2.5.2

Message Sequence

7.0.0

NA

6.2.5.3

Detailed Description

7.0.0

NA

6.2.6

S1 based HO - MME & SGW relocation

7.0.0

NA

6.2.6.1

General

7.0.0

NA

6.2.6.2

Message Sequence

7.0.0

NA

6.2.6.3

Detailed Description

7.0.0

NA

7

Enhanced SRVCC (e-SRVCC)

7.0.0

See "3GPP_TS_23.237 Compliance" PICS

7.1

eSRVCC Architecture

7.0.0

Note that Ut is not supported.

7.2

eSRVCC Functional Node Description

7.0.0

NA

7.2.1

Universal Terrestrial Access Network (UTRAN)

7.0.0

Noted

7.2.2

SGSN

7.0.0

Noted

7.2.3

Mobile Switching Centre (MSC)

7.0.0

Noted

7.2.4

ATCF/ATGW (Access Transfer Control Function/Access Transfer Gateway)

7.0.0

Noted

7.2.5

SCC AS (Service Centralisation and Continuity Application Server)

7.0.0

See "3GPP_TS_23.292 Compliance" PICS

7.3

eSRVCC Interface Description

7.0.0

Noted

7.3.1

Uu Interface (UE - RNS)

7.0.0

Noted

7.3.2

Iu-CS (RNS - MSC)

7.0.0

Noted

7.3.3

Iu-PS (RNS - SGSN)

7.0.0

Noted

7.3.4

Gn Interface (SGSN - MME/PGW)

7.0.0

Noted

7.3.5

Gr Interface (SGSN - HSS)

7.0.0

Noted

7.3.6

Sv (MSC - MME)

7.0.0

Noted

7.3.7

I2 (MSC - ATCF)

7.0.0

Noted

7.3.8

D (MSC - HLR(HSS))

7.0.0

Noted

7.4

eSRVCC Call Flows

7.0.0

NA

7.4.1

Attachment and IMS Registration

7.0.0

NA

7.4.1.1

General

7.0.0

NA

7.4.1.2

Message Sequence

7.0.0

NA

7.4.1.3

Detailed Description

7.0.0

NA

7.4.1.3.1

UE LTE Attach

7.0.0

NA

7.4.1.3.2

UE IMS Registration

7.0.0

NA

7.4.2

UE Voice Call Establishment - Originating Side

7.0.0

NA

7.4.2.1

General

7.0.0

NA

7.4.2.2

Message Sequence

7.0.0

NA

7.4.2.3

Detailed Description

7.0.0

NA

7.4.3

UE Voice Call Establishment - Terminating Side

7.0.0

NA

7.4.3.1

General

7.0.0

NA

7.4.3.2

Message Sequence

7.0.0

NA

7.4.3.3

Detailed Description

7.0.0

NA

7.4.4

PS-CS SRVCC

7.0.0

NA

7.4.4.1

General

7.0.0

NA

7.4.4.2

Message Sequence

7.0.0

NA

7.4.4.3

Detailed Description

7.0.0

NA

8

Implementation Guidelines

7.0.0

Noted


IR.64 Compliance

This section describes the following:

IR.64_V10 Compliance

Table 2-2 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document IR.64 version 10, "IR.64 IMS Service Centralization and Continuity Guidelines, Version 10.0."

Table 2-2 GSMA_IR.64_V10 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

NA

1.1

Overview

7.0.0

NA

1.2

Scope

7.0.0

NA

1.3

Abbreviations

7.0.0

NA

1.4

References

7.0.0

NA

2

Service Centralization in the IMS

7.0.0

NA

2.1

General

7.0.0

Noted

2.1.1

Anchoring when using PS access

7.0.0 (Partial)

TS 23.237 Support:

6.2.1.4 Originating sessions for (v)SRVCC that use ATCF enhancements

6.2.2.5 Terminating sessions for (v)SRVCC that use ATCF enhancements

2.1.2

Anchoring when using CS access

7.0.0

NA

2.2

Service Data

7.0.0

NA

3

Terminated Access Domain Selection

7.0.0

NA

4

SRVCC

7.0.0

NA

4.1

General

7.0.0 (Partial)

MSC Server assisted mid-call feature is not supported.

4.2

Impacted entities

7.0.0

Noted

4.3

SRVCC Architecture

7.0.0

NA

4.3.1

Overview

7.0.0 (Partial)

TS 24.237 Support is summarized as follows:

A.3.3 Signalling flows for registration with SRVCC enhancements

A.4.2 Session origination with PS to CS SRVCC enhancements

A.6.2 PS-CS access transfer: PS-CS

A.16 Signalling flows for PS to CS SRVCC session transfer for IMS emergency session (OCECAS is not involved in emergency sessions).

A.18.2 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and without media anchored

A.18.3 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and with media anchored

A.18.6 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and session traverses IBCF

A.19 Signalling flows for vSRVCC

The following flows are not supported:

A.3.2 Signalling flows for multiple registration for service continuity

A.3.4 Signalling flows for registration with SRVCC enhancements from UE supporting CS to PS SRVCC

A.3.5 Signalling flows for UE attaching to CS domain

A.3.6 Signalling flows for UE attaching to CS domain

A.4.3 Call origination prior to CS to PS SRVCC

A.5.2 Call termination prior to CS to PS SRVCC

A.6.1 PS-CS access transfer: CS-PS

A.7 Signalling flows for PS-PS transfer

A.8 Signalling flows for PS-PS access transfer in conjunction with PS-CS access transfer

A.9 Signalling flows for media adding/deleting for access transfer

A.15 Signalling flows for MSC server assisted mid-call feature

A.17 Signalling flows for PS to CS SRVCC in Alerting State

4.3.1

Overview (Contd)

7.0.0 (Partial)

A.18.4 Session transfer for originating call is in alerting phase using PS to CS SRVCC procedure with ATCF: PS to CS

A.18.5 Signalling flows for PS to CS Access Transfer: SRVCC enhancements using ATCF with MSC server assisted mid- call feature and ATCF anchored

A.20 Signalling flows for CS to PS Access Transfer: using CS to PS SRVCC

4.4

Support of mid-call state and calls in alerting state

Non-compliant

IR.92 A.3 Note (1) states: The mechanisms to perform transfer of additional session / held state / conference call state / alerting calls are out of scope of the present version of this profile.

4.4.1

Overview

Non-compliant

See IR.92 A.3 Note (1)

4.4.2

UE impact

Non-compliant

IR.92 A.3 Note (1)

4.4.3

Network impacts

Non-compliant

IR.92 A.3 Note (1)

4.5

SRVCC Architecture for emergency calls

7.0.0

OCECAS does not provide an Emergency Access Transfer Function.

4.5.1

UE impacts

7.0.0

NA

4.5.2

Network impacts

7.0.0

NA

4.6

Handling of non-voice media during SRVCC

7.0.0 (Partial)

Assuming that the system can determine the target access type (GERAN non DTM v. GERAN with DTM) from the HSS or the access transfer INVITE from the S-CSCF, then the system will allow removal of media from the session (SDP).

Annex A (informative)

Issues with initial deployments for Service Centralization in the IMS

7.0.0

Noted

A.1

General

7.0.0

Noted

A.2

Issue 1: Anchoring of all calls in IMS

7.0.0

Noted

A.2.1

Overview

7.0.0

Noted

A.2.2

Guidelines to resolve issue 1

7.0.0

Noted

A.3

Issue 2: Support for MSC Server enhanced for ICS

7.0.0

Noted

A.3.1

Overview

7.0.0

Noted

A.3.2

Guidelines to resolve issue 2

7.0.0

Noted

A.4

Issue 3: Use of CAMEL home routing during roaming scenario

7.0.0

Noted

A.4.1

Overview

7.0.0

Noted

A.4.2

Guidelines to resolve issue 3

7.0.0

Noted

A.5

Issue 4: Deployment of SCC AS

7.0.0

Noted

A.5.1

Overview

7.0.0

Noted

A.5.2

Guidelines to resolve issue 4

7.0.0

Noted

 

Document Management

7.0.0

NA


IR.64_V6.0 Compliance

Table 2-3 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document IR.64, Version 6.0, "IMS Service Centralization and Continuity Guidelines, Version 6.0."

Table 2-3 GSMA IR.64 v6.0 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

NA

1.1

Overview

7.0.0

NA

1.2

Scope

7.0.0

NA

1.3

Abbreviations

7.0.0

NA

1.4

References

7.0.0

NA

2

Service Centralization in the IMS

7.0.0

NA

2.1

General

7.0.0

Noted

2.1.1

Anchoring when using PS access

7.0.0 (Partial)

TS 23.237 Support:

6.2.1.4 Originating sessions for (v)SRVCC that use ATCF enhancements

6.2.2.5 Terminating sessions for (v)SRVCC that use ATCF enhancements

2.1.2

Anchoring when using CS access

7.0.0

NA

3

Terminated Access Domain Selection

7.0.0

NA

4.1

General

7.0.0

Noted

4.2

Impacted entities

7.0.0

Noted

4.3

SRVCC Architecture

7.0.0

NA

4.3.1

Overview

7.0.0 (Partial)

TS 24.237 Support is summarized as follows:

A.3.3 Signalling flows for registration with SRVCC enhancements

A.4.2 Session origination with PS to CS SRVCC enhancements

A.6.2 PS-CS access transfer: PS-CS

A.16 Signalling flows for PS to CS SRVCC session transfer for IMS emergency session (OCECAS is not involved in emergency sessions).

A.18.2 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and without media anchored.

A.18.3 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and with media anchored.

A.18.6 Signalling flows for PS to CS Access Transfer: PS to CS SRVCC enhancements using ATCF and session traverses IBCF.

A.19 Signalling flows for vSRVCC

The following flows are not supported:

A.3.2 Signalling flows for multiple registration for service continuity

A.3.4 Signalling flows for registration with SRVCC enhancements from UE supporting CS to PS SRVCC

A.3.5 Signalling flows for UE attaching to CS domain.

A.3.6 Signalling flows for UE attaching to CS domain.

A.4.3 Call origination prior to CS to PS SRVCC

A.5.2 Call termination prior to CS to PS SRVCC

A.6.1 PS-CS access transfer: CS-PS

A.7 Signalling flows for PS-PS transfer

A.8 Signalling flows for PS-PS access transfer in conjunction with PS-CS access transfer

A.9 Signalling flows for media adding/deleting for access transfer

A.15 Signalling flows for MSC server assisted mid-call feature

A.17 Signalling flows for PS to CS SRVCC in Alerting State

4.3.1 cont.

Overview (cont.)

7.0.0 (Partial)

A.18.4 Session transfer for originating call is in alerting phase using PS to CS SRVCC procedure with ATCF: PS to CS

A.18.5 Signalling flows for PS to CS Access Transfer: SRVCC enhancements using ATCF with MSC server assisted mid- call feature and ATCF anchored

A.20 Signalling flows for CS to PS Access Transfer: using CS to PS SRVCC

4.4

Support of mid-call state and calls in alerting state

Non-compliant

IR.92 A.3 Note (1) states: The mechanisms to perform transfer of additional session / held state / conference call state / alerting calls are out of scope of the present version of this profile.

This functionality is therefore considered out of scope for release 1.0

4.4.1

Overview

Non-compliant

See above IR.92 A.3 Note

4.4.2

UE impact

Non-compliant

See above IR.92 A.3 Note

4.4.3

Network impacts

Non-compliant

See above IR.92 A.3 Note

4.5

SRVCC Architecture for emergency calls

Non-compliant

There will be no explicit support for emergency calls.

4.5.1

UE impacts

7.0.0

Noted

4.5.2

Network impacts

7.0.0

Noted

4.6

Handling of non-voice media during SRVCC

7.0.0 (Partial)

Assuming that the system can determine the target access type (GERAN non DTM v. GERAN with DTM) from the HSS or the access transfer INVITE from the S-CSCF, then the system will allow removal of media from the session (SDP).

Annex A (informative)

Issues with initial deployments for Service Centralization in the IMS

7.0.0

Noted

A.1

General

7.0.0

Noted

A.2

Issue 1: Anchoring of all calls in IMS

7.0.0

Noted

A.2.1

Overview

7.0.0

Noted

A.2.2

Guidelines to resolve issue 1

7.0.0

Noted

A.3

Issue 2: Support for MSC Server enhanced for ICS

7.0.0

Noted

A.3.1

Overview

7.0.0

Noted

A.3.2

Guidelines to resolve issue 2

7.0.0

Noted

A.4

Issue 3: Use of CAMEL home routing during roaming scenario

7.0.0

Noted

A.5

Issue 4: Deployment of SCC AS

7.0.0

Noted

A.5.1

Overview

7.0.0

Noted

A.5.2

Guidelines to resolve issue 4

7.0.0

Noted

 

Document Management

7.0.0

NA


IR.92 Compliance

This section describes the following:

IR.92_V7.1 Compliance

Table 2-4 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document IR.92, Version 7.1, "IMS Profile for Voice and SMS, Version 7.1."

Table 2-4 GSMA_IR.92_V7.1 Compliance

Section Number Section Title Product Release Release caveats

1

General Introduction

7.0.0

NA

1.1

The IMS Profile for Voice and SMS

7.0.0

Noted

1.2

Relationship to existing standards

7.0.0

NA

1.2.1

3GPP specifications

7.0.0

Noted

1.3

Scope

7.0.0

Noted

1.4

Definition of Terms

7.0.0

Noted

1.5

Document Cross-References

7.0.0

Noted

2

IMS Feature Set

7.0.0

NA

2.1

General

7.0.0

Noted

2.2

Support of generic IMS functions

7.0.0

NA

2.2.1

SIP Registration Procedures

7.0.0 (Partial)

No support for following sections of 3GPP TS 24.229:

5.7.1.4 User identity verification at the AS

5.7.1.5 Request authorization

5.7.1.6 Event notification throttling

5.7.1.7.2 Translation of the numbers in a non-international format (not out-of-the-box, but it would be possible to configure this using Control-Flow activities).

5.7.1.8 GRUU assignment and usage

5.7.1.9 Use of ICSI and IARI values

5.7.1.10 Carrier selection (although this could be possible with extra Control-Flow and HSS configuration)

5.7.1.11 Tracing (although this could be possible with extra Control-Flow and HSS configuration)

5.7.1.12 Delivery of original destination identity (although this could be possible with extra Control-Flow configuration)

5.7.1.13 CPC and OLI (although this could be possible with extra Control-Flow configuration)

5.7.1.14 Emergency transactions (this is not needed for OCECAS use cases)

5.7.1.15 Protecting against attacks using 3xx responses

5.7.1.16 Support of Roaming Architecture for Voice over IMS with Local Breakout (although this could be possible with extra Control-Flow configuration)

5.7.1.17 Delivery of network provided location information (although this could be possible with extra Control-Flow and HSS configuration)

5.7.1.18 Delivery of MRB address information

5.7.1.19 Overload control

2.2.2

Authentication

Non-compliant

No support for 3GPP TS 24.229:

5.7.1.4 User identity verification at the AS .

Also need to consider any 3GPP TS 33.203 impacts.

2.2.3

Addressing

7.0.0

Context value branching feature allows control flow to detect different types of addressing.

2.2.4

Call Establishment and Termination

7.0.0 (Partial)

Partial support for 3GPP TS 24.229:

5.7.2 Application Server (AS) acting as terminating UA, or redirect server:

  • No manipulation of P-Charging-Vector header

  • No inclusion of Resource-Priority header

5.7.3 Application Server (AS) acting as originating UA:

  • No activity to generate initial outbound request

5.7.4 Application Server (AS) acting as a SIP proxy:

  • Not supported

5.7.5 Application Server (AS) performing 3rd party call control:

  • No support for initiating B2BUA

  • No manipulation of P-Charging-Vector header

  • No inclusion of Resource-Priority header

  • No support for session check using UPDATE

2.2.5

Forking

7.0.0

Noted

2.2.6

Tracing of Signalling

7.0.0

Noted

2.2.7

The use of Signalling Compression

7.0.0

Noted

2.2.8

Early media and announcements

7.0.0

Noted

2.3

Supplementary Services

7.0.0

NA

2.3.1

Supplementary Services Overview

7.0.0 (Partial)

No support for:

Message Waiting Indication 3GPP TS 24.606

Communication Waiting 3GPP TS 24.615

2.3.2

Supplementary Service Configuration

Non-compliant

XCAP not supported.

2.3.3

Ad-Hoc Multi Party Conference

7.0.0

NA

2.3.4

Communication Waiting

Non-compliant

Not supported

2.3.5

Message Waiting Indication

Non-compliant

Not supported

2.3.6

Originating Identification Restriction

7.0.0

NA

2.3.7

Terminating Identification Restriction

7.0.0

NA

2.3.8

Communication Diversion

7.0.0 (Partial)

media condition not supported Out-Of-The-Box (but possible through configuration)

2.3.9

Communication Barring

7.0.0

NA

2.4

Call Set-up Considerations

7.0.0

NA

2.4.1

SIP Precondition Considerations

7.0.0

Noted

2.4.2

Integration of resource management and SIP

7.0.0

NA

2.4.2.1

Loss of PDN connectivity

7.0.0

Noted

2.4.2.2

Void

7.0.0

NA

2.4.2.3

Loss of media bearer and Radio Connection

7.0.0

Noted

2.4.3

Voice Media Considerations

7.0.0

Noted

2.4.4

Multimedia Considerations

7.0.0

Noted

2.5

SMS over IP

Non-compliant

Not supported

3

IMS Media

7.0.0

NA

3.1

General

7.0.0

Noted

3.2

Voice Media

7.0.0

NA

3.2.1

Codecs

7.0.0

Noted

3.2.2

RTP Profile and SDP Considerations

7.0.0

NA

3.2.2.1

RTP Profile

7.0.0

Noted

3.2.2.2

SDP Offer Considerations

7.0.0

NA

3.2.2.3

SDP Answer Considerations

7.0.0

NA

3.2.3

Data Transport

7.0.0

Noted

3.2.4

RTCP Usage

7.0.0

NA

3.2.5

AMR Payload Format Considerations

7.0.0

Noted

3.2.6

Jitter Buffer Management Considerations

7.0.0

Noted

3.2.7

Front End Handling

7.0.0

Noted

3.3

DTMF Events

7.0.0

Noted

4

Radio and Packet Core Feature Set

7.0.0

NA

4.0

General

7.0.0

Noted

4.1

Robust Header Compression

7.0.0

Noted

4.2

LTE Radio Capabilities

7.0.0

NA

4.2.1

Radio Bearers

7.0.0

Noted

4.2.2

DRX Mode of Operation

7.0.0

Noted

4.2.3

RLC configurations

7.0.0

Noted

4.2.4

GBR and NGBR Services, GBR Monitoring Function

7.0.0

Noted

4.3

Bearer Management

7.0.0

NA

4.3.1

EPS Bearer Considerations for SIP Signalling and XCAP

7.0.0

Noted

4.3.2

EPS Bearer Considerations for Voice

7.0.0

Noted

4.4

P-CSCF Discovery

7.0.0

NA

5

Common Functionalities

7.0.0

NA

5.1

IP Version

7.0.0

NA

5.2

Emergency Service

7.0.0

NA

5.2.1

General

7.0.0 (Partial)

AS does not support generation of emergency transactions as per 3GPP TS 24.229 section 5.7.1.14

5.3

Roaming Considerations

7.0.0

Noted

Annex A

Complementing IMS with CS

7.0.0

NA

A.1

General

7.0.0

Noted

A.2

Domain Selection

7.0.0

Noted

A.3

SR-VCC

7.0.0 (Partial)

See "IR.64 Compliance".

A.4

IMS Voice service settings management when using CS access

7.0.0

Noted

A.5

Emergency Service

7.0.0 (Partial)

See 5.2

No support for SR-VCC for IMS emergency sessions (3GPP TS 24.237).

No support for SIP instance ID (3GPP TS 24.237)

A.6

Roaming Considerations

7.0.0

Noted

A.7

SMS Support

Non-compliant

Not supported

Annex B

Features needed in certain regions

7.0.0

NA

B.1

General

7.0.0

Noted

B.2

Global Text Telephony

7.0.0

Noted

B.3

Service Specific Access Control

7.0.0

Noted

 

Document Management

7.0.0

NA


IR.92_V8.0 Compliance

Table 2-5 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document IR.92, Version 8.0, "IMS Profile for Voice and SMS, Version 8.0."

Table 2-5 GSMA_IR.92_V8.0 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

NA

1.1

Overview

7.0.0

Noted

1.2

Relationship to existing standards

7.0.0

NA

1.2.1

3GPP specifications

7.0.0

Noted

1.3

Scope

7.0.0

Noted

1.4

Definition of Terms

7.0.0

Noted

1.5

Document Cross-References

7.0.0

Noted

2

IMS Feature Set

7.0.0

NA

2.1

General

7.0.0

Noted

2.2

Support of generic IMS functions

7.0.0

NA

2.2.1

SIP Registration Procedures

7.0.0 (Partial)

No support for following sections of 3GPP TS 24.229:

5.7.1.4 User identity verification at the AS (only trusted users are expected)

5.7.1.5 Request authorization

5.7.1.6 Event notification throttling

5.7.1.7.2 Translation of the numbers in a non-international format (not out-of-the-box, but it would be possible to configure this using Control-Flow activities).

5.7.1.8 GRUU assignment and usage

5.7.1.9 Use of ICSI and IARI values

5.7.1.10 Carrier selection (although this is possible with extra Control-Flow and HSS configuration)

5.7.1.11 Tracing (although this is possible with extra Control-Flow and HSS configuration)

5.7.1.12 Delivery of original destination identity (although this is possible with extra Control-Flow configuration)

5.7.1.13 CPC and OLI (although this is possible with extra Control-Flow configuration)

5.7.1.14 Emergency transactions (this is not needed for OCECAS use cases)

5.7.1.15 Protecting against attacks using 3xx responses

5.7.1.16 Support of Roaming Architecture for Voice over IMS with Local Breakout

5.7.1.17 Delivery of network provided location information (although this could be possible with extra Control-Flow and HSS configuration)

5.7.1.18 Delivery of MRB address information

5.7.1.19 Overload control

2.2.2

Authentication

Non-compliant

No support for 3GPP TS 24.229:

5.7.1.4 User identity verification at the AS (only trusted users are expected)

2.2.3

Addressing

7.0.0

Context value branching feature allows control flow to detect different types of addressing.

2.2.4

Call Establishment and Termination

7.0.0 (Partial)

Partial support for 3GPP TS 24.229:

5.7.2 Application Server (AS) acting as terminating UA, or redirect server:

  • No manipulation of P-Charging-Vector header

  • No inclusion of Resource-Priority header

5.7.3 Application Server (AS) acting as originating UA:

  • No activity to generate initial outbound request

5.7.4 Application Server (AS) acting as a SIP proxy:

  • Not supported 5.7.5 Application Server (AS) performing 3rd party call control

  • No support for initiating B2BUA - No manipulation of P-Charging-Vector header

  • No inclusion of Resource-Priority header

  • No support for session check using UPDATE

2.2.5

Forking

7.0.0

Noted

2.2.6

The use of Signalling Compression

7.0.0

Noted

2.2.7

Early media and announcements

7.0.0

Noted

2.3

Supplementary Services

7.0.0

NA

2.3.1

Supplementary Services Overview

7.0.0 (Partial)

No support for:

Message Waiting Indication 3GPP TS 24.606

Communication Waiting 3GPP TS 24.615

2.3.2

Supplementary Service Configuration

Non-compliant

XCAP not supported. (Configuration is possible via a REST interface)

2.3.3

Ad-Hoc Multi Party Conference

7.0.0

NA

2.3.4

Communication Waiting

Non-compliant

Not supported

2.3.5

Message Waiting Indication

Non-compliant

Not supported

2.3.6

Originating Identification Restriction

7.0.0

NA

2.3.7

Terminating Identification Restriction

7.0.0

NA

2.3.8

Communication Diversion

7.0.0 (Partial)

Media condition not supported Out-Of-The-Box (but possible through configuration)

2.3.9

Communication Barring

7.0.0

NA

2.4

Call Set-up Considerations

7.0.0

NA

2.4.1

SIP Precondition Considerations

7.0.0

Noted

2.4.2

Integration of resource management and SIP

7.0.0

NA

2.4.2.1

Loss of PDN connectivity

7.0.0

Noted

2.4.2.2

Void

7.0.0

NA

2.4.2.3

Loss of media bearer and Radio Connection

7.0.0

Noted

2.4.3

Voice Media Considerations

7.0.0

Noted

2.4.4

Multimedia Considerations

7.0.0

Noted

2.5

SMS over IP

Non-compliant

Not supported

3

IMS Media

7.0.0

NA

3.1

General

7.0.0

Noted

3.2

Voice Media

7.0.0

NA

3.2.1

Codecs

7.0.0

Noted

3.2.2

RTP Profile and SDP Considerations

7.0.0

NA

3.2.2.1

RTP Profile

7.0.0

Noted

3.2.2.2

SDP Offer Considerations

7.0.0

NA

3.2.2.3

SDP Answer Considerations

7.0.0

NA

3.2.3

Data Transport

7.0.0

Noted

3.2.4

RTCP Usage

7.0.0

NA

3.2.5

AMR Payload Format Considerations

7.0.0

Noted

3.2.6

Jitter Buffer Management Considerations

7.0.0

Noted

3.2.7

Front End Handling

7.0.0

Noted

3.3

DTMF Events

7.0.0

Noted

4

Radio and Packet Core Feature Set

7.0.0

NA

4.0

General

7.0.0

Noted

4.1

Robust Header Compression

7.0.0

Noted

4.2

LTE Radio Capabilities

7.0.0

NA

4.2.1

Radio Bearers

7.0.0

Noted

4.2.2

DRX Mode of Operation

7.0.0

Noted

4.2.3

RLC configurations

7.0.0

Noted

4.2.4

GBR and NGBR Services, GBR Monitoring Function

7.0.0

Noted

4.3

Bearer Management

7.0.0

NA

4.3.1

EPS Bearer Considerations for SIP Signalling and XCAP

7.0.0

Noted

4.3.2

EPS Bearer Considerations for Voice

7.0.0

Noted

4.4

P-CSCF Discovery

7.0.0

NA

5

Common Functionalities

7.0.0

NA

5.1

IP Version

7.0.0

NA

5.2

Emergency Service

7.0.0

NA

5.2.1

General

7.0.0 (Partial)

AS does not support generation of emergency transactions as per 3GPP TS 24.229 section 5.7.1.14

5.3

Roaming Considerations

7.0.0

Noted

Annex A

Complementing IMS with CS

7.0.0

 

A.1

General

7.0.0

Noted

A.2

Domain Selection

7.0.0

Noted

A.3

SR-VCC

7.0.0 (Partial)

See "IR.64 Compliance".

A.4

IMS Voice service settings management when using CS access

7.0.0

Noted

A.5

Emergency Service

7.0.0 (Partial)

See 5.2:

No support for SR-VCC for IMS emergency sessions (3GPP TS 24.237).

No support for SIP instance ID (3GPP TS 24.237)

A.6

Roaming Considerations

7.0.0

Noted

A.7

SMS Support

Non-compliant

Not supported

A.8

Call Waiting in the CS domain

Non-compliant

Not supported

Annex B

Features needed in certain regions

7.0.0

NA

B.1

General

7.0.0

Noted

B.2

Global Text Telephony

7.0.0

Noted

B.3

Service Specific Access Control

7.0.0

Noted

Document Management

Document Management

7.0.0

NA


IR.94_V5.0 Compliance

Table 2-6 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the GSMA document IR.94, Version 5.0, "IMS Profile for Conversational Video Service, Version 5.0."

Table 2-6 GSMA_IR.94 v5.0 Compliance

Section Number Section Title Product Release Release caveats

1

Introduction

7.0.0

NA

1.1

Overview

7.0.0

Noted

1.2

Relationship to 3GPP Specifications

7.0.0

Noted

1.3

Scope

7.0.0

Noted

1.4

Definition of Terms

7.0.0

Noted

1.5

Document Cross-References

7.0.0

Noted

2

IMS Feature Set

7.0.0

NA

2.1

General

7.0.0

Noted

2.2

Support of Generic IMS functions

7.0.0

NA

2.2.1

SIP Registration Procedures

7.0.0

Existing String and Branch activities can process RFC3840 tags if required (but not all are configured out-of-the-box).

2.2.2

Call Establishment and Termination

7.0.0

NA

2.2.3

Early Media

7.0.0

Noted

2.3

Supplementary Services

7.0.0

NA

2.3.1

General

7.0.0

Noted

2.3.2

Communication Hold

7.0.0

NA

2.3.3

Ad-Hoc Multi Party Conference

7.0.0

Noted

2.4

Call Set-up Considerations for Calls with Video Media

7.0.0

NA

2.4.1

Integration of Resource Management and SIP

7.0.0

Noted

2.4.2

Video Media Considerations

7.0.0

Noted

3

IMS Media

7.0.0

NA

3.1

General

7.0.0

Noted

3.2

Voice Media

7.0.0

Noted

3.3

Video Media

7.0.0

NA

3.3.1

Video Codec

7.0.0

Noted

3.3.2

RTP Profile and Data Transport

7.0.0

Noted

3.3.3

RTCP Usage

7.0.0

Noted

3.3.4

RTP Payload Format Considerations for Video

7.0.0

Noted

4

Radio and Packet Core Feature Set

7.0.0

NA

4.1

General

7.0.0

Noted

4.2

Bearer Considerations for Video

7.0.0

NA

4.2.1

E-UTRAN

7.0.0

Noted

4.2.2

UTRAN

7.0.0

Noted

4.3

LTE Radio Capabilities

7.0.0

Noted

4.4

HSPA Radio Capabilities

7.0.0

Noted

Annex A

Complementing IMS with CS

7.0.0

NA

A.1

General

7.0.0

Noted

A.2

SR-VCC

7.0.0

See 23.237, 24.237, "IR.64 Compliance"

 

Document Management

7.0.0

NA