1 3GPP Compliance

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

It covers the following statements:

• 3GPP 23 Series Compliance

• 3GPP 24 Series Compliance

• 3GPP 29Series Compliance

• 3GPP 32 Series Compliance

3GPP 23 Series Compliance

This section describes the following:

• 3GPP_TS_23.237 Compliance

• 3GPP_TS_23.292 Compliance

3GPP_TS_23.237 Compliance

Table 1-1 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 23.237 (v12.8.0), "IP Multimedia Subsystem (IMS) Service Continuity, Stage 2."

Table 1-1 PICS for 3GPP TS 23.237

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	High Level principles and architectural requirements	7.0.0	NA
4.1	Basic Assumptions	7.0.0	NA
4.1.0	General	7.0.0	Noted
4.1.1	PS-CS Access Transfer	7.0.0	Noted
4.1.2	PS-PS Access Transfer	7.0.0	Noted
4.1.3	Inter-UE Transfer	7.0.0	Noted
4.2	Architectural Requirements	7.0.0	NA
4.2.1	General	7.0.0	NA
4.2.2	Access Transfer Requirements	7.0.0 (Partial)	OCECAS does not update the operator policy in the UE
4.2.3	IUT Requirements	Non-compliant	IUT (inter user equipment transfer) is not supported.
4.3	Service Continuity	7.0.0	NA
4.3.1	Session Transfer concepts	7.0.0	NA
4.3.1.1	General	7.0.0	NA
4.3.1.2	Access Transfer concepts	7.0.0	NA
4.3.1.2.1	General Access Transfer concepts	7.0.0	NA
4.3.1.2.2	Access Transfer (PS-CS) concepts	7.0.0	NA
4.3.1.2.2A	MSC Server assisted mid-call feature	7.0.0	NA
4.3.1.2.3	Co-existence of ICS UE and MSC Server assisted mid-call feature	7.0.0	NA
4.3.1.3	Inter-UE Transfer concepts	Non-compliant	IUT is not supported.
4.3.2	Void	7.0.0	NA
4.3.3	Information used for IMS Service Continuity	7.0.0	NA
5	Architecture model and reference points	7.0.0	NA
5.1	Overview	7.0.0	NA
5.2	Reference Architecture for non emergency session	7.0.0	NA
5.2.1	General	7.0.0	NA
5.2.2	Architecture when using ATCF enhancements	7.0.0	NA
5.3	Functional Entities	7.0.0	NA
5.3.1	SCC AS	7.0.0 (Partial)	OCECAS does not update the operator policy in the UE. IUT is not supported. CS to PS transfer is not supported.
5.3.2	IMS Service Continuity UE	7.0.0	NA
5.3.2.1	Access Transfer Functions	7.0.0	Noted
5.3.2.2	IUT Functions and Roles	Non-compliant	Not considered as IUT is not supported as SCC AS.
5.3.3	Emergency Access Transfer Function (EATF)	7.0.0	OCECAS is not the EATF; and is not involved in emergency calls.
5.3.4	Access Transfer Control Function (ATCF)	7.0.0	NA
5.3.4.1	General	7.0.0	NA
5.3.4.2	ATCF inclusion	7.0.0	NA
5.3.5	Access Transfer Gateway (ATGW)	7.0.0	NA
5.3.6	HSS	7.0.0	NA
5.3.7	MSC Server	7.0.0	NA
5.4	Signalling and bearer paths for IMS Service Continuity	7.0.0	NA
5.4.1	General	7.0.0	NA
5.4.2	Sessions with PS media flow(s)	Non-compliant	OCECAS expects to be deployed with an Access Transfer Control Function (ATCF).
5.4.2a	Sessions with PS media flow(s) using ATCF	7.0.0	NA
5.4.3	Sessions with CS media	Non-compliant	OCECAS expects to be deployed with an ATCF
5.4.3a	Sessions with CS media flow(s) using ATCF	7.0.0	NA
5.5	IUT Collaborative Sessions	Non-compliant	IUT is not supported.
5.6	Reference Architecture for SRVCC emergency session	7.0.0	OCECAS is not the EATF (Emergency Access Transfer Function), and not involved in emergency calls.
6	Procedures and flows for Access Transfer	7.0.0	NA
6.1	Registration	7.0.0	NA
6.1.1	General	7.0.0	NA
6.1.2	Registration using ATCF enhancements	7.0.0	NA
6.1.3	CS to PS - Single Radio	Non-compliant	CS to PS transfer is not supported.
6.2	Origination and Termination	7.0.0	NA
6.2.1	Origination	7.0.0	NA
6.2.1.1	Origination Procedures	7.0.0	NA
6.2.1.2	Originating sessions that use CS media	7.0.0	NA
6.2.1.3	Originating sessions that use only PS media flow(s)	7.0.0	NA
6.2.1.4	Originating sessions for (v)SRVCC that use ATCF enhancements	7.0.0	NA
6.2.1.5	Originating sessions for CS to PS - Single Radio	Non-compliant	CS to PS transfer is not supported.
6.2.2	Termination	-	NA
6.2.2.1	Termination Procedures	7.0.0	NA
6.2.2.2	Terminating sessions that use CS media	7.0.0	NA
6.2.2.3	Terminating sessions that use only PS media flow(s)	7.0.0	NA
6.2.2.4	Terminating sessions over Gm where speech media is not accepted by the UE	Non-compliant	Not supported
6.2.2.5	Terminating sessions for (v)SRVCC that use ATCF enhancements	7.0.0	NA
6.2.2.6	Terminating sessions for CS to PS - Single Radio	Non-compliant	CS to PS transfer is not supported.
6.3	Access Transfer	7.0.0	NA
6.3.1	Access Transfer Procedure	7.0.0	NA
6.3.1.1	Introduction	7.0.0	NA
6.3.1.2	Access Transfer Procedures	7.0.0	NA
6.3.1.2a	Access Transfer Procedures using ATCF enhancements	7.0.0 (Partial)	CS to PS transfer is not supported.
6.3.1.3	Enablement of Access Transfer Procedures	7.0.0 (Partial)	CS to PS transfer is not supported.
6.3.1.3a	Enablement of Access Transfer procedures using ATCF enhancements	7.0.0 (Partial)	CS to PS transfer is not supported.
6.3.1.4	Execution of Access Transfer procedures	7.0.0	NA
6.3.1.4a	Execution of Access Transfer procedures using ATCF enhancements	7.0.0	NA
6.3.1.5	Remote Leg Update	7.0.0	NA
6.3.1.6	Source Access Leg Release	7.0.0	NA
6.3.1.7	Access Transfer Information for ATCF	7.0.0	NA
6.3.2	Access Transfer Information flows	7.0.0	NA
6.3.2.0	General	7.0.0	NA
6.3.2.1.1	PS-CS Access Transfer: PS to CS - Dual Radio	7.0.0	NA
6.3.2.1.1a	PS-CS Access Transfer: PS to CS - Dual Radio with Session State Information	Non-compliant	Not supported
6.3.2.1.2	PS-CS Access Transfer: CS to PS - Dual Radio	Non-compliant	CS to PS transfer is not supported
6.3.2.1.2a	PS-CS Access Transfer: CS to PS - Dual Radio with Session State Information	Non-compliant	CS to PS transfer is not supported
6.3.2.1.2b	CS-PS Access Transfer: CS to PS - Dual Radio, incoming voice call in alerting phase	Non-compliant	CS to PS transfer is not supported
6.3.2.1.2c	CS-PS Access Transfer: CS to PS - Dual Radio, outgoing voice call in pre-alerting state or in alerting phase	Non-compliant	CS to PS transfer is not supported
6.3.2.1.2d	PS-CS Access Transfer: PS to CS - Dual Radio, outgoing voice or video call in pre-alerting state or in alerting phase	Non-compliant	Early phase transfer not supported
6.3.2.1.2e	PS-CS Access Transfer: PS to CS - Dual Radio, incoming voice call in alerting phase	Non-compliant	Early phase transfer not supported
6.3.2.1.3	Subsequent Access Transfers	7.0.0	NA
6.3.2.1.4	PS-CS Access transfer: PS to CS - Single Radio	7.0.0	NA
6.3.2.1.4a	PS-CS Access Transfer: PS to CS - Single Radio with Session State Information	Non-compliant	Not supported
6.3.2.1.4b	PS to CS Access Transfer: PS to CS - Single Radio; using I1 reference point	Non-compliant	I1 not supported
6.3.2.1.4c	PS-CS Access Transfer: PS to CS - Single Radio, incoming voice or video call in alerting phase	Non-compliant	Early phase transfer not supported
6.3.2.1.4d	PS-CS Access Transfer: PS to CS - Single Radio, outgoing voice or video call in pre-alerting state or in alerting phase	Non-compliant	Early phase transfer not supported
6.3.2.1.4e	PS-CS Access Transfer: PS to CS - Single Radio, voice and video	7.0.0	NA
6.3.2.1.5	PS-CS Access Transfer for voice and video, Dual Radio	Non-compliant	Not supported
6.3.2.1.6	PS-CS Access transfer: PS to CS - Dual Radio, mid-call service with an active speech and video session	Non-compliant	mid-call session features not supported
6.3.2.1.7	PS-CS Access transfer: PS to CS - Dual Radio, mid-call service with one inactive speech and video session	Non-compliant	mid-call session features not supported
6.3.2.1.7a	PS-CS Access transfer: PS to CS - Single Radio, mid-call service with an incoming waiting call in alerting phase	Non-compliant	mid-call session features not supported
6.3.2.1.7b	PS-CS Access transfer: PS to CS - Single Radio, mid-call service with an outgoing call in pre-alerting state or in alerting phase	Non-compliant	mid-call session features not supported
6.3.2.1.7c	PS-CS Access transfer: PS to CS - Single Radio, mid-call service with an incoming call in alerting phase and a held session	Non-compliant	mid-call session features not supported
6.3.2.1.8	PS-CS Access Transfer: Conferencing - for UEs not using ICS capabilities	Non-compliant	mid-call session features not supported
6.3.2.1.9	PS-CS Access Transfer: PS to CS - Single Radio using ATCF enhancements	7.0.0	NA
6.3.2.1.9.1	ATCF with media anchored in ATGW	7.0.0	NA
6.3.2.1.9.2	ATCF without media anchored in ATGW	7.0.0	NA
6.3.2.1.9.3	ATCF not included during registration	7.0.0	NA
6.3.2.1.10	PS-CS Access Transfer: CS to PS - Single Radio	Non-compliant	CS to PS transfer is not supported.
6.3.2.2	PS-PS Access Transfer	-	NA
6.3.2.2.1	PS-PS Access Transfer with full media transfer	7.0.0	NA
6.3.2.2.2	PS-PS Access Transfer with partial media transfer	Non-compliant	Not supported
6.3.2.2.3	PS-PS Access Transfer with full media transfer for an incoming call in early dialog phase	Non-compliant	Early phase transfer not supported.
6.3.2.2.4	PS-PS Access Transfer with full media transfer for an outgoing call in early dialog phase	Non-compliant	Early phase transfer not supported
6.3.2.3	PS-PS in conjunction with PS-CS Access Transfer	7.0.0	NA
6.3.2.3.1	PS-PS in conjunction with PS-CS Access Transfer: PS to CS for Ues not using ICS capabilities	7.0.0	NA
6.3.2.3.2	PS - PS in conjunction with PS - CS Access Transfer: CS to PS for UEs not using ICS capabilities	Non-compliant	CS to PS transfer is not supported.
6.3.2.3.3	PS - PS in conjunction with PS - CS Access Transfer: PS to CS for UEs with ICS capabilities - Using Gm reference point	7.0.0	NA
6.3.2.3.4	PS - PS in conjunction with PS - CS Access Transfer: CS to PS for UEs with ICS capabilities - Using Gm reference point	Non-compliant	CS to PS transfer is not supported.
6.3.2.3.5	PS - PS in conjunction with PS - CS Access Transfer: Active/Held sessions - Using Gm reference point	Non-compliant	Not supported
6.3.2.3.6	PS - PS in conjunction with PS - CS Access Transfer: Explicit Communication Transfer - Using Gm reference point	Non-compliant	Not supported
6.3.2.3.7	PS - PS in conjunction with PS - CS Access Transfer: Conferencing - Using Gm reference point	Non-compliant	Not supported
6.3.2.3.8	PS - PS in conjunction with PS - CS Access Transfer: PS to CS - using I1 reference point	Non-compliant	Not supported
6.3.2.3.9	PS - PS in conjunction with PS - CS Access Transfer: CS to PS - using I1 reference point	Non-compliant	Not supported
6.3.2.3.10	PS - PS in conjunction with PS - CS Access Transfer: PS to CS for Active/Held sessions - using I1 reference point	Non-compliant	Not supported
6.2.3.2.11	PS-PS in conjunction with PS-CS AccessTransfer: CS to PS for Active/Held sessions - using I1 reference point	Non-compliant	Not supported
6.3.3	Media Adding/Deleting	7.0.0	NA
6.3.3.1	Local End Initiation case: Adding new PS media to existing CS session	Non-compliant	Not supported
6.3.3.2	Local End Initiation case: Incorporating existing CS media in new IMS Session and Gm Service Control	Non-compliant	Not supported
6.3.3.3	Local End Initiation case: Adding PS media to IMS session with CS media	Non-compliant	Not supported
6.3.3.4	Remote End Initiation case: Adding new PS media to existing CS session	Non-compliant	Not supported
6.3.3.5	Remote End Initiation case: Incorporating existing CS media in new IMS Session and Gm Service Control	Non-compliant	Not supported
6.3.3.6	Remote End Initiation case: Adding PS media to IMS session with CS media	Non-compliant	Not supported
6.3.3.7	Local End Initiation case - Removing media from split CS and PS sessions	Non-compliant	Not supported
6.3.3.8	Remote End Initiation case - Removing media from split CS and PS sessions	Non-compliant	Not supported
6.3.3.9	Local End Initiation case: Adding new PS media to existing PS session	Non-compliant	Not supported
6.3.3.10	Remote End Initiation case: Adding new PS media to existing PS session	Non-compliant	Not supported
6.3.3.11	Local End Initiation case: Removing media from split PS sessions	Non-compliant	Not supported
6.3.3.12	Remote End Initiation case: Removing media from split PS sessions	7.0.0	Not supported
6.3.4	Void	7.0.0	NA
6.3.5	Service continuity for ICS UE using MSC Server assisted mid-call feature while maintaining CS media	Non-compliant	mid-call session features not supported.
6.4	Operator Policy and User Preferences	7.0.0	NA
6.5	Execution of supplementary services	7.0.0	NA
6.5.1	General	7.0.0	NA
6.5.2	Originating Identification Presentation (OIP)	7.0.0	NA
6.5.3	Originating Identification Restriction (OIR)	7.0.0	NA
6.5.4	Terminating Identification Presentation (TIP)	7.0.0	NA
6.5.5	Terminating Identification Restriction (TIR)	7.0.0	NA
6.5.6	Communication Diversion (CDIV)	7.0.0	NA
6.5.7	Communication Hold (HOLD)	Non-compliant	Not supported with SRVCC
6.5.8	Communication Barring (CB)	7.0.0	NA
6.5.9	Message Waiting Indication (MWI)	Non-compliant	Not supported
6.5.10	Conference (CONF)	Non-compliant	Not supported with SRVCC
6.5.11	Explicit Communication Transfer (ECT)	Non-compliant	Not supported
6.5.12	Advice of Charge (AOC)	Non-compliant	Not supported
6.5.13	Closed User Groups (CUG)	Non-compliant	Not supported
6.5.14	Three-Party (3PTY)	Non-compliant	Not supported
6.5.15	Flexible Alerting (FA)	Non-compliant	Not supported
6.5.16	Communication Waiting (CW)	Non-compliant	Not supported
6.5.17	Completion of Communications to Busy Subscriber (CCBS)/Completion of Communications by No Reply (CCNR)	7.0.0	NA
6.5.18	Customized Alerting Tones (CAT)	7.0.0	NA
6.5.19	Malicious Communication IDentification (MCID)	7.0.0	NA
6.5.20	Reverse Charging	7.0.0	NA
6.5.21	Personal Network Management (PNM)	7.0.0	NA
6.5.22	Customized Ringing Signal (CRS)	7.0.0	NA
6a	Procedures and flows for Inter-UE Transfer	Non-compliant	IUT not supported
6b	Void	7.0.0	NA
6c	Procedures and flows for SRVCC Emergency Session	7.0.0	NA
6c.1	IMS Emergency origination flow for PS to CS SRVCC	7.0.0	OCECAS is not the EATF, and not involved in emergency calls.
6c.2	SRVCC session transfer of IMS emergency session for PS to CS	7.0.0	OCECAS is not the EATF, and not involved in emergency calls.
6c.3	SRVCC Support for UEs in Normal Mode	7.0.0	OCECAS is not the EATF, and not involved in emergency calls.
6c.4	SRVCC Support for UEs in Limited Service Mode	7.0.0	OCECAS is not the EATF, and not involved in emergency calls.
7	Security	7.0.0	NA
7.1	General	7.0.0	NA
7.2	Access security for CS Domain	7.0.0	NA
7.3	Access security for IMS	7.0.0	NA
8	Charging	7.0.0	NA
8.1	Charging strategy	7.0.0 (Partial)	OCECAS can not initiate a charging update when handling an SRVCC update. (It can send an update including SRVCC information at the subsequent charging timer expiry)
8.2	Accounting strategy	7.0.0	NA

3GPP_TS_23.292 Compliance

Table 1-2 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 23.292 (v12.5.0), "IP Multimedia Subsystem (IMS) centralized services, Stage 2."

Table 1-2 PICS for 3GPP TS 23.292

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	High level Principles and requirements	7.0.0
4.1	General	7.0.0	Noted
4.2	Service consistency	7.0.0	Noted
4.3	Service continuity	7.0.0	Noted
4.4	Session scenarios	7.0.0	NA
4.4.1	Overview	7.0.0	NA
4.4.2	ICS UE Session Scenarios	7.0.0	Subject to the caveats for each supplementary services. See relevant PICS
4.5	Service settings data management	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
4.6	Identities	7.0.0	NA
4.6.1	Identities used by an ICS UE	7.0.0	Noted
4.6.2	Identities used by an MSC Server enhanced for ICS	7.0.0	NA
4.7	Coexistence of an ICS UE and a non ICS UE	7.0.0	NA
4.8	Routing of originated calls to IMS	7.0.0	NA
4.9	Void	7.0.0	NA
5	Architecture model and reference points	7.0.0	NA
5.1	Overview	7.0.0	NA
5.2	Reference architecture	7.0.0	NA
5.3	Functional Entities	7.0.0	NA
5.3.1	SCC AS	7.0.0 (Partial)	OCECAS does not support I1 interface. OCECAS does not provide IUA or CAA.
5.3.2	UE enhanced for ICS	7.0.0	Note that OCECAS does not support I1.
5.3.3	MSC Server enhancements for ICS	7.0.0	Noted
5.4	Reference points	7.0.0	NA
5.4.1	Reference Point UE - SCC AS (I1)	Non-compliant	Not supported
5.4.2	Reference Point MSC Server - CSCF (I2)	7.0.0	Noted
5.4.3	Reference Point MSC server - CS-MGW (Mc)	7.0.0	Noted
5.4.4	Reference Point MSC Server - TAS (I3)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
6	Functional description	7.0.0	NA
6.1	Common IMS Functions	7.0.0	NA
6.1.1	P-CSCF procedures	7.0.0	Noted
6.1.2	IMS ALG procedures	7.0.0	Noted
6.1.3	S-CSCF procedures	7.0.0	Noted
6.1.4	IBCF procedures	7.0.0	Noted
7	Procedures and flows	7.0.0	NA
7.0	General	7.0.0	Noted
7.1	Signalling and bearer paths	7.0.0	NA
7.1.1	Sessions established using the Gm or I1 reference point	Non-compliant	Not supported
7.1.2	Sessions established using CS call control and MSC Server	7.0.0	NA
7.2	Registration	7.0.0	NA
7.2.1	IMS registration via CS access	7.0.0	NA
7.2.1.1	Overview	7.0.0	NA
7.2.1.2	Registration using I2 reference point	7.0.0	NA
7.2.1.3	Deregistration using I2 reference point	7.0.0	NA
7.2.1.4	Registration after Deregistration using I2 reference point	7.0.0	NA
7.2.1.5	Registration before Deregistration using I2 reference point	7.0.0	NA
7.2.2	IMS Registration via IP-CAN	7.0.0	NA
7.3	Originations	7.0.0	NA
7.3.1	Originating sessions that use PS media	7.0.0	NA
7.3.2	Originating sessions that use CS media	7.0.0	NA
7.3.2.1	Non ICS UE originating sessions that use CS media	7.0.0	NA
7.3.2.1.1	Overview	7.0.0	NA
7.3.2.1.2	Origination using I2 reference point	7.0.0	NA
7.3.2.1.3	Origination when using an MSC Server	7.0.0 (Partial)	Construction of IMRN will require extra configuration.
7.3.2.2	ICS UE Originating sessions that use CS media	7.0.0	NA
7.3.2.2.1	Overview	7.0.0	NA
7.3.2.2.2	Originations with CS media when using I1	Non-compliant	Not supported (I1 is not supported)
7.3.2.2.3	Originations with CS media when not using I1	7.0.0	NA
7.3.2.2.4	Originations with CS media using the Gm reference point	7.0.0 (Partial)	Construction of SCC AS PSI DN will require extra configuration.
7.4	Terminations	7.0.0	NA
7.4.1	Terminating sessions that use PS media	7.0.0	NA
7.4.1.1	Full duplex speech via PS	7.0.0	NA
7.4.1.2	Void	7.0.0	NA
7.4.1.3	Void	7.0.0	NA
7.4.2	Terminating sessions that use CS media	7.0.0	NA
7.4.2.1	Non ICS UE terminating sessions that use CS media	7.0.0	NA
7.4.2.1.1	Overview	7.0.0	NA
7.4.2.1.2	Termination using I2 reference point	7.0.0	NA
7.4.2.1.3	Termination to non ICS UE not registered in IMS	7.0.0	NA
7.4.2.2	ICS UE Terminating sessions that use CS media	7.0.0	NA
7.4.2.2.1	Overview	7.0.0 (Partial)	Construction of SCC AS PSI DN will require extra configuration.
7.4.2.2.2	Terminations with CS media using the Gm reference point	7.0.0 (Partial)	Construction of SCC AS PSI DN will require extra configuration.
7.4.2.2.3	Terminations with CS media using the I1 reference point	Non-compliant	Not supported (I1 is not supported)
7.4.2.2.4	Terminations with CS media using CS control with I1 augmentation	Non-compliant	Not supported (I1 is not supported)
7.4.2.2.5	Terminations with CS media when not using Gm or I1	7.0.0	NA
7.4.2.2.6	Void	7.0.0	NA
7.4.2.2.7	Terminating access network reselection - fallback to alternate access	7.0.0	NA
7.4.3	Terminating sessions over Gm rejected by the UE	7.0.0	NA
7.5	Service continuity	7.0.0	NA
7.5.1	Service continuity for ICS UE	7.0.0	NA
7.5.1.1	Service continuity while maintaining the use of CS access for the media	7.0.0	NA
7.5.1.1.1	IMS sessions established using Gm reference point	7.0.0	NA
7.5.1.1.1.1	Overview	7.0.0	NA
7.5.1.1.1.2	Use of Gm reference point possible after handover	7.0.0	NA
7.5.1.1.1.3	Use of Gm reference point not possible after Handover	7.0.0	NA
7.5.1.1.1.3a	Use of Service Control Signalling Path not possible after Handover	7.0.0	NA
7.5.1.1.1.3a.1	MSC Server assisted midNAcall feature not used	7.0.0	NA
7.5.1.2	Service continuity when transferring the media of IMS sessions between PS and CS access	7.0.0	See "3GPP_TS_23.237 Compliance" PICS.
7.5a	Addition of Gm service control to existing call	7.0.0	NA
7.5a.1	Overview	7.0.0	NA
7.5a.2	Augmentation call flow	7.0.0	NA
7.6	Consistency of Supplementary Services	7.0.0	NA
7.6.0	General	7.0.0	NA
7.6.1	Supplementary Services for ICS UE	7.0.0	NA
7.6.1.1	Overview	7.0.0	NA
7.6.1.2	IMS session using CS bearer	7.0.0	NA
7.6.1.2.1	Overview	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2	Use of Gm reference point	7.0.0	NA
7.6.1.2.2.1	Line ID Services (OIP, OIR, TIP, TIR)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2.2	Communication Diversion Services	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2.3	Communication Barring	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2.4	Communication Hold/Resume	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2.5	Explicit Communication Transfer	Non-compliant	Not supported
7.6.1.2.2.6	Conferencing	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.1.2.2.7	Communication Waiting	Non-compliant	Not supported
7.6.1.2.2.8	Customized Alerting Tone (CAT)	7.0.0 (Partial)	See "3GPP_TS_24.182 Compliance" PICS for the limited CAT support.
7.6.1.2.3	Use of I1 reference point	Non-compliant	Not supported (I1 is not supported)
7.6.1.2.4	When use of Gm or I1 reference point is not possible due to VPLMN limitations	7.0.0	NA
7.6.1.2.4.1	When attached to an MSC Server enhanced with ICS	7.0.0	NA
7.6.1.2.4.2	When attached to an MSC Server not enhanced with ICS	7.0.0	NA
7.6.1.3	User configuration of Supplementary Services	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2	Supplementary service invocation using the MSC Server enhanced for ICS	7.0.0	NA
7.6.2.1	Overview	7.0.0	NA
7.6.2.2	Line ID Services (OIP, OIR, TIP, TIR)	7.0.0	NA
7.6.2.3	Communication Diversion Services	7.0.0	NA
7.6.2.3.1	Communication Forwarding Unconditional (CFU)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2.3.2	Communication Forwarding Busy (CFB)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2.3.3	Communication Forwarding No Reply (CFNR)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2.3.4	Communication Forwarding on Not Logged-in (CFNL)	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2.3.5	Communication Deflection (CD)	7.0.0	NA
7.6.2.3.6	Communication Forwarding on Subscriber Not Reachable (CFNRc)	7.0.0	NA
7.6.2.3.7	Communication Diversion Notification (CDIVN)	7.0.0	NA
7.6.2.3.8	Diversion notifications to originating users	7.0.0	NA
7.6.2.4	Communication Barring	7.0.0	NA
7.6.2.5	Communication Hold/Resume	7.0.0	NA
7.6.2.6	Communication Waiting	Non-compliant	Not supported
7.6.2.7	Explicit Communication Transfer	Non-compliant	Not supported
7.6.2.8	Conferencing	7.0.0	NA
7.6.2.9	User configuration of communication service settings	7.0.0	NA
7.6.2.9.1	TAS procedures	7.0.0 (Partial)	See "3GPP_TS_24.173 Compliance" PICS. Configuration via XCAP is not supported.
7.6.2.9.2	UE supporting multimedia telephony	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.2.9.3	MSC Server enhanced for ICS	7.0.0	NA
7.6.2.10	Customized Alerting Tone (CAT)	7.0.0 (Partial)	See "3GPP_TS_24.173 Compliance" PICS for the limited CAT support.
7.6.2.11	Communication Completion on Busy Subscriber/No Reply/Not Logged In	7.0.0	NA
7.6.2.11.1	Communication Completion Terminated at Served User	7.0.0	NA
7.6.2.11.2	Communication Completion Originated at Served User	7.0.0	NA
7.6.3	Service consistency for non ICS UE when attached to an MSC Server not enhanced with ICS	7.0.0	NA
7.6.3.1	Line ID Services (OIP, OIR, TIP, TIR)	7.0.0	NA
7.6.3.2	Communication Diversion Services	7.0.0	NA
7.6.3.2.1	Communication Diversion services; CFU, CFNL	7.0.0	NA
7.6.3.2.2	Communication Diversion services; CFNR, CFB	7.0.0	NA
7.6.3.2.2a	Communication Diversion services; CFNRc	7.0.0	NA
7.6.3.2.3	Communication Diversion services; Communication Deflection	7.0.0	NA
7.6.3.3	Communication Barring	7.0.0	NA
7.6.3.4	Communication Hold/Resume	7.0.0	NA
7.6.3.5	Explicit Communication Transfer	7.0.0	NA
7.6.3.6	Conferencing	7.0.0	NA
7.6.3.7	User configuration of Supplementary Services	7.0.0	NA
7.6.3.7.1	UE not supporting multimedia telephony	7.0.0	NA
7.6.3.7.2	UE supporting multimedia telephony	7.0.0	See "3GPP_TS_24.173 Compliance" PICS.
7.6.3.8	Customized Alerting Tone (CAT)	Non-compliant	Not supported
7.6.3.9	Communication Waiting	Non-compliant	Not supported
7.6.3.10	Communication Completion on Busy Subscriber/No Reply/Not Logged In	7.0.0	NA
7.6.3.10.1	Communication Completion Terminated at Served User	7.0.0	NA
7.6.3.10.2	Communication Completion Originated at Served User	7.0.0	NA
7.7	Session Release	7.0.0	NA
7.7.1	Session Release for ICS UE	7.0.0	NA
7.7.1.1	General Gm Procedures	7.0.0	NA
7.7.1.2	Session Release for Gm and I1	7.0.0	NA
7.7.1.3	Release of the Service Control Signalling Session when using I1	Non-compliant	Not supported
7.7.2	Session Release for MSC Server enhanced for ICS	-	NA
7.7.2.1	General	7.0.0	NA
7.7.2.2	Session Release by served UE	7.0.0	NA
7.7.2.3	Session Release by far-end	7.0.0	NA
7.7.2.4	Network initiated Session Release	7.0.0	NA
7.8	Loss of Gm capability	Non-compliant	Not supported
7.9	Addition/Removal of video media flow	7.0.0	NA
7.9.1	Addition/Removal of video media flow for Non ICS UE	7.0.0	NA
7.9.1.1	Overview	7.0.0	NA
7.9.1.2	Addition/Removal of video media flow through SCUDIF using I2 reference point	7.0.0	NA
7.9.1.3	Addition/Removal of video media flow through SCUDIF via the MSC Server not enhanced for ICS.	7.0.0	NA
7.9.2	Addition/Removal of video media flow for ICS UE	7.0.0	NA
7.9.2.1	Overview	7.0.0	NA
7.9.2.2	Addition/Removal of video media flow through SCUDIF using Gm Reference Point	7.0.0	NA
7.9.2.3	Addition/Removal of video media flow through SCUDIF using I1 Reference Point	Non-compliant	Not supported
7.9.2.4	Addition/Removal of video media flow through redial using Gm Reference Point	7.0.0	NA
7.9.2.5	Addition/Removal of video media flow through redial using I1 Reference Point	Non-compliant	Not supported
8	Charging	7.0.0	NA
8.1	General description	7.0.0	NA
8.2	Offline charging	7.0.0	NA
8.3	On-line charging	7.0.0	NA
9	Security Considerations	7.0.0	NA
9.1	Access security	7.0.0	NA
9.2	Network Domain Security	7.0.0	NA

3GPP 24 Series Compliance

This section describes the following:

• 3GPP_TS_24.147 Compliance

• 3GPP_TS_24.173 Compliance

• 3GPP_TS_24.182 Compliance

• 3GPP_TS_24.237 Compliance

• 3GPP_TS_24.604 Compliance

• 3GPP_TS_24.605 Compliance

• 3GPP_TS_24.607 Compliance

• 3GPP_TS_24.608 Compliance

• 3GPP_TS_24.610 Compliance

• 3GPP_TS_24.611 Compliance

3GPP_TS_24.147 Compliance

Table 1-3 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.147 (v12.4.0), "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem, Stage 3."

Table 1-3 PICS for 3GPP TS 24.147

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Conferencing overview	7.0.0 (Partial)	Conference Policy and Conference Notifications are not supported.
5	Protocol using SIP and SIP events for conferencing	7.0.0	NA
5.1	Introduction	7.0.0	NA
5.2	Functional entities	7.0.0	NA
5.2.1	User Equipment (UE)	7.0.0	NA
5.2.2	Media Resource Function Controller (MRFC)	7.0.0	NA
5.2.3	Conferencing Application Server (AS)	7.0.0 (Partial)	Only ad-hoc conferencing is supported. See clause 5.3 for more details. OCECAS does not take the role of a conference participant.
5.2.4	Media Gateway Control Function (MGCF)	7.0.0	NA
5.3	Role	7.0.0	NA
5.3.1	Conference Participant	7.0.0	NA
5.3.1.1	General	7.0.0	NA
5.3.1.2	Subscription for conference event package	Non-compliant	Not supported
5.3.1.3	Conference creation	7.0.0	NA
5.3.1.3.1	General	7.0.0	NA
5.3.1.3.2	Conference creation with a conference factory URI	7.0.0 (Partial)	Conference subscriptions are not supported.
5.3.1.3.3	Three-way session creation	7.0.0	NA
5.3.1.4	Join a conference	7.0.0	NA
5.3.1.4.1	User joining a conference by using a conference URI	7.0.0 (Partial)	Conference subscriptions are not supported.
5.3.1.4.2	User joining a conference after receipt of a REFER request	7.0.0	NA
5.3.1.5	Inviting other users to a conference	7.0.0	NA
5.3.1.5.1	General	7.0.0 (Partial)	Starting a conference with a recipient list is not supported.
5.3.1.5.2	User invites other user to a conference by sending a REFER request to the other user	7.0.0	OCECAS would not be aware of the conference in this scenario, so conference control at OCECAS is not possible.
5.3.1.5.3	User invites other user to a conference by sending a REFER request to the conference focus	7.0.0	NA
5.2.1.5.4	User invites other users to a conference by including URI list in initial INVITE request to the conference focus	Non-compliant	Not supported.
5.3.1.6	Leaving a conference	7.0.0	NA
5.3.1.6.1	Conference participant leaving a conference	7.0.0 (Partial)	Conference subscriptions are not supported.
5.3.1.6.2	Conference focus removes conference participant from a conference	7.0.0 (Partial)	Conference subscriptions are not supported.
5.3.1.6.3	Removing a conference participant from a conference	7.0.0	NA
5.3.1.7	Consent to list server distribution	7.0.0	NA
5.3.2	Conference focus	7.0.0	NA
5.3.2.1	General	7.0.0	NA
5.3.2.2	Generic procedures for all conference related methods at the conference focus	7.0.0	NA
5.3.2.2.1	Conference focus originating case	7.0.0 (Partial)	P-Charging-Vector is not populated.
5.3.2.2.2	Conference focus terminating case	7.0.0 (Partial)	P-Charging-Vector and P-Charging-Function-Addresses are not populated.
5.3.2.3	Conference creation	7.0.0	NA
5.3.2.3.1	Conference creation with a conference factory URI	7.0.0	NA
5.3.2.3.2	Conference creation with a conference URI	7.0.0	NA
5.3.2.4	User joining a conference	7.0.0	NA
5.3.2.4.1	User joining a conference by using a conference URI	7.0.0 (Partial)	The user identity is not verified.
5.3.2.5	Invitation of users to a conference	7.0.0	NA
5.3.2.5.1	General	7.0.0 (Partial)	Starting a conference with a recipient list is not supported.
5.3.2.5.2	Request from a user to invite another user to a conference using a REFER request	7.0.0 (Partial)	The user identity is not verified. (Trusted users are expected).
5.3.2.5.3	Request from a user to invite another user to a conference using an INVITE request for conference creation	Non-compliant	Not supported
5.3.2.5.4	Inviting a user to a conference by sending an INVITE request	7.0.0	NA
5.3.2.5.5	Inviting a user to a conference by sending a REFER request	Non-compliant	Not supported
5.3.2.6	Leaving a conference	7.0.0	NA
5.3.2.6.1	Conference participant leaving a conference	7.0.0	NA
5.3.2.6.2	Removing a conference participant from a conference	7.0.0	NA
5.3.2.6.2.1	General	7.0.0	NA
5.3.2.6.2.2	Request from a conference participant to remove another conference participant from a conference	Non-compliant	Not supported
5.3.2.6.2.3	Conference focus removes conference participant from a conference	7.0.0	NA
5.3.2.7	Conference termination	7.0.0	NA
5.3.3	Conference Notification Service	7.0.0	NA
5.3.3.1	General	Non-compliant	Not supported
5.3.3.2	Subscription to conference event package	Non-compliant	Not supported
5.3.3.3	Leaving a conference	Non-compliant	Not supported
5.3.3.4	Conference termination	Non-compliant	Not supported
6	Protocol using SDP for conferencing	7.0.0	NA
6.1	Introduction	7.0.0	NA
6.2	Functional entities	7.0.0	NA
6.2.1	User Equipment (UE)	7.0.0	NA
6.2.2	Media Resource Function Controller (MRFC)	7.0.0	NA
6.2.3	Conferencing Application Server (AS)	7.0.0	NA
6.2.4	Media Gateway Control Function (MGCF)	7.0.0	NA
6.3	Role	7.0.0	NA
6.3.1	Conference Participant	7.0.0	NA
6.3.2	Conference Focus	7.0.0	NA
7	Void	7.0.0	NA
8	Protocol for floor control for conferencing	7.0.0	NA
8.1	Introduction	Non-compliant	Not supported
8.2	Functional entities	7.0.0	NA
8.2.1	User Equipment (UE)	Non-compliant	Not supported
8.2.2	Media Resource Function Processor (MRFP)	Non-compliant	Not supported
8.3	Role	7.0.0	NA
8.3.1	Floor participant	Non-compliant	Not supported
8.3.2	Floor chair	Non-compliant	Not supported
8.3.3	Floor control server	Non-compliant	Not supported

3GPP_TS_24.173 Compliance

Table 1-4 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.173 (v12.3.0), "IMS Multimedia telephony communication service and supplementary services, Stage 3."

Table 1-4 PICS 3GPP TS 24.173

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Overview of multimedia telephony communication service and associated supplementary services in the IP Multimedia (IM) Core Network (CN) subsystem	7.0.0	NA
4.1	General	7.0.0	Noted
4.1A	Roles	NA	NA
4.1A.1	Multimedia telephony participant	7.0.0	NA
4.1A.2	Multimedia telephony application server	7.0.0	NA
4.2	Overview of basic communication part	7.0.0	NA
4.3	Overview of supplementary services part	7.0.0 (Partial)	XCAP is not supported.
5	Basic Communication	7.0.0	NA
5.1	IMS communication service identifier	7.0.0	NA
5.2	Session control procedures	7.0.0	NA
5.3	Interworking	7.0.0	NA
6	Supplementary services and enhancements	7.0.0	NA
6.1	High level requirements	7.0.0	NA
6.2	Originating Identification Presentation (OIP)	7.0.0	See "3GPP_TS_24.607 Compliance" PICS.
6.3	Originating Identification Restriction (OIR)	7.0.0	See "3GPP_TS_24.607 Compliance" PICS.
6.4	Terminating Identification Presentation (TIP)	7.0.0	See "3GPP_TS_24.608 Compliance" PICS.
6.5	Terminating Identification Restriction (TIR)	7.0.0	See "3GPP_TS_24.608 Compliance" PICS.
6.6	Communication Diversion (CDIV)	7.0.0	See "3GPP_TS_24.604 Compliance" PICS.
6.7	Communication Hold (HOLD)	7.0.0	See "3GPP_TS_24.610 Compliance" PICS.
6.8	Communication Barring (CB)	7.0.0	See "3GPP_TS_24.611 Compliance" PICS.
6.9	Message Waiting Indication (MWI)	Non-compliant	Not supported
6.10	Conference (CONF)	7.0.0	See "3GPP_TS_24.605 Compliance" PICS.
6.11	Explicit Communication Transfer (ECT)	Non-compliant	Not supported
6.12	XCAP over Ut interface for Manipulating NGN Services	Non-compliant	Not supported
6.13	Advice Of Charge (AOC)	Non-compliant	Not supported
6.14	Closed User Groups (CUG)	Non-compliant	Not supported
6.15	Three-Party (3PTY)	Non-compliant	Not supported. Note that is different from the 3-party ad hoc conferences that OCECAS does support. (OCECAS supports receiving REFERs from UE1 and sending INVITEs for each REFER. It does not support receiving INVITEs from new conference participants wanting to join.
6.16	Flexible Alerting (FA)	Non-compliant	Not supported
6.17	Communication Waiting	Non-compliant	Not supported
6.18	Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR)	Non-compliant	Not supported
6.19	Customized Alerting Tones (CAT)	7.0.0 (Partial)	Early media is supported, so CAT is possible (but not configured out-of-the-box). See "3GPP_TS_24.182 Compliance" PICS for details.
6.20	Customized Ringing Signal (CRS)	Non-compliant	Not supported
6.21	Personal Network Management (PNM)	Non-compliant	Not supported
6.22	Unstructured Supplementary Service Data (USSD)	Non-compliant	Not supported

3GPP_TS_24.182 Compliance

Table 1-5 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.182 (v12.0.0), "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT), Protocol specification.”

Table 1-5 PICS_3GPP_TS_24.182

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Customized Alerting Tones (CAT)	7.0.0	Note that CAT is not configured out-of-the-box. All compliance below will require extra OCECAS configuration.
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	NA
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	NA
4.3.1.1	CAT provision/withdrawal	7.0.0	NA
4.3.1.2	Requirements on the originating network side	7.0.0	NA
4.3.1.3	Requirements on the terminating network side	7.0.0	NA
4.4	Syntax requirements	7.0.0	Noted
4.5	Signalling procedures	7.0.0	NA
4.5.1	General	Non-compliant	Configuration via XCAP is not supported. Configuration is via a UI or REST interface.
4.5.2	Activation/deactivation	7.0.0	NA
4.5.3	Registration/erasure	7.0.0	NA
4.5.4	Interrogation	7.0.0	NA
4.5.5	Invocation and operation	7.0.0	NA
4.5.5.1	Actions at the originating UE	7.0.0	NA
4.5.5.1.1	General	7.0.0	NA
4.5.5.1.2	UE Actions for CAT copy	Non-compliant	Assuming that this means having the originators profile updated with the same media as the called party, this is not supported. (It would require two active profiles in the control flow).
4.5.5.1.3	UE Actions for CAT stop	7.0.0	NA
4.5.5.1.4	UE support of DTMF	7.0.0	NA
4.5.5.2	Actions at the AS serving the originating UE	7.0.0	NA
4.5.5.2.1	General	7.0.0	NA
4.5.5.2.2	AS Actions for forking model	Non-compliant	The SIP 183 response does not get "g.3gpp.cat" added to the answer.
4.5.5.2.3	AS Actions for early session model	7.0.0	NA
4.5.5.2.3A	AS Actions for CAT Reject	Non-compliant	Manipulation of the SDP offer is not possible in the Control Flow.
4.5.5.2.4	AS Actions for CAT stop	7.0.0	NA
4.5.5.2.5	AS support of DTMF	7.0.0	NA
4.5.5.2.6	AS Actions for Gateway model	7.0.0	NA
4.5.5.3	Actions at the AS serving the terminating UE	7.0.0	NA
4.5.5.3.1	General	7.0.0	NA
4.5.5.3.2	AS actions for forking model	Non-compliant	The SIP 183 response does not get "g.3gpp.cat" added to the answer. Likewise the P-Early-Media header field is not correct. The SDP answer is not correct.
4.5.5.3.3	AS Actions for early session model	7.0.0 (Partial)	The 18x response headers are not filled with "early-session" and the "g.3gpp.cat" value is not added.
4.5.5.3.4	AS Actions for CAT copy	7.0.0	NA
4.5.5.3.5	AS Actions for CAT stop	7.0.0	NA
4.5.5.3.6	AS support of DTMF	7.0.0 (Partial)	"telephone-event" media subtype is not supported. (SIP INFO mechanism is supported).
4.5.5.3.7	AS Actions for Gateway model	7.0.0	OCECAS does not include the SDP from the SIP 183 in the SIP 200
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication session Hold (HOLD)	7.0.0	NA
4.6.2	Termination Identification Presentation (TIP)	7.0.0	NA
4.6.3	Termination Identification Restriction (TIR)	7.0.0	NA
4.6.4	Originating Identification Presentation (OIP)	7.0.0	NA
4.6.5	Originating Identification Restriction (OIR)	7.0.0	NA
4.6.6	Conference (CONF)	7.0.0	NA
4.6.7	Communication DIVersion services (CDIV)	-	NA
4.6.7.1	General	7.0.0	NA
4.6.7.2	CFNR	7.0.0	NA
4.6.8	Message Waiting Indication (MWI)	7.0.0	NA
4.6.9	Communication Barring (CB)	7.0.0	NA
4.6.10	Explicit Call Transfer (ECT)	Non-compliant	ECT is not supported
4.6.11	Communication Wait	Non-compliant	CW is not supported
4.6.12	Completion of Communications to Busy Subscriber	7.0.0	NA
4.6.13	Customized Ringing Signal (CRS)	7.0.0	Is possible through some complex configuration
4.7	Parameter values (timers)	7.0.0	NA
4.8	Service configuration	7.0.0	NA
Annex A	Signalling flows	7.0.0	NA
A.1	Scope of signalling flows	7.0.0	NA
A.2	Void	7.0.0	NA
A.3	CAT forking model signalling flows	7.0.0	NA
A.3.1	Introduction	7.0.0	NA
A.3.2	CAT when UE#1 and UE#2 have resources	Non-compliant	Forking model not supported
A.3.3	CAT when UE#1 does not have required resources available while UE#2 has resources available	Non-compliant	Forking model not supported
A.3.4	CAT when UE#1 has resources available while UE#2 does not have required resources available	Non-compliant	Forking model not supported
A.4	CAT early session model signalling flows	7.0.0	NA
A.4.1	Introduction	7.0.0	NA
A.4.2	CAT when UE#1 and UE#2 have resources available	7.0.0 (Partial)	SIP 183 does not include early-session, dtmfInfo in headers.
A.4.3	CAT when UE#1 does not have required resources available while UE#2 has resources available	Non-compliant	Early session SDP content is not included in SIP 183.
A.4.4	CAT when UE#1 has resources available while UE#2 does not have required resources available	Non-compliant	Early session SDP content is not included in SIP 183.
A.5	CAT Gateway model signalling flows	7.0.0	NA
A.5.1	Introduction	7.0.0	NA
A.5.2	CAT when UE#1 and UE#2 have resources available	7.0.0 (Partial)	180 response does not have P-Early-Media header added
A.5.2A	CAT using reINVITE request when UE#1 and UE#2 have resources available	Non-compliant	Not supported
A.5.3	CAT when UE#1 does not have required resources available while UE#2 has resources available	Non-compliant	31. UPDATE is not sent.
A.5.3A	CAT using reINVITE request when UE#1 does not have required resources available while UE#2 has resources available	Non-compliant	Not supported
A.5.4	CAT when UE#1 has resources available while UE#2 does not have required resources available	Non-compliant	15. UPDATE is not sent.
A.5.4A	CAT using reINVITE request when UE#1 has resources available while UE#2 does not have required resources available	Non-compliant	Not supported
A.5.5	CAT diverting for CFNR using reINVITE request when UE#1, UE#2 and UE#3 have resources available	Non-compliant	Not supported
A.5.6	CAT diverting for CFU	7.0.0	NA
A.5.6.1	General	7.0.0	NA
A.5.6.2	Gateway model CAT diverting for CFU when UE#1, UE#2 and UE#3 have resources available	7.0.0 (Partial)	180 response does not have P-Early-Media header added
A.5.7	CAT when both UE#1 and UE#2 do not have required resources available	Non-compliant	Necessary UPDATEs from the AS are not sent.
A.6	Interworking with CS domain	-	NA
A.6.1	Introduction	7.0.0	NA
A.6.2	CAT provided by the terminating CS domain	7.0.0	NA
A.6.3	CAT provided to the originating CS domain with the CAT forking model	Non-compliant	Not supported.
A.6.4	CAT provided to the originating CS domain with the CAT early session model	7.0.0	NA
Annex B	SDP a=content attribute "g.3gpp.cat" value	7.0.0	NA
B.1	Introduction	7.0.0	Noted
B.2	New value	7.0.0	Noted

3GPP_TS_24.237 Compliance

Table 1-6 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.237 (v12.0.0), "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity, Stage 3.”

Table 1-6 3GPP_TS_24.237

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Overview of IP Multimedia (IM) Core Network (CN) subsystem Service Continuity	7.0.0	NA
4.1	General	7.0.0	Noted
4.2	Underlying network capabilities	7.0.0	NA
4.2.1	General	7.0.0	NA
4.2.2	PS-CS session continuity, Single Radio	7.0.0	NA
4.2.3	PS to CS and CS to PS session continuity, dual radio	7.0.0	NA
4.3	URI and address assignments	7.0.0	NA
4.4	Support of session continuity in enterprise scenarios	7.0.0	NA
4.5	Guidelines for use of media feature tags or feature capability indicators	7.0.0	NA
5	Functional entities	7.0.0	NA
5.1	Introduction	7.0.0	NA
5.2	User Equipment (UE)	7.0.0	NA
5.3	Application Server (AS)	7.0.0	NA
5.4	MSC server	7.0.0	NA
5.5	EATF	7.0.0	Note that OCECAS is not considered an EATF
5.6	Access Transfer Control Function (ATCF)	7.0.0	NA
5.7	Access Transfer Gateway (ATGW)	7.0.0	NA
6	Roles for registration in the IM CN subsystem for service continuity	7.0.0	NA
6.1	Introduction	7.0.0	NA
6.2	SC UE	7.0.0	NA
6.2.1	Distinction of requests	7.0.0	NA
6.2.2	General	Non-compliant	Not supported
6.2.3	SC UE receiving the ATGW information for CS to PS SRVCC	Non-compliant	CS to PS transfer not supported
6.3	SCC AS	7.0.0	NA
6.3.1	General	7.0.0 (Partial)	Registrations are not checked for association with on-going calls. Otherwise compliant.
6.3.2	Triggers for the SCC AS providing information to ATCF	7.0.0	NA
6.3.3	SCC AS providing the PS to CS SRVCC related information to the ATCF	7.0.0 (Partial)	P-Charging-Vector is not examined
6.3.4	Triggers for the SCC AS providing information to MSC server	Non-compliant	CS to PS transfer not supported
6.3.5	SCC AS providing the CS to PS SRVCC information to the MSC server	Non-compliant	CS to PS transfer not supported
6.4	MSC server	7.0.0	NA
6.4.1	Distinction of requests	7.0.0	NA
6.4.2	General	7.0.0	NA
6.4.3	MSC server receiving the MSC information for CS to PS SRVCC	Non-compliant	CS to PS transfer not supported
6.5	Access Transfer Control Function (ATCF)	-	NA
6.5.1	Distinction of requests	7.0.0	NA
6.5.2	Registration related procedures in the ATCF	7.0.0	NA
6.5.3	ATCF receiving the SRVCC-related information	7.0.0	NA
6.5.4	ATCF sending the ATGW information for CS to PS SRVCC	Non-compliant	CS to PS transfer not supported
6.5.5	ATCF receiving the UE information for CS to PS SRVCC	Non-compliant	CS to PS transfer not supported
6A	Roles for General Capabilities	7.0.0	NA
6A.1	Introduction	7.0.0	NA
6A.2	UE roles	7.0.0	NA
6A.3	ATCF	7.0.0	NA
6A.4	SCC AS	7.0.0	NA
6A4.1	Common SIP message set up procedures	7.0.0	NA
6A.4.2	SIP INVITE request	7.0.0	Only supported header fields are populated.
6A.4.3	SIP INVITE responses towards the SC UE	7.0.0	Only supported header fields are populated.
6A.4.3A	SIP INVITE responses towards the MSC server	7.0.0	Only supported header fields are populated.
6A.4.4	Handling of OMR specific attributes	Non-compliant	Not supported
6A.4.5	Target refresh request for a dialog and associated responses	Non-compliant	The header fields are not populated.
6A.4.6	Rejecting malicious SIP REFER requests from remote UE	7.0.0 (Partial)	mid-call and alerting phase are not supported.
6A.4.7	Protecting from malicious SIP INFO requests with remote leg information from remote UE	7.0.0	NA
6A.4.8	Precondition and access transfer	7.0.0	NA
6A.5	SDP media description conflict between target and remote access leg	7.0.0	NA
6A.6	Indicating traffic leg	7.0.0 (Partial)	OCECAS does not append the "iotl" parameter.
6A.7	MSC server	7.0.0	NA
7	Roles for call origination for service continuity	7.0.0	NA
7.1	Introduction	7.0.0	NA
7.2	SC UE	7.0.0	NA
7.3	SCC AS	7.0.0	NA
7.3.1	Distinction of requests sent to the SCC AS	7.0.0	Conference subscriptions are not supported.
7.3.2	Call origination procedures at the SCC AS	7.0.0	With the exception of 6A.4.3
7.3.3	Subscription related procedures in the SCC AS	Non-compliant	Conference subscriptions are not supported.
7.4	EATF	Non-compliant	Note that OCECAS is not considered an EATF
7.5	Access Transfer Control Function (ATCF)	7.0.0	NA
7.6	MSC server	7.0.0	NA
8	Roles for call termination for service continuity	7.0.0	NA
8.1	Introduction	7.0.0	NA
8.2	SC UE	7.0.0	NA
8.3	SCC AS	7.0.0	NA
8.3.1	Distinction of requests sent to the SCC AS	7.0.0	NA
8.3.2	Call termination procedures in the SCC AS	7.0.0	NA
8.4	Access Transfer Control Function (ATCF)	7.0.0	NA
8.5	MSC server	7.0.0	NA
9	Roles for PC-CS access transfer	7.0.0	NA
9.1	Introduction	7.0.0	NA
9.1A	Additional procedures with MSC Server assisted mid-call feature	Non-compliant	Not supported
9.2	SC UE	7.0.0 (Partial)	Mid-call feature, alerting phase, and CS-to-PS transfer are not supported.
9.3	SCC AS	7.0.0	NA
9.3.0	General	7.0.0	NA
9.3.1	Distinction of requests sent to the SCC AS	7.0.0	NA
9.3.2	SCC AS procedures for PS to CS access transfer	7.0.0 (Partial)	Note that mid-call feature and alerting phase are not supported.
9.3.2A	SCC AS procedures for PS to CS access transfer with MSC server assisted mid-call feature	Non-compliant	Not supported
9.3.3	SCC AS procedures for CS to PS access transfer	Non-compliant	Not supported
9.3.4	SCC AS procedures for CS to PS access transfer with MSC server assisted mid-call feature	Non-compliant	Not supported
9.3.5	SCC AS procedures for PS to CS dual radio access transfer of calls in an early dialog phase	Non-compliant	Not supported
9.3.6	Removal of non-transferred audio media components and release of source access legs	7.0.0	NA
9.3.7	SCC AS procedures for CS to PS dual radio access transfer for calls in an early phase	Non-compliant	Not supported
9.4	MSC server enhanced for ICS	7.0.0
9.5	PS to CS session continuity with MSC server assisted mid- call feature	Non-compliant	Not supported
9.6	PS to CS session continuity with MSC server assisted mid- call feature for speech and video session	Non-compliant	Not supported
9.7	MSC procedures for PS to CS dual radio access transfer of calls in an early phase	Non-compliant	Not supported
9.8	MSC server enhanced for dual radio access transfer using a SIP interface	Non-compliant	Not supported
10	Roles for PS-PS access transfer	7.0.0	NA
10.1	Introduction	7.0.0	NA
10.2	SC UE	7.0.0	NA
10.3	SCC AS	7.0.0	NA
10.3.1	Distinction of requests sent to the SCC AS	Non-compliant	The pstops media feature tag is never examined
10.3.2	PS to PS access transfer procedures at the SCC AS	7.0.0 (Partial)	Comparison of the media lines is not performed. Early dialog transfer is not supported.
10.3.3	Void	7.0.0	NA
10.3.4	S-CSCF releasing the source access leg during PS to PS access transfer	7.0.0	NA
10.3.5	P-CSCF releasing the source access leg during PS to PS access transfer	7.0.0	NA
10.3.6	P-CSCF releasing early dialog during PS to PS access transfer	Non-compliant	Transfer of early dialogs is not supported.
11	Roles for PS-PS access transfer in conjunction with PS-CS access transfer	7.0.0	NA
11.1	Introduction	7.0.0	NA
11.2	SC UE	7.0.0	NA
11.3	SCC AS	7.0.0	NA
11.3.1	Distinction of requests sent to the SCC AS	7.0.0	NA
11.3.2	SCC AS procedures for PS to PS+CS access transfer	Non-compliant	Not supported
11.3.3	SCC AS procedures for PS+CS to PS access transfer	Non-compliant	Not supported
12	Roles for PS-CS access transfer, Single Radio	7.0.0	NA
12.1	Introduction	7.0.0	NA
12.2	SC UE procedures for PS to CS access transfer, PS to CS SRVCC	7.0.0	NA
12.2.1	General	7.0.0	NA
12.2.2	ICS-based	7.0.0	NA
12.2.3	Not based on ICS	7.0.0	NA
12.2.3A	Not based on ICS with MSC Server assisted mid-call feature	Non-compliant	Not supported
12.2.3B	Call in alerting phase	Non-compliant	Not supported
12.2.4	Abnormal cases	7.0.0	NA
12.2.4.1	Confirmed dialog	7.0.0	NA
12.2.4.2	Early dialog	Non-compliant	Not supported
12.2.4.3	Moving from a 3GPP access to non-3GPP access colliding with SRVCC access transfer	7.0.0	NA
12.2A	SC UE procedures for PS to CS access transfer, vSRVCC	7.0.0	NA
12.2A.1	General	7.0.0	NA
12.2A.2	ICS-based	7.0.0	NA
12.2A.3	Not based on ICS	7.0.0	NA
12.2A.4	Void	7.0.0	NA
12.2A.5	Call in alerting phase	Non-compliant	Not supported
12.2A.5A	Call in pre-alerting phase	Non-compliant	Not supported
12.2A.6	Abnormal cases	7.0.0	NA
12.2B	SC UE procedures for CS to PS SRVCC	Non-compliant	CS to PS transfer not supported
12.3	SCC AS	7.0.0	NA
12.3.0	General	7.0.0	NA
12.3.0A	Distinction of requests sent to the SCC AS	7.0.0	NA
12.3.0B	Determine the transferable session set	7.0.0	NA
12.3.1	SCC AS procedures for PS to CS access transfer, PS to CS SRVCC	7.0.0	NA
12.3.2	SCC AS procedures for PS to CS access transfer with MSC server assisted mid-call feature, PS to CS SRVCC	Non-compliant	Not supported
12.3.3	SCC AS procedures for PS to CS SRVCC, abnormal case	7.0.0	NA
12.3.3.1	PS to CS SRVCC cancelled by MME/SGSN or failure by UE to transition to CS domain for ongoing session	7.0.0	NA
12.3.3.1A	PS to CS SRVCC cancelled by MME/SGSN or failure by UE to transition to CS domain for session in early dialog state	Non-compliant	Not supported
12.3.3.2	P-CSCF releasing the source access leg during PS to CS SRVCC	7.0.0	NA
12.3.3.3	P-CSCF releasing the source access leg when call is in alerting phase	Non-compliant	Not supported
12.3.3.4	PS to CS SRVCC cancelled by MME/SGSN or release of the target access leg for an ongoing session	Non-compliant	Not supported. (Q.850 is never checked for).
12.3.3.5	PS to CS SRVCC cancelled by MME/SGSN or release of the target access leg for a session in an early dialog phase	Non-compliant	Not supported
12.3.4	SCC AS procedures for PS to CS access transfer when call is in alerting phase or pre-alerting phase	Non-compliant	Not supported
12.3.5	SCC AS procedures for PS to CS access transfer: PS to CS SRVCC enhancement using ATCF	7.0.0	NA
12.3.6	SCC AS procedures for PS to CS access transfer, vSRVCC	7.0.0	NA
12.3.6.0	Determine the transferable session set	7.0.0	NA
12.3.6.1	General	7.0.0	NA
12.3.6.2	SCC AS procedures for PS to CS access transfer when call is in alerting phase, vSRVCC	Non-compliant	Not supported
12.3.6.3	SCC AS procedures for PS to CS access transfer: vSRVCC enhancement using ATCF	7.0.0	NA
12.3.6.4	SCC AS procedures for vSR-VCC, abnormal case	7.0.0	NA
12.3.7	SCC AS procedures for handling of SIP OPTIONS request	7.0.0	NA
12.3.8	Removal of non-transferred audio media components and superfluous sessions	7.0.0	NA
12.3.9	Charging correlation	Non-compliant	P-Charging-Vector is not examined
12.3.10	SCC AS procedures for CS to PS SRVCC	Non-compliant	Not supported
12.4	MSC server enhanced for ICS	7.0.0	NA
12.4.0	MSC server enhanced for ICS supporting PS to CS SRVCC	7.0.0	NA
12.4.0A	MSCserverenhancedforICSproceduresforEmergencySession Transfer	7.0.0	Note that OCECAS is not considered an EATF
12.4.0B	MSC server enhanced for ICS supporting vSRVCC	7.0.0	NA
12.4.1	Void	7.0.0	NA
12.4.2	MSC server enhanced for ICS supporting CS to PS SRVCC	Non-compliant	Not supported
12.4.3	Abnormal cases	7.0.0	NA
12.4A	MSC server assisted mid-call feature	Non-compliant	Not supported
12.5	EATF	7.0.0	Note that OCECAS is not considered an EATF
12.6	MSC server enhanced for SRVCC using SIP interface	7.0.0	NA
12.6.1	Session transfer from MSC server enhanced for SRVCC using SIP interface	7.0.0	NA
12.6.2	Emergency session transfer from MSC server enhanced for SRVCC using SIP interface	7.0.0	Note that OCECAS is not considered an EATF
12.6.3	MSC server enhanced for SRVCC using SIP interface procedures for PS to CS access transfer for calls in alerting phase or pre- alerting phase	Non-compliant	Not supported
12.6.4	Abnormal cases	7.0.0	NA
12.7	Access Transfer Control Function (ATCF)	7.0.0	NA
12.7.1	Distinction of requests	7.0.0	NA
12.7.2	ATCF procedures for PS to CS access transfer, PS to CS SRVCC	7.0.0	NA
12.7.3	ATCF procedures for CS to PS SRVCC	Non-compliant	Not supported
13	Roles for media adding/deleting for access transfer	7.0.0	NA
13.1	Introduction	7.0.0	NA
13.2	SC UE	7.0.0	NA
13.3	SCC AS	7.0.0	NA
13.3.1	Adding or removing media through Gm	7.0.0	NA
13.3.2	Adding Gm control to existing CS session	7.0.0 (Partial)	Comparison of the media lines is not performed
14	Void	7.0.0	NA
15	Void	7.0.0	NA
16	Void	7.0.0	NA
17	Void	7.0.0	NA
18	Void	7.0.0	NA
19	Void	7.0.0	NA
20	Service continuity and MMTEL interactions	7.0.0	NA
20.1	Roles for access transfer and supplementary services interaction	7.0.0	NA
20.1.1	Introduction	7.0.0	NA
20.1.2	Originating Identification Presentation (OIP)	7.0.0	NA
20.1.3	Originating Identification Restriction (OIR)	7.0.0	NA
20.1.4	Terminating Identification Presentation (TIP)	7.0.0	NA
20.1.5	Terminating Identification Restriction (TIR)	7.0.0	NA
20.1.6	Communication Diversion (CDIV)	7.0.0	NA
20.1.7	Communication Hold (HOLD)	Non-compliant	Not supported with SRVCC
20.1.8	Communication Barring (CB)	7.0.0	NA
20.1.9	Message Waiting Indication (MWI)	Non-compliant	Not supported
20.1.10	Conference (CONF)	Non-compliant	Not supported with SRVCC
20.1.11	Explicit Communication Transfer (ECT)	Non-compliant	Not supported
20.1.12	Advice of Charge (AOC)	Non-compliant	Not supported
20.1.13	Closed User Groups (CUG)	Non-compliant	Not supported
20.1.14	Three-Party (3PTY)	Non-compliant	Not supported
20.1.15	Flexible Alerting (FA)	Non-compliant	Not supported
20.1.16	Communication Waiting (CW)	Non-compliant	Not supported
20.1.17	Completion of Communications to Busy Subscriber (CCBS)/Completion of Communications by No Reply (CCNR)	7.0.0	NA
20.1.18	Customized Alerting Tones (CAT)	7.0.0	NA
20.1.19	Malicious Communication IDentification (MCID)	7.0.0	NA
20.1.20	Reverse Charging	7.0.0	Noted
20.1.21	Personal Network Management (PNM)	7.0.0	Noted
20.1.22	Customized Ringing Signal (CRS)	7.0.0	Noted
20.2	Void	7.0.0	NA
21	Void	7.0.0	NA
22	Roles for detection of remote leg information	7.0.0	NA
22.1	Introduction	7.0.0 (Partial)	g.3gpp.remote-leg-info feature-capability is never checked for.
22.2	MSC server enhanced for ICS	7.0.0	NA
22.2.1	Distinction of requests	7.0.0	NA
22.2.2	Discover remote leg information	7.0.0	NA
22.3	SCC AS	7.0.0	NA
22.3.1	Distinction of requests	Non-compliant	Not supported
22.3.2	Providing remote leg information	Non-compliant	Not supported

3GPP_TS_24.604 Compliance

Table 1-7 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.604 (v12.5.0), "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-7 PICS_3GPP_TS_24.604

Section Number	Section Title	Product Release	Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Communications Diversion (CDIV)	7.0.0	NA
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	NA
4.2.1	General description	7.0.0	NA
4.2.1.1	Service description	7.0.0	Notifications are not configured out-of-the-box, but are configurable through the SIP message activity, or outbound HTTP messages.
4.2.1.2	Communication Forwarding Unconditional (CFU)	7.0.0	As a service provider option, a subscription option can be provided to enable the served user to receive a reminder indication that the CFU service has been activated. This option is not configured out-of-the-box, but is configurable with an HSS query followed by the SIP message activity.
4.2.1.3	Communication Forwarding on Busy user (CFB)	7.0.0	As a service provider option, a subscription option can be provided to enable the served user to receive a reminder indication that the CFB service has been activated. This option is not configured out-of-the-box, but is configurable with an HSS query followed by the SIP message activity.
4.2.1.4	Communication Forwarding on no Reply (CFNR)	7.0.0	As a service provider option, a subscription option can be provided to enable the served user to receive a reminder indication that the CFNR service has been activated. This option is not configured out-of-the-box, but is configurable with an HSS query followed by the SIP message activity.
4.2.1.5	Communication Forwarding on Subscriber Not Reachable (CFNRc)	7.0.0	As a service provider option, a subscription option can be provided to enable the served user to receive a reminder indication that the CFNRc service has been activated. This option is not configured out-of-the-box, but is configurable with an HSS query followed by the SIP message activity.
4.2.1.6	Communication Deflection (CD)	7.0.0	NA
4.2.1.7	Communication Forwarding on Not Logged-in (CFNL)	7.0.0 (Partial)	As a service provider option, a subscription option can be provided to enable the served user to receive a reminder indication that the CFNL service has been activated. This option is not supported.
4.2.1.8	Void	7.0.0	NA
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0 (Partial)	Table 4.3.1.1: Subscription options for CDIV services. Only the following options are configured out-of-the-box: Originating user receives notification that his communication has been diverted (forwarded or deflected). Other notifications would require re-configuration of the VoLTE Control Flows to include served-user preference lookup and subsequent notification. Table 4.3.1.2: Network provider options for CDIV services. Only the following options are supported: Total number of all diversions for each communication. AS behavior when the maximum number of diversions for a communication is reached. AS behavior when the maximum number of diversions for a communication is reached.
4.3.2	Requirements on the originating network side	7.0.0	Noted
4.3.3	Requirements in the network	7.0.0	Noted
4.4	Coding requirements	7.0.0	NA
4.4.0	General	7.0.0	Noted
4.4.1	SIP-Messages	7.0.0	NA
4.4.1.1	SIP messages for redirection	7.0.0 (Partial)	REFER method not supported.
4.4.1.2	Void	7.0.0	NA
4.4.2	Parameters	7.0.0	Noted
4.5	Signalling requirements	7.0.0	NA
4.5.0	General	7.0.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1	Activation/deactivation	7.0.0	NA
4.5.1a	Registration/erasure	7.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1b	Interrogation	7.0.0 (Partial)	Interrogation will be via the platform's UDR RESTful interface.
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the originating UA	7.0.0	Noted
4.5.2.2	Void	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Void	7.0.0	NA
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Actions at the AS of the diverting User	7.0.0	NA
4.5.2.6.0	General	7.0.0 (Partial)	AS always acts as a routing B2BUA. The AS shall based on local policy on how to handle PSAP callbacks suppress diversion when the received initial INVITE request towards the served user is identified as a PSAP callback. Handling PSAP callbacks is not implemented.
4.5.2.6.1	Checking of the diversion limits	7.0.0	NA
4.5.2.6.2	Setting of the diversion parameters by the AS	7.0.0	NA
4.5.2.6.2.1	Overview	7.0.0	NA
4.5.2.6.2.2	Diversion where served user is not last in received History-Info header	7.0.0	NA
4.5.2.6.2.3	Diversion with served user last in received History-Info header	7.0.0	NA
4.5.2.6.2.4	Overview of the operation	7.0.0	NA
4.5.2.6.3	Diversion procedures at the diverting AS	7.0.0	NA
4.5.2.6.4	Notification procedures of the originating user (Subscription Option)	7.0.0	NA
4.5.2.6.5	Indication of communication diversion to the diverting user /CDIV Notification (subscription option)	7.0.0	NA
4.5.2.6.5.0	General	7.0.0	NA
4.5.2.6.5.1	Void	7.0.0	NA
4.5.2.6.5.2	Void	7.0.0	NA
4.5.2.6.6	Not reachable indication	7.0.0	NA
4.5.2.7	Actions at the AS of the diverted-to user	7.0.0	AS always acts as a routing B2BUA.
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Void	7.0.0	NA
4.5.2.10	Void	7.0.0	NA
4.5.2.11	Void	7.0.0	NA
4.5.2.12	Void	7.0.0	NA
4.5.2.13	Void	7.0.0	NA
4.5.2.14	Void	7.0.0	NA
4.5.2.15	Actions at the diverted to UA	7.0.0	Noted
4.5.2.16	Actions at the diverting UA	7.0.0	Noted
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication Hold (HOLD)	7.0.0	Noted
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	NA
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	NA
4.6.4	Originating Identity Presentation (OIP)	7.0.0	NA
4.6.5	Originating Identity Restriction (OIR)	7.0.0	NA
4.6.6	Conference calling (CONF)	7.0.0	Noted
4.6.7	Communication diversion services (CDIV)	7.0.0	NA
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	Noted
4.6.9	Anonymous Communication Rejection and Communication Barring (ACR/CB)	7.0.0	NA
4.6.10	Explicit Communication Transfer (ECT)	Non-compliant	REFER method not supported.
4.6.10.1	Actions at the diverting AS	Non-compliant	REFER method not supported.
4.6.10.1.1	Determine whether ECT is applied to the diverted communication	Non-compliant	REFER method not supported.
4.6.10.1.2	Handling of transfer requests	Non-compliant	REFER method not supported.
4.6.10.1.3	Actions when CDIV is invoked again by the transferred communication	Non-compliant	REFER method not supported.
4.6.11	Communication Waiting (CW)	Non-compliant	CW not supported.
4.6.12	Completion of Communications to Busy Subscriber (CCBS)	Non-compliant	CCBS not supported.
4.6.13	Advice Of Charge (AOC)	7.0.0	Noted
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Parameter values (timers)	7.0.0	NA
4.8.1	No reply timer	7.0.0	NA
4.8.2	Void	7.0.0	NA
4.8.3	CDIV Indication Timer	Non-compliant	Parameter not supported.
4.9	Service Configuration for redirection services	7.0.0	NA
4.9.1	Structure of the XML Document	7.0.0	NA
4.9.1.0	General	Non-compliant	XCAP not supported. Configuration/provisioning will be via the platform's UDR RESTful interface. A mapping of XCAP XML elements to internal UDR view data has been documented.
4.9.1.1	Communication Diversion Element	7.0.0 (Partial)	Equivalent values may be configured via the platform's UDR RESTful interface.
4.9.1.1A	NoReplyTimer	7.0.0 (Partial)	Equivalent value may be configured via the platform's UDR RESTful interface.
4.9.1.2	Communication Diversion Rules	7.0.0 (Partial)	Equivalent ruleset may be configured via the platform's UDR RESTful interface.
4.9.1.3	Communication Diversion Rule Conditions	7.0.0 (Partial)	Equivalent rules may be configured via the platform's UDR RESTful interface. The following conditions are not supported: presence-status cp:sphere media ocp:external-list
4.9.1.4	Communication Diversion Rule Actions	7.0.0 (Partial)	Equivalent rules may be configured via the platform's UDR RESTful interface. The following optional actions are not supported: notify-caller reveal-served-user-identity-to-caller reveal-identity-to-caller - notify-served-user notify-served-user-on-outbound-call reveal-identity-to-target
4.9.1.5	Supported Actions and Conditions for Communication Diversion	7.0.0 (Partial)	XCAP not supported. Interrogation will be via the platform's UDR RESTful interface.
4.9.2	XML Schema	Non-compliant	XCAP not supported.
4.9.3	XML schema for indication of supported conditions and actions	Non-compliant	XCAP not supported.
4.10	Void	7.0.0	NA
Annex A (informative):	Signalling Flows	7.0.0	NA
A.1	Normal Cases	7.0.0	NA
A.1.1	Communication Forwarding unconditional	7.0.0	NA
A.1.2	Communication Deflection	7.0.0	NA
A.1.3	Communication forwarding on no reply	7.0.0	NA
A.1.4	Communication Forwarding on Busy	7.0.0	NA
A.1.5	Communication Forwarding Not Logged-in (CFNL)	7.0.0	NA
A.1.6	Void	7.0.0	NA
A.1.7	Service configuration	Non-compliant	XCAP not supported.
A.2	Interworking	7.0.0	NA
A.2.1	Communication Forwarding unconditional	7.0.0	NA
A.2.2	Communication Deflection	7.0.0	NA
Annex B (informative):	Example of filter criteria	7.0.0 (Partial)	PSAP not supported.
Annex C (informative):	Coding considerations	7.0.0	Noted
Annex D (informative):	Void	7.0.0	NA
Annex E (normative):	Void	7.0.0	NA
Annex F (informative):	Change history	7.0.0	NA

3GPP_TS_24.605 Compliance

Table 1-8 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.605 (v12.4.0), "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-8 3GPP TS 24 605

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	CONFerence (CONF)	7.0.0	NA
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	Noted
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	NA
4.3.2	Requirements on the originating network side	7.0.0	Noted
4.3.3	Requirements in the network	7.0.0	Noted
4.3.4	Requirements on the terminating network side	7.0.0	Noted
4.4	Coding requirements	7.0.0	See "3GPP_TS_24.147 Compliance" PICS
4.5	Signalling requirements	7.0.0	NA
4.5.1	Activation/deactivation	7.0.0	NA
4.5.1A	Registration/erasure	7.0.0	Noted
4.5.1B	Interrogation	7.0.0	Noted
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the originating UE	7.0.0	NA
4.5.2.1.1	User joining a conference	7.0.0	NA
4.5.2.1.2	User inviting another user to a conference	7.0.0	NA
4.5.2.1.3	User leaving a conference	7.0.0	NA
4.5.2.1.4	User creating a conference	7.0.0	NA
4.5.2.1.5	Subscription for the conference event package	7.0.0	NA
4.5.2.2	Actions at the conferencing AS	7.0.0	NA
4.5.2.2.1	Conference focus	7.0.0 (Partial)	The P-Charging-Vector is not added to the initial response. The identity and the referred-by fields are not validated. 24.147 5.3.2.3 (Starting a conference using an INVITE with a recipient-list) is not supported.
4.5.2.2.1A	Void	7.0.0	NA
4.5.2.2.2	Conference notification service	Non-compliant	Not supported.
4.5.2.2A	Procedures at the AS serving the originating user	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Void	7.0.0	NA
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Void	7.0.0	NA
4.5.2.7	Actions at the destination UE	7.0.0	NA
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Void	7.0.0	NA
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication Hold (HOLD)	7.0.0	NA
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	Noted
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	NA
4.6.4	Originating Identity Presentation (OIP)	7.0.0	Noted
4.6.5	Originating Identity Restriction (OIR)	7.0.0 (Partial)	The referred-by header field is not checked for privacy when constructing INVITEs.
4.6.6	Conference calling (CONF)	7.0.0	NA
4.6.7	Communication diversion services (CDIV)	7.0.0	Noted
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	Noted
4.6.9	Anonymous Communication Rejection and Communication Barring (ACR/CB)	Non-compliant	Inbound REFER requests are not checked against OCB rules.
4.6.10	Explicit Communication Transfer (ECT)	7.0.0	Noted
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Parameter values (timers)	7.0.0	NA

3GPP_TS_24.607 Compliance

Table 1-9 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.607 (v12.2.0), "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-9 PICS_3GPP_TS_24.607

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)	7.0.0	NA
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	Noted
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	NA
4.3.1.1	OIP Provision/withdrawal	7.0.0	NA
4.3.1.2	OIR Provision/withdrawal	7.0.0	NA
4.3.2	Requirements on the originating network side	7.0.0	Noted
4.3.3	Requirements on the terminating network side	7.0.0	Noted
4.4	Syntax requirements	7.0.0	Noted
4.5	Signalling procedures	7.0.0	NA
4.5.0	General	7.0.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1	Activation/deactivation	7.0.0	Noted
4.5.1A	Registration/erasure	7.0.0	Noted
4.5.1B	Interrogation	7.0.0 (Partial)	Interrogation will be via the platform's UDR RESTful interface.
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the originating UE	7.0.0	Noted
4.5.2.2	Void	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Actions at the AS serving the originating UE	7.0.0	Additionally, based on operator policy, the AS shall either modify the From header field to remove the identification information, or add a Privacy header field set to "user". OCECAS will add a Privacy header field set to "user". As an originating network option, if the "no screening" special arrangement does not exist with the originating user, the AS may attempt to match the information in the From header with the set of registered public identities of the originating user. If a match is not found, the AS may set the From header to the SIP URI that includes the default public user identity. This option is not supported.
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Void	7.0.0	NA
4.5.2.7	Void	7.0.0	NA
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Actions at the AS serving the terminating UE	7.0.0	Additionally, the Application Server may as a network option anonymize the contents of the From header by setting it to a default non significant value. This option is not supported. As a network option, if the terminating user has an override category, the AS shall send the P Asserted Identity headers and remove the Privacy header fields. This option is not supported.
4.5.2.10	Void	7.0.0	NA
4.5.2.11	Void	7.0.0	NA
4.5.2.12	Actions at the terminating UE	7.0.0	Noted
4.6	Interaction with other services	-	NA
4.6.1	Communication Hold (HOLD)	7.0.0	NA
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	NA
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	NA
4.6.4	Originating Identity Presentation (OIP)	7.0.0	Note: OIP override category is not supported
4.6.5	Originating Identity Restriction (OIR)	7.0.0	Note: OIP override category is not supported
4.6.6	Conference calling (CONF)	7.0.0	NA
4.6.7	Communication diversion services (CDIV)	7.0.0	Note: OIP override category is not supported
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	NA
4.6.9	Incoming Communication Barring (ICB)	7.0.0	NA
4.6.10	Explicit Communication Transfer (ECT)	7.0.0	NA
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Signalling flows	7.0.0	Noted
4.9	Parameter values (timers)	7.0.0	Noted
4.10	Service configuration	7.0.0	NA
4.10.0	General	Non-compliant	XCAP not supported. Configuration/provisioning will be via the platform's UDR RESTful interface.
4.10.1	Data semantics	Non-compliant	XCAP not supported.
4.10.2	XML schema	Non-compliant	XCAP not supported.
Annex A (informative):	Signalling flows	7.0.0	NA
Annex B (informative):	Example of filter criteria	7.0.0	NA
B.1	Originating filter criteria for OIR service	7.0.0	Noted
B.2	Terminating filter criteria for OIP service	7.0.0	Noted
Annex C (informative):	Change history	7.0.0	NA

3GPP_TS_24.608 Compliance

Table 1-10 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.608 (v12.0.0), "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-10 PICS_3GPP_TS_24.608

Section Number	Section Title	Product Release	Release Caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)	7.0.0	NA
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	Noted
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	NA
4.3.1.1	TIP provision/withdrawal	7.0.0	NA
4.3.1.2	TIR provision/withdrawal	7.0.0	NA
4.3.2	Requirements on the originating network side	7.0.0	Override option not supported.
4.3.3	Requirements on the terminating network side	7.0.0	Noted
4.4	Syntax requirements	7.0.0	Noted
4.5	Signalling procedures	7.0.0	NA
4.5.0	General	7.0.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1	Activation/deactivation	7.0.0	Noted
4.5.1A	Registration/erasure	7.0.0	Noted
4.5.1B	Interrogation	7.0.0 (Partial)	Interrogation will be via the platform's UDR RESTful interface.
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the originating UE	7.0.0	Noted
4.5.2.2	Void	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Actions at the AS serving the originating UE	7.0.0	As a network option, if the originating user has an override category, the AS shall send the P-Asserted-Identity headers and remove the Privacy header fields. This option is not supported.
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Void	7.0.0	NA
4.5.2.7	Void	7.0.0	NA
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Actions at the AS serving the terminating UE	7.0.0	As a terminating network option, if the "no screening" special arrangement does not exist with the terminating user and an UPDATE request is received from the terminating user, then the AS may attempt to match the information in the From header with the set of registered public user identities for the served user. If no match is found, the AS may change the value of the From header in the UPDATE request to the public user identity of the served user. This option is not supported.
4.5.2.10	Void	7.0.0	NA
4.5.2.11	Void	7.0.0	NA
4.5.2.12	Actions at the terminating UE	7.0.0	Noted
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication Hold (HOLD)	7.0.0	NA
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	Note: override category is not supported
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	Note: override category is not supported
4.6.4	Originating Identity Presentation (OIP)	7.0.0	NA
4.6.5	Originating Identity Restriction (OIR)	7.0.0	NA
4.6.6	Conference calling (CONF)	7.0.0	NA
4.6.7	Communication diversion services (CDIV)	7.0.0	NA
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	NA
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Parameter values (timers)	7.0.0	NA
4.9	Service configuration	7.0.0	NA
4.9.0	General	Non-compliant	XCAP not supported. Configuration/provisioning will be via the platform's UDR RESTful interface. A mapping of XCAP XML elements to internal UDR view data has been documented.
4.9.1	Data semantics	Non-compliant	XCAP not supported.
4.9.2	XML schema	Non-compliant	XCAP not supported.
Annex A (informative):	Signalling flows	7.0.0	NA
Annex B (informative):	Example of filter criteria	7.0.0	NA
B.1	Originating IFC for TIP service	7.0.0	Noted
B.2	Terminating IFC for TIR service	7.0.0	Noted
Annex C (informative):	Void	7.0.0	NA
Annex D (informative):	Change history	7.0.0	NA

3GPP_TS_24.610 Compliance

Table 1-11 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.610 (v12.6.0), "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-11 3GPP_TS_24.610

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Communication Hold (HOLD)	7.0.0	NA
4.1	Void	7.0.0	NA
4.2	Description	7.0.0	NA
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	Noted
4.3.2	Requirements on the originating network side	7.0.0	Noted
4.3.3	Requirements in the network	7.0.0	Noted
4.3.4	Requirements on the terminating network side	7.0.0	Noted
4.4	Coding requirements	7.0.0	Noted
4.5	Signalling requirements	7.0.0	NA
4.5.1	Activation/deactivation	7.0.0	Noted
4.5.1A	Registration/erasure	7.0.0	Noted
4.5.1B	Interrogation	7.0.0	Noted
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the invoking UE	7.0.0	Noted
4.5.2.2	Void	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Actions at the AS of the invoking UE	7.0.0 (Partial)	As a network option, for each media stream marked "recvonly" in the SDP answer sent to the invoking UE, the AS of the invoking UE shall lower the bandwidth by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800". This is not supported. As a network option, for each media stream marked "inactive" in the SDP answer sent to the invoking UE, the AS of the invoking UE shall lower the bandwidth by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800". This is not supported. The AS shall based on local policy on how to handle PSAP callbacks reject any HOLD invocation request from the served UE by sending a 403 (Forbidden) response. Handling of PSAP callbacks is not supported.
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Void	7.0.0	NA
4.5.2.7	Void	7.0.0	NA
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Void	7.0.0	NA
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication Hold (HOLD)	7.0.0	Noted
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	Noted
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	Noted
4.6.4	Originating Identity Presentation (OIP)	7.0.0	Noted
4.6.5	Originating Identity Restriction (OIR)	7.0.0	Noted
4.6.6	Conference calling (CONF)	7.0.0	Noted
4.6.7	Communication diversion services (CDIV)	7.0.0	Noted
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	Noted
4.6.9	Anonymous Communication Rejection and Communication Barring (ACR/CB)	7.0.0	Noted
4.6.10	Explicit Communication Transfer (ECT)	7.0.0	Noted
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Parameter values (timers)	7.0.0	Noted
Annex A (informative):	Signalling flows	7.0.0	NA
A.1	HOLD communication	7.0.0	Noted
A.1.1	HOLD communication without announcement	7.0.0	NA
A.1.2	HOLD communication with announcement	7.0.0	NA
A.1.3	HOLD communication with modification of the SDP answer	Non-compliant	Session description protocol (SDP) modification is not supported.
A.2	RESUME Communication	7.0.0	NA
A.2.1	RESUME communication without announcement	7.0.0	NA
A.2.2	RESUME communication with announcement	7.0.0	NA
Annex B (informative):	Example of filter criteria	7.0.0 (Partial)	Public Safety Answering Point (PSAP) is not supported.
Annex C (informative):	Change history	7.0.0	NA

3GPP_TS_24.611 Compliance

Table 1-12 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 24.611 (v12.4.0), "Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol specification.”

Table 1-12 3GPP_TS_24.611

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Anonymous Communication Rejection (ACR) and Communication Barring (CB)	7.0.0	NA
4.1	Introduction	7.0.0	Noted
4.2	Description	7.0.0	NA
4.2.1	General description	7.0.0	Noted
4.3	Operational requirements	7.0.0	NA
4.3.1	Provision/withdrawal	7.0.0	Noted
4.3.2	Requirements on the originating network side	7.0.0	Noted
4.3.3	Requirements in the network	7.0.0	Noted
4.3.4	Requirements on the terminating network side	7.0.0	Noted
4.4	Coding requirements	7.0.0	NA
4.4.1	ICB coding requirements	7.0.0	Noted
4.4.2	ACR coding requirements	7.0.0	Noted
4.4.3	OCB coding requirements	7.0.0	Noted
4.5	Signalling requirements	7.0.0	NA
4.5.0	General	7.0.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1	Activation/deactivation	7.0.0 (Partial)	Self-care provisioning by subscribers through XCAP is not supported. Alternatives using the UDR REST interface, or the media server, or SIP dial strings (as per TS 24.238)
4.5.1a	Registration/erasure	7.0.0 (Partial)	Configuration/provisioning will be via the platform's UDR RESTful interface.
4.5.1b	Interrogation	7.0.0 (Partial)	Interrogation will be via the platform's UDR RESTful interface.
4.5.2	Invocation and operation	7.0.0	NA
4.5.2.1	Actions at the originating UE	7.0.0	Noted
4.5.2.2	Void	7.0.0	NA
4.5.2.3	Void	7.0.0	NA
4.5.2.4	Actions at the originating AS	7.0.0	AS always acts as a routing B2BUA.
4.5.2.5	Void	7.0.0	NA
4.5.2.6	Actions at the terminating AS	7.0.0	NA
4.5.2.6.1	Actions for ICB at the terminating AS	7.0.0 (Partial)	AS always acts as a routing B2BUA. The AS shall based on local policy on how to handle PSAP callbacks suppress ICB when the received initial INVITE request towards the served user is identified as a PSAP callback. Handling PSAP callbacks is not supported. The dynamic ICB is a network option to extend the ICB functionality: Dynamic ICB is not supported.
4.5.2.6.2	Action for ACR at the terminating AS	7.0.0	NA
4.5.2.7	Void	7.0.0	NA
4.5.2.8	Void	7.0.0	NA
4.5.2.9	Void	7.0.0	NA
4.5.2.10	Void	7.0.0	NA
4.5.2.11	Void	7.0.0	NA
4.5.2.12	Void	7.0.0	NA
4.5.2.13	Actions at the destination UE	7.0.0	Noted
4.6	Interaction with other services	7.0.0	NA
4.6.1	Communication Hold (HOLD)	7.0.0	Noted
4.6.2	Terminating Identity Presentation (TIP)	7.0.0	NA
4.6.3	Terminating Identity Restriction (TIR)	7.0.0	NA
4.6.4	Originating Identity Presentation (OIP)	7.0.0 (Partial)	OIP override category is not supported
4.6.5	Originating Identity Restriction (OIR)	7.0.0	NA
4.6.6	Conference calling (CONF)	7.0.0	Noted
4.6.7	Communication diversion services (CDIV)	7.0.0	Noted
4.6.8	Malicious Communication IDentification (MCID)	7.0.0	Noted
4.6.9	Explicit Communication Transfer (ECT)	7.0.0	Noted
4.7	Interactions with other networks	7.0.0	NA
4.7.1	Void	7.0.0	NA
4.7.2	Void	7.0.0	NA
4.7.3	Void	7.0.0	NA
4.8	Parameter values (timers)	7.0.0	Noted
4.9	Service configuration	7.0.0	NA
4.9.1	Structure of the XML Document	7.0.0	NA
4.9.1.0	Definitions	7.0.0	Noted
4.9.1.1	General	Non-compliant	XCAP not supported. Configuration/provisioning will be via the platform's UDR RESTful interface.
4.9.1.2	Communication Barring elements	7.0.0 (Partial)	Equivalent values may be configured via the platform's UDR RESTful interface.
4.9.1.3	Communication Barring rules	7.0.0 (Partial)	Equivalent rule set may be configured through the platform's UDR RESTful interface.
4.9.1.4	Communication Barring rule conditions	7.0.0 (Partial)	Equivalent rules may be configured via the platform's UDR RESTful interface. The following conditions are not supported: presence-status media cp:sphere ocp:external-list ocp:other-identity
4.9.1.5	Communication Barring rule actions	7.0.0 (Partial)	Equivalent rules may be configured via the platform's UDR RESTful interface.
4.9.1.6	Supported Conditions for Communication Barring	7.0.0 (Partial)	XCAP not supported. Interrogation will be via the platform's UDR RESTful interface.
4.9.2	XML Schema	Non-compliant	XCAP not supported.
4.9.3	XML schema for indication of supported conditions and actions	Non-compliant	XCAP not supported.
Annex A (informative):	Signalling flows	7.0.0	NA
A.1	ACR termination towards UE-B	7.0.0	NA
A.2	Service configuration	Non-compliant	XCAP not supported.
Annex B (informative):	Example of filter criteria	7.0.0 (Partial)	PSAP not supported.
Annex C (informative):	Change history	7.0.0	NA

3GPP 29Series Compliance

This section describes the following:

• 3GPP_TS_29.328 Compliance

• 3GPP_TS_29.329 Compliance

3GPP_TS_29.328 Compliance

Table 1-13 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 29.328 (v12.7.0), "IP Multimedia (IM) Subsystem Sh interface, Signalling flows and message contents.”

Table 1-13 3GPP_TS_29.328

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	Main Concept	7.0.0	NA
5	General Architecture	7.0.0	NA
5.1	Functional requirements of network entities	7.0.0	NA
5.1.1	Functional Requirements of the Application Server	7.0.0	NA
5.1.2	Functional requirements of HSS	7.0.0	NA
5.1.3	Functional Requirements of the Presence Network Agent	7.0.0	NA
5.2	Functional classification of Sh interface procedures	7.0.0	NA
6	Procedure Descriptions	7.0.0	Noted
6.1	User data handling procedures	7.0.0	NA
6.1.1	Data read (Sh-Pull)	7.0.0	NA
6.1.1.1	Detailed behaviour	7.0.0	NA
6.1.2	Data Update (Sh-Update)	7.0.0	NA
6.1.2.1	Detailed behavior	7.0.0	Update-Eff feature not supported
6.1.3	Subscription to notifications (Sh-Subs-Notif)	7.0.0	NA
6.1.3.1	Detailed behavior	7.0.0	Update-Eff feature not supported
6.1.4	Notifications (Sh-Notif)	7.0.0	Notifications will update local copies of data, and explicitly initiate Control Flow Events
6.1.4.1	Detailed behavior	7.0.0	Notif-Eff feature not supported
6.2	AS permissions list	7.0.0	Noted
6.3	Void	7.0.0	NA
6.4	Void	7.0.0	NA
6.5	User identity to HSS resolution	Non-compliant	Not supported.
7	Procedure Descriptions	7.0.0	NA
7.1	User Identity	7.0.0	NA
7.1.1	IMS Public User Identity / Public Service Identity	7.0.0	NA
7.1.2	MSISDN	7.0.0	NA
7.1A	Wildcarded PSI	7.0.0	Not used by OCECAS
7.1B	Wildcarded Public User Identity	7.0.0	Not used by OCECAS
7.2	Requested Domain	7.0.0	NA
7.2A	Requested Nodes	7.0.0	NA
7.2B	Serving Node Indication	7.0.0	Not used by OCECAS
7.3	Requested Data	7.0.0	NA
7.4	Service Indication	7.0.0	NA
7.5	Result	7.0.0	NA
7.6	Data	7.0.0	Note that a number of the following data elements are not configured out-of-the-box, but are possible using Control Flow configuration (probably relying on the Generate Document node to construct the data xml)
7.6.1	Repository Data	7.0.0	NA
7.6.2	IMSPublicIdentity	7.0.0	NA
7.6.3	IMS User State	7.0.0	NA
7.6.4	S-CSCF Name	7.0.0	NA
7.6.5	Initial Filter Criteria	7.0.0	NA
7.6.6	Location Information	7.0.0	NA
7.6.6.1	Location Information for CS	7.0.0	NA
7.6.6.2	Location Information for GPRS	7.0.0	NA
7.6.6.3	Location Information for EPS	7.0.0	NA
7.6.6.4	Location Information for TWAN	7.0.0	NA
7.6.7	User state	7.0.0	NA
7.6.8	Charging information	7.0.0	NA
7.6.9	MSISDN	7.0.0	NA
7.6.9A	Extended MSISDN	7.0.0	NA
7.6.10	PSIActivation	7.0.0	NA
7.6.11	DSAI	7.0.0	NA
7.6.12	Void	7.0.0	NA
7.6.13	Service Level Trace Information	7.0.0	NA
7.6.14	Service Priority Level	7.0.0	NA
7.6.15A	Extended Priority	7.0.0	NA
7.6.16	SMSRegistrationInfo	7.0.0	NA
7.6.17	UE reachability for IP	7.0.0	NA
7.6.18	T-ADS Information	7.0.0	NA
7.6.19	Private Identity	7.0.0	NA
7.6.20	STN-SR	7.0.0	NA
7.6.21	UE SRVCC Capability	7.0.0	NA
7.6.22	CSRN	7.0.0	NA
7.6.23	Reference Location Information	7.0.0	NA
7.6.24	IMSI	7.0.0	NA
7.6.25	IMSPrivateUserIdentity	7.0.0	NA
7.7	Subscription request type	7.0.0	NA
7.8	Current Location	7.0.0	NA
7.9	Application Server Identity	7.0.0	NA
7.10	Application Server Name	7.0.0	NA
7.11	Requested Identity Set	7.0.0	NA
7.12	Expiry Time	7.0.0	NA
7.13	Send Data Indication	7.0.0	NA
7.14	DSAI Tag	7.0.0	NA
7.15	Session-Priority	7.0.0	NA
7.16	One Time Notification	7.0.0	NA
7.17	Repository Data ID	7.0.0	NA
7.18	Pre-paging Supported	7.0.0	NA
7.19	Local Time Zone Indication	7.0.0	NA
7.20	UDR Flags	7.0.0	NA
7.21	Call Reference Info	7.0.0	NA
7.22	Call Reference Number	7.0.0	NA
7.23	AS-Number	7.0.0	NA
8	Protocol version identification	7.0.0	NA
9	Operational Aspects	7.0.0	See "3GPP_TS_29.329 Compliance" PICS
Annex A	Mapping of Sh operations and terminology to Diameter	7.0.0	NA
A.1	Introduction	7.0.0	NA
A.2	Sh message to Diameter command mapping	7.0.0	NA
A.3	Void	7.0.0	NA
Annex B	Message flow	7.0.0	Noted
Annex C	UML model of the data downloaded over Sh interface	7.0.0	Noted
Annex D	XML schema for the Sh interface user profile	7.0.0	NA
Annex E	T-ADS request handling in the HSS	7.0.0	Noted
Annex F	Diameter overload control mechanism	7.0.0	NA
F.1	General	Non-compliant	Not supported.
F.2	HSS behavior	Non-compliant	Not supported.
F.3	AS behavior	Non-compliant	Not supported.
Annex G	Diameter overload node behavior	Non-compliant	Not supported.
Annex H	Change history	7.0.0	Noted

3GPP_TS_29.329 Compliance

Table 1-14 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 29.329 (v12.5.0), "Sh interface based on the Diameter protocol Protocol details.”

Table 1-14 3GPP_TS_29.329

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Abbreviations	7.0.0	Noted
4	General	7.0.0	NA
5	Use of the Diameter base protocol	7.0.0	NA
6	Diameter application for Sh interface	7.0.0	NA
6.1	Command-code values	7.0.0	All mandatory parameters are sent, but several optional parameters are never used.
6.1.1	User-Data-Request (UDR) Command	7.0.0	NA
6.1.2	User-Data-Answer (UDA) Command	7.0.0	NA
6.1.3	Profile-Update-Request (PUR) Command	7.0.0	NA
6.1.4	Profile-Update-Answer (PUA) Command	7.0.0	NA
6.1.5	Subscribe-Notifications-Request (SNR) Command	7.0.0	NA
6.1.6	Subscribe-Notifications-Answer (SNA) Command	7.0.0	NA
6.1.7	Push-Notification-Request (PNR) Command	7.0.0	NA
6.1.8	Push-Notifications-Answer (PNA) Command	7.0.0	NA
6.2	Result-Code AVP values	7.0.0	NA
6.2.1	Success	7.0.0	NA
6.2.2	Permanent Failures	7.0.0	NA
6.2.2.1	DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100)	7.0.0	NA
6.2.2.2	DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101)	7.0.0	NA
6.2.2.3	DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102)	7.0.0	NA
6.2.2.4	DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103)	7.0.0	NA
6.2.2.5	DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104)	7.0.0	NA
6.2.2.6	DIAMETER_ERROR_TOO_MUCH_DATA (5008)	7.0.0	NA
6.2.2.7	DIAMETER_ERROR_TRANSPARENT_DATA OUT_OF_SYNC (5105)	7.0.0	NA
6.2.2.8	DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011)	7.0.0	NA
6.2.2.9	DIAMETER_ERROR_SUBS_DATA_ABSENT (5106)	7.0.0	NA
6.2.2.10	DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107)	7.0.0	NA
6.2.2.11	DIAMETER_ERROR_DSAI_NOT_AVAILABLE (5108)	7.0.0	NA
6.2.2.12	DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002)	7.0.0	NA
6.2.3	Transient Failures	7.0.0	NA
6.2.3.1	DIAMETER_USER_DATA_NOT_AVAILABLE (4100)	7.0.0	NA
6.2.3.2	DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101)	7.0.0	NA
6.3	AVPs	7.0.0	For the AVPs in this section, most are not configured, but can be with alterations to the groovy scripts in csp.xml.
6.3.1	User-Identity AVP	7.0.0	NA
6.3.2	MSISDN AVP	7.0.0 (Partial)	Not used by default. OCECAS cannot encode a Telephony Binary Coded Decimal (TBCD) string, so only possible if extracted from an inbound string.
6.3.3	User-Data AVP	7.0.0	NA
6.3.4	Data-Reference AVP	7.0.0	NA
6.3.5	Service-Indication AVP	7.0.0 (Partial)	Not used by default. OCECAS cannot encode the octetString, so only possible if extracted from an inbound string.
6.3.6	Subs-Req-Type AVP	7.0.0	NA
6.3.7	Requested-Domain AVP	7.0.0	Not used by default
6.3.7A	Requested-Notes AVP	7.0.0	Not used by default
6.3.8	Current-Location AVP	7.0.0	Not used by default
6.3.9	Server-Name AVP	7.0.0	Not used by default
6.3.10	Identity-Set AVP	7.0.0	Not used by default
6.3.11	Supported-Features AVP	7.0.0	Not used by default
6.3.12	Feature-List AVP	7.0.0	Not used by default
6.3.13	Feature-List AVP	7.0.0	Not used by default
6.3.14	Supported-Applications AVP	7.0.0	Not used by default
6.3.15	Public-Identity AVP	7.0.0	NA
6.3.16	Expiry-Time AVP	7.0.0	Not used by default
6.3.17	Send-Data-Indication AVP	7.0.0	Not used by default
6.3.18	DSAI-Tag AVP	7.0.0 (Partial)	Not used by default. OCECAS does not support this AVP type. To use this AVP, extract it from the inbound message, and use it as a string.
6.3.19	Wildcarded-Public-Identity AVP	7.0.0	Not used by default
6.3.20	Wildcarded-IMPU AVP	7.0.0	Not used by default
6.3.21	Session-Priority AVP	7.0.0	Not used by default
6.3.22	One-Time-Notification AVP	7.0.0	Not used by default
6.3.23	Serving-Node-Indication AVP	7.0.0	Not used by default
6.3.24	Repository-Data-ID AVP	7.0.0	Not used by default
6.3.25	Sequence-Number AVP	7.0.0	Not used by default
6.3.26	Pre-paging-Supported AVP	7.0.0	Not used by default
6.3.27	Local-Time-Zone-Indication AVP	7.0.0	Not used by default
6.3.28	UDR-Flags	7.0.0	Not used by default
6.3.29	Call-Reference-Info AVP	7.0.0 (Partial)	Not used by default
6.3.30	Call-Reference-Number AVP	7.0.0 (Partial)	Not used by default. OCECAS does not support this AVP type. To use this AVP, extract it from the inbound message, and use it as a string.
6.3.31	AS-Number AVP	7.0.0 (Partial)	Not used by default. OCECAS does not support this AVP type. To use this AVP, extract it from the inbound message, and use it as a string.
6.3.32	OC-Supported-Features	7.0.0	Not used by default
6.3.33	OC-OLR	7.0.0	Not used by default
6.4	Use of namespaces	7.0.0	Noted
6.4.1	AVP codes	7.0.0	Noted
6.4.2	Experimental-Result-Code AVP values	7.0.0	Noted
6.4.3	Command Code values	7.0.0	Noted
6.4.4	Application-ID value	7.0.0	Noted
7	Special Requirements	7.0.0	NA
7.1	Version Control	Non-compliant	Notif-Eff, Update-Eff and Update-Eff-Enhance are not supported.

3GPP 32 Series Compliance

This section describes the following:

• 3GPP_TS_32.260 Compliance

• 3GPP_TS_32.275 Compliance

• 3GPP_TS_32.299 Compliance

3GPP_TS_32.260 Compliance

Table 1-15 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 32.260 (v12.6.0), "Telecommunication management; Charging management IP Multimedia Subsystem (IMS) charging.”

Table 1-15 3GPP_TS_32.260

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	Noted
2	References	7.0.0	Noted
3	Definitions, symbols and abbreviations	7.0.0	Noted
4	Architecture Considerations	7.0.0	Noted
4.1	High level IMS architecture	7.0.0	Noted
4.2	IMS offline charging architecture	7.0.0	Noted
4.3	IMS online charging architecture	7.0.0	Noted
5	Charging principles	7.0.0	NA
5.1	IMS charging principles	7.0.0	NA
5.1.0	Introduction	7.0.0	NA
5.1.1	IMS charging applicability	7.0.0	Ro/Rf choice is from configuration, not inbound messages
5.1.2	IMS charging correlation	7.0.0	NA
5.1.2.1	Basic principles for IMS domain correlation	7.0.0	NA
5.1.2.2	IMS Charging Identifier	7.0.0	NA
5.1.2.2A	Related ICID	Non-compliant	Not included in INVITE response
5.1.2.3	Access network charging identifier	7.0.0	NA
5.1.2.4	Inter Operator Identifier	7.0.0	Not used by default
5.1.2.5	void	7.0.0	NA
5.1.2.6	IMS visited network identifier	7.0.0	NA
5.1.3	SDP handling	7.0.0	NA
5.1.4	Trigger conditions	7.0.0	NA
5.1.5	IMS support of real-time tariff transfer	7.0.0	NA
5.1.6	Served user identification	7.0.0	NA
5.1.7	Single charging session from AS/ATCF acting as B2BUA	7.0.0	NA
5.1.8	Charging support for roaming architecture for voice over IMS with local breakout	7.0.0	Noted
5.1.9	Charging support for Network provided Location information	7.0.0	NA
5.1.9A	Charging support for IMS transit scenarios	7.0.0	NA
5.1.10	Charging support for TRF	7.0.0	NA
5.2	IMS offline charging principles	7.0.0	NA
5.2.1	Basic principles	7.0.0	NA
5.2.2	Message flows and types	7.0.0	NA
5.2.2.1	Message flows - successful cases and scenarios	7.0.0	NA
5.2.2.1.1	Session establishment - mobile origination	7.0.0	NA
5.2.2.1.2	Session establishment - mobile termination	7.0.0	NA
5.2.2.1.3	Mid-session procedures	7.0.0 (Partial)	re-INVITEs for modified media components are passed on without notifying the control flow, so are not chargeable.
5.2.2.1.4	Session release - mobile initiated	7.0.0	NA
5.2.2.1.5	Session-unrelated procedures	7.0.0	NA
5.2.2.1.6	Session establishment - PSTN initiated	7.0.0	NA
5.2.2.1.7	Session establishment - IMS initiated	7.0.0	NA
5.2.2.1.8	Session release - PSTN initiated	7.0.0	NA
5.2.2.1.9	Session release - IMS initiated	7.0.0	NA
5.2.2.1.10	Multi-Party call	7.0.0	NA
5.2.2.1.11	AS related procedures - AS acting as a redirect server	7.0.0	NA
5.2.2.1.12	AS related procedures - AS acting as a voice mail server	7.0.0	NA
5.2.2.1.13	AS Related Procedures - AS Acting as a SCC AS	7.0.0 (Partial)	CS to PS transfer not supported. PS to CS transfer cannot trigger a charging action, but it can be updated at charging timer expiry. (Otherwise flows are supported)
5.2.2.1.14	Initiating alternate charged party call	7.0.0	NA
5.2.2.1.15	Session establishment via IBCF to S-CSCF NA IMS initiated	7.0.0	-
5.2.2.1.16	AS related procedures - AS acting as a MMTel AS	7.0.0	See "3GPP_TS_32.275 Compliance" PICS
5.2.2.1.17	Session establishment via IBCF to a third party AS providing tariff information in real time (RTTI)	Non-compliant	OCECAS cannot manipulate the 200OK to include charging data
5.2.2.1.18	Third party AS providing tariff information in real time (RTTI) during the session	Non-compliant	OCECAS cannot initiate SIP info messages
5.2.2.1.19	Support of Optimal Media Routing (OMR)	7.0.0	NA
5.2.2.1.20	AS acting as a B2BUA - single charging session	7.0.0 (Partial)	re-INVITEs for modified media components are passed on without notifying the control flow, so are not chargeable.
5.2.2.1.21	Session establishment for roaming architecture for voice over IMS with local breakout	7.0.0	NA
5.2.2.1.22	Service continuity using ATCF	7.0.0	NA
5.2.2.2	Message flows - error cases and scenarios	7.0.0	NA
5.2.2.2.0	Introduction	7.0.0	NA
5.2.2.2.1	Session related SIP procedures - reception of SIP error messages	7.0.0	NA
5.2.2.2.2	Session related SIP procedures - SIP session failure	7.0.0	NA
5.2.2.2.3	Session unrelated SIP procedures	7.0.0	NA
5.2.2.2.4	CDF connection failure	7.0.0 (Partial)	On having no valid connection, the charging data is stored in the OCECAS EDRs, which must be manually updated to the CDF.
5.2.2.2.5	No reply from CDF	7.0.0	NA
5.2.2.2.6	Duplicate detection	7.0.0	NA
5.2.2.2.7	CDF detected failure	7.0.0	NA
5.2.3	CDR generation	7.0.0	NA
5.2.4	GTP' record transfer flows	7.0.0	NA
5.2.5	Bi CDR file transfer	7.0.0	NA
5.3	IMS online charging scenarios	7.0.0	NA
5.3.1	Basic principles	7.0.0 (Partial)	Not all mid-session changes are considered applicable to ECAS use cases, and are therefore not chargeable
5.3.2	Message flows and types	7.0.0	NA
5.3.2.0	Introduction	7.0.0	NA
5.3.2.1	Immediate Event Charging (IEC)	7.0.0	NA
5.3.2.1.0	Introduction	7.0.0	NA
5.3.2.1.1	Message flows - successful cases and scenarios	7.0.0	NA
5.3.2.1.1.1	IEC - Debit Units operation	7.0.0	NA
5.3.2.1.1.2	Scenarios	7.0.0	NA
5.3.2.1.2	Message flows - error cases and scenarios	7.0.0	NA
5.3.2.1.2.0	Introduction	7.0.0	NA
5.3.2.1.2.1	Reception of SIP error messages	7.0.0	NA
5.3.2.1.2.2	Debit Units operation failure	7.0.0	NA
5.3.2.1.2.3	Duplicate detection	7.0.0	NA
5.3.2.2	Event Charging with Unit Reservation (ECUR) and Session Charging with Unit Reservation (SCUR)	7.0.0	NA
5.3.2.2.0	General	7.0.0	NA
5.3.2.2.1	Message flows - successful cases and scenarios	7.0.0	NA
5.3.2.2.1.1	ECUR and SCUR - Reserve / Debit Units operations	7.0.0	NA
5.3.2.2.1.2	Expiration of reservation validity	7.0.0	NA
5.3.2.2.1.3	Scenarios	7.0.0 (Partial)	All scenarios are supported with the exception that not all reINVITES can trigger a charging update.
5.3.2.2.2	Message flows - error cases and scenarios	7.0.0	NA
5.3.2.2.2.0	Introduction	7.0.0	NA
5.3.2.2.2.1	Reception of SIP error messages	7.0.0	NA
5.3.2.2.2.2	Debit / Reserve Units operation failure	7.0.0	NA
5.3.2.2.2.3	Duplicate detection	7.0.0	NA
5.3.2.2.2.4	Aborted session setup	7.0.0	NA
5.3.2.3	IMS service termination by OCS	7.0.0	NA
5.3.2.3.0	Introduction	7.0.0	NA
5.3.2.3.1	Triggers on Ro interface which imply the termination of the IMS service	7.0.0	NA
5.3.2.3.2	Indication to the UE of the reason for IMS service release	7.0.0	NA
6	Definition of charging information	7.0.0	NA
6.1	Data description for IMS offline charging	7.0.0	NA
6.1.1	Rf message contents	7.0.0	NA
6.1.1.0	Introduction	7.0.0	NA
6.1.1.1	Charging Data Request message	7.0.0	NA
6.1.1.2	Charging Data Response message	7.0.0	NA
6.1.2	GTP' message contents	7.0.0	NA
6.1.3	CDR description on the Bi interface	7.0.0	NA
6.1.3.1	CDR content description	7.0.0	NA
6.1.3.2	CDR triggers	7.0.0	NA
6.1.3.2.1	Session related CDRs	7.0.0	NA
6.1.3.2.2	Session unrelated CDRs	7.0.0	NA
6.1.3.3	S-CSCF CDR content	7.0.0	Not relevant to OCECAS
6.1.3.4	P-CSCF CDR content	7.0.0	Not relevant to OCECAS
6.1.3.5	I-CSCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.6	MRFC CDR content	7.0.0	Not relevant to ECAS
6.1.3.7	MGCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.8	BGCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.9	SIP AS CDR content	7.0.0	NA
6.1.3.10	IBCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.11	E-CSCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.12	TRF CDR content	7.0.0	Not relevant to ECAS
6.1.3.13	ATCF CDR content	7.0.0	Not relevant to ECAS
6.1.3.14	TF CDR content	7.0.0	Not relevant to ECAS
6.2	Data description for IMS online charging	7.0.0	NA
6.2.1	Ro message contents	7.0.0	NA
6.2.1.0	Introduction	7.0.0	NA
6.2.1.1	Debit / Reserve Units Request message	7.0.0	NA
6.2.1.2	Debit / Reserve Units Response message	7.0.0	NA
6.3	IMS charging specific parameters	7.0.0	NA
6.3.1	Definition of IMS charging information	7.0.0	NA
6.3.1.0	General	7.0.0	NA
6.3.1.1	IMS charging information assignment for Service Information	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of PS information compliance
6.3.1.2	Definition of the IMS Information	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of specific field compliance
6.3.2	Detailed message format for offline charging	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of PS information compliance
6.3.3	Detailed message format for online charging	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of PS information compliance
6.3.4	Formal IMS charging parameter description	7.0.0	NA
6.3.4.1	IMS charging information for CDRs	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of specific field compliance
6.3.4.2	IMS charging information for charging events	7.0.0	See "3GPP_TS_32.299 Compliance" PICS for details of specific field compliance

3GPP_TS_32.275 Compliance

Table 1-16 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 32.275 (v12.2.0), "Telecommunication management, Charging management, MultiMedia Telephony (MMTel) charging."

Table 1-16 3GPP_TS_32.275

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	NA
2	References	7.0.0	NA
3	Definitions and abbreviations	7.0.0	NA
3.1	Definitions	7.0.0	Noted
3.2	Symbols	7.0.0	Noted
3.3	Abbreviations	7.0.0	Noted
4	Architecture considerations	7.0.0	NA
4.1	High level MMTel architecture	7.0.0	Noted
4.2	MMTel offline charging architecture	7.0.0	Noted
4.3	MMTel online charging architecture	7.0.0	Noted
5	MMTel charging principles and scenarios	7.0.0	NA
5.0	Introduction	7.0.0	OCECAS makes services available for offline and online without discrimination
5.1	MMTel charging principles	7.0.0	NA
5.1.1	Supplementary services invocation	7.0.0	Note that for all compliance in section 5, only online charging for originating flows is configured out-of-the box. (Terminating and Rf charging is possible through configuration).
5.1.1.1	OIP charging	7.0.0	NA
5.1.1.2	OIR charging	7.0.0	NA
5.1.1.3	TIP charging	7.0.0	NA
5.1.1.4	TIR charging	7.0.0	NA
5.1.1.5	HOLD charging	7.0.0	Hold charging is not configured on out-of-the-box.
5.1.1.6	CB charging	7.0.0	NA
5.1.1.7	CDIV charging	7.0.0	NA
5.1.1.8	CW charging	Non-compliant	Not supported.
5.1.1.9	ECT charging	Non-compliant	Not supported.
5.1.1.10	MWI charging	Non-compliant	Not supported.
5.1.1.11	CONF charging	7.0.0	Conference charging is not configured on out-of-the-box.
5.1.1.12	CCBS charging	Non-compliant	Not supported.
5.1.1.13	CCNR charging	Non-compliant	Not supported.
5.1.1.14	FA charging	Non-compliant	Not supported.
5.1.1.15	MCID charging	7.0.0	NA
5.1.1.16	CAT charging	Non-compliant	Not supported.
5.1.1.17	CUG charging	Non-compliant	Not supported.
5.1.1.18	PNM charging	7.0.0	PNM charging is not configured out-of-the-box
5.1.1.19	CRS charging	Non-compliant	Not supported.
5.1.1.20	Reverse charging	7.0.0	Not configured out-of-the-box
5.1.1.21	AoC charging	7.0.0	Not supported.
5.1.2	Supplementary services management by the user	7.0.0	Noted
5.2	MMTel offline charging scenarios	7.0.0	NA
5.2.1	Basic principles	7.0.0	NA
5.2.2	Diameter message flows	7.0.0	NA
5.2.2.0	Introduction	7.0.0	NA
5.2.2.1.1	Originating Identification Presentation (OIP) charging	7.0.0	NA
5.2.2.1.2	Originating Identification Restriction (OIR) charging	7.0.0	NA
5.2.2.1.3	Terminating Identification Presentation (TIP) charging	7.0.0	NA
5.2.2.1.4	Terminating Identification Restriction (TIR) charging	7.0.0	NA
5.2.2.1.5	Communication Hold (HOLD) charging	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.6	Communication Barring - CB (ICB/ACB) charging	7.0.0	NA
5.2.2.1.6.1	Communication Barring (CB) - ICB and Charging Data Request	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.6.2	Communication Barring (CB) - OCB	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.7	Communications Diversion (CDIV) charging	7.0.0	NA
5.2.2.1.7.1	Communications Diversions (CDIV) - successful establishment	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.7.2	Communications Diversion (CDIV) - release	7.0.0	NA
5.2.2.1.8	Communication Waiting (CW) charging	Non-compliant	Not supported.
5.2.2.1.9	Explicit Communication Transfer (ECT) charging	Non-compliant	Not supported.
5.2.2.1.9.1	Explicit Communication Transfer (ECT): Blind Transfer	Non-compliant	Not supported.
5.2.2.1.9.2	Explicit Communication Transfer (ECT): Release	Non-compliant	Not supported.
5.2.2.1.10	Message Waiting Indication (MWI) charging	Non-compliant	Not supported.
5.2.2.1.11	Conference (CONF) Charging	7.0.0	NA
5.2.2.1.11.0	Introduction	7.0.0	NA
5.2.2.1.11.1	CONF charging - user creating a conference	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.11.2	CONF charging - user joining a conference	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.11.3	CONF charging - user inviting another user to a conference	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.11.4	CONF charging - user leaving a conference	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.11.5	Three-Party (3PTY) charging - successful establishment	Non-compliant	Not supported.
5.2.2.1.11.6	Three-Party (3PTY) charging - release	Non-compliant	Not supported.
5.2.2.1.12	CCBS charging	Non-compliant	Not supported.
5.2.2.1.13	CCNR charging	Non-compliant	Not supported.
5.2.2.1.14	Flexible Alerting (FA)	Non-compliant	Not supported.
5.2.2.1.14.1	Flexible Alerting (FA) - establishment	Non-compliant	Not supported.
5.2.2.1.14.2	Flexible Alerting (FA) - call release	Non-compliant	Not supported.
5.2.2.1.15	Malicious Communication Identification (MCID)	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.16	Customized Alerting Tone (CAT)	Non-compliant	Not supported.
5.2.2.1.17	Closed User Group (CUG)	Non-compliant	Not supported.
5.2.2.1.18	Personal Network Management (PNM)	7.0.0	Possible, but not configured out-of-the-box
5.2.2.1.19	Customized Ringing Signal (CRS)	Non-compliant	Not supported.
5.2.2.1.20	Advice of Charge (AoC)	Non-compliant	Not supported.
5.2.3	GTP' record transfer flows	7.0.0	Noted
5.2.4	Bi CDR file transfer	7.0.0	Noted (not relevant to OCECAS)
5.3	MMTel online charging scenarios	7.0.0	NA
5.3.1	Basic principles	7.0.0	NA
5.3.2	Diameter message flows	7.0.0	NA
5.3.2.1	Message flows - Successful cases and scenarios	7.0.0	NA
5.3.2.1.0	Interaction with IMS-GWF	7.0.0	NA
5.3.2.1.1	Communications Diversion (CDIV)	7.0.0	NA
5.3.2.1.1.1	Communications Diversion (CDIV) - successful establishment	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.1.2	Communications Diversion (CDIV) - release	7.0.0	NA
5.3.2.1.2	Flexible Alerting (FA)	Non-compliant	Not supported.
5.3.2.1.3	Closed User Group (CUG)	Non-compliant	Not supported.
5.3.2.1.4	Conference (CONF)	7.0.0	NA
5.3.2.1.4.0	Introduction	7.0.0	NA
5.3.2.1.4.1	CONF - user creating a conference - ECUR mode	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.4.2	CONF - user creating a conference - SCUR mode	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.4.3	CONF - user joining a conference (SCUR mode)	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.4.4	CONF - using inviting another user to a conference (SCUR mode)	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.4.5	CONF - user leaving a conference (SCUR mode)	7.0.0	Possible, but not configured out-of-the-box
5.3.2.1.4.6	CONF (3PTY) - successful establishment	Non-compliant	Not supported.
5.3.2.1.5	Explicit Communication Transfer (ECT)	Non-compliant	Not supported.
5.3.2.2	Message flows - error cases and scenarios	7.0.0	See "3GPP_TS_32.260 Compliance" PICS
6	Definition of charging information	7.0.0	NA
6.1	Data description for MMTel offline charging	7.0.0	NA
6.1.1	Rf message contents	7.0.0	NA
6.1.1.0	Introduction	7.0.0	NA
6.1.1.1	Charging Data Request message description	7.0.0	See "3GPP_TS_32.299 Compliance" PICS
6.1.1.2	Charging Data Response message description	7.0.0	See "3GPP_TS_32.299 Compliance" PICS
6.1.2	GTP' message contents	7.0.0	NA
6.1.3	CDR description on the Bi interface	7.0.0	NA
6.1.3.1	CDR field type	7.0.0	NA
6.1.3.2	CDR triggers	7.0.0	NA
6.1.3.3	MMTel-AS CDR content	7.0.0	See "3GPP_TS_32.260 Compliance" PICS
6.2	Data description for MMTel online charging	7.0.0	NA
6.2.1	Ro message contents	7.0.0	NA
6.2.1.0	Introduction	7.0.0	NA
6.2.1.1	Debit / Reserve Units Request message	7.0.0	See "3GPP_TS_32.260 Compliance" PICS
6.2.1.2	Debit / Reserve Units Response message	7.0.0	See "3GPP_TS_32.260 Compliance" PICS
6.3	MMTel charging specific parameters	7.0.0	NA
6.3.1	Definition of MMTel charging information	7.0.0	NA
6.3.1.0	Introduction	7.0.0	NA
6.3.1.1	MMTel charging information assignment for Service Information	7.0.0	NA
6.3.1.2	Definition of the MMTel Information	7.0.0 (Partial)	See "3GPP_TS_32.299 Compliance" PICS for exact details of which parameters are supported.
6.3.1.3	Support of MMTel Information in MMTel offline charging	7.0.0	NA
6.3.1.4	Support of MMTel Information in MMTel online charging	7.0.0	NA

3GPP_TS_32.299 Compliance

Table 1-17 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the 3GPP specification 32.299 (v12.4.0), "Telecommunication management; Charging management; Diameter charging applications."

Table 1-17 3GPP_TS_32.299

Section Number	Section Title	Product Release	Release caveats
1	Scope	7.0.0	Noted
2	References	7.0.0	Noted
3	Definitions, symbols and abbreviations	7.0.0	Noted
4	Architecture Considerations	7.0.0	Noted
4.1	High level architecture	7.0.0	Noted
4.1.1	Charging related transfer requirements	7.0.0 (Partial)	Noted
5	3GPP charging applications requirements	7.0.0	Noted
5.1	Offline Charging Scenarios	7.0.0	NA
5.1.1	Basic Principles	7.0.0	NA
5.1.1.1	Event based charging	7.0.0	NA
5.1.1.2	Session based charging	7.0.0	NA
5.1.2	Basic Operation	7.0.0	Individual Service Information component compliance is considered in the appropriate AVP section.
5.2	Online Charging scenarios	7.0.0	NA
5.2.1	Basic principles	7.0.0	NA
5.2.2	Charging Scenarios	7.0.0	NA
5.2.2.1	Immediate Event Charging	7.0.0	NA
5.2.2.1.1	Decentralized Unit Determination and Centralized Rating	7.0.0	NA
5.2.2.1.2	Centralized Unit Determination and Centralized Rating	7.0.0	NA
5.2.2.1.3	Decentralized Unit Determination and Decentralized Rating	7.0.0	Monetary unit determination is limited to Control Flow Logic
5.2.2.1.4	Further Options	7.0.0	NA
5.2.2.2	Event Charging with Reservation	7.0.0	NA
5.2.2.2.1	Decentralized Unit Determination and Centralized Rating	7.0.0	Reserved Units Supervision is limited, depending on inbound interface
5.2.2.2.2	Centralized Unit Determination and Centralized Rating	7.0.0	Granted Units Supervision is limited, depending on inbound interface
5.2.2.2.3	Decentralized Unit Determination and Decentralized Rating	7.0.0	Budget Control is limited, depending on inbound interface
5.2.2.3	Session charging with Reservation	7.0.0	NA
5.2.2.3.1	Decentralized Unit Determination and Centralized Rating	7.0.0	NA
5.2.2.3.2	Centralized Unit Determination and Centralized Rating	7.0.0	NA
5.2.2.3.3	Decentralized Unit Determination and Decentralized Rating	7.0.0	Monetary unit determination is limited to Control Flow Logic
5.2.3	Basic Operations	7.0.0	NA
5.3	Other requirements	7.0.0	NA
5.3.1	Re-authorization	7.0.0	NA
5.3.2	Threshold based re-authorization triggers	7.0.0	NA
5.3.3	Termination action	7.0.0	NA
5.3.4	Account Expiration	7.0.0	NA
6	3GPP Charging Applications - Protocol Aspects	7.0.0	NA
6.1	Basic Principles for Diameter Offline Charging	7.0.0	NA
6.1.1	Event based charging	7.0.0	NA
6.1.2	Session based charging	7.0.0	NA
6.1.3	Offline charging error cases - Diameter procedures	7.0.0	NA
6.1.3.1	CDF connection failure	7.0.0	NA
6.1.3.2	No reply from CDF	7.0.0	NA
6.1.3.3	Duplicate detection	7.0.0	NA
6.1.3.4	CDF detected failure	7.0.0	NA
6.2	Message Contents for Offline Charging	7.0.0	NA
6.2.1	Summary of Offline Charging Message Formats	7.0.0	NA
6.2.1.1	General	7.0.0	NA
6.2.1.2	Structure for the Accounting Message Formats	7.0.0	NA
6.2.2	Accounting-Request Message	7.0.0	Individual AVP compliance covered in clause 7
6.2.3	Accounting-Answer Message	7.0.0	NA
6.3	Basic Principles for Diameter Online charging	7.0.0	NA
6.3.1	Online Specific Credit Control Application Requirements	7.0.0	NA
6.3.2	Diameter Description on the Ro reference point	7.0.0	NA
6.3.2.1	Basic Principles	7.0.0	NA
6.3.3	Immediate Event Charging	7.0.0	NA
6.3.4	Event Charging with Unit Reservation (ECUR)	7.0.0	NA
6.3.5	Session Charging with Unit Reservation (SCUR)	7.0.0	NA
6.3.6	Error Cases and Scenarios	7.0.0	NA
6.3.6.1	Duplicate Detection	7.0.0	NA
6.3.6.2	Reserve Units and Debit Units Operation Failure	7.0.0	The Direct-Debit-Failure-Handling AVP (RFC4006) is possible, but not defined in the default control flows. Credit-Control-Failure-Handling and CC-Session-Failover are obeyed. Failover is only to another configured peer in this realm.
6.3.7	Support of Tariff Changes during an Active User Session	7.0.0	NA
6.3.7.1	Support of Tariff Changes using the Tariff Switch Mechanism	7.0.0	NA
6.3.7.2	Support of Tariff Changes using Validity Time AVP	7.0.0	NA
6.3.8	Support of Re-authorisation	7.0.0	NA
6.3.9	Support of Failure Handling	7.0.0	NA
6.3.10	Support of Failover	7.0.0	Failover to other configured peers of the realm is supported. New sessions are only directed first to the failed-over OCS once connection to the failing OCS is closed.
6.3.11	Credit Pooling	Non-compliant	Not supported in 7.0.0
6.4	Message formats for Online Charging	7.0.0	NA
6.4.1	Summary of Online Charging Message Formats	7.0.0	NA
6.4.1.1	General	7.0.0	NA
6.4.1.2	Structure for the Credit Control Message Formats	7.0.0	NA
6.4.2	Credit-Control-Request Message	7.0.0	Individual AVP compliance covered in clause 7
6.4.3	Credit-Control-Answer Message	7.0.0	Individual AVP compliance covered in clause 7
6.4.4	Re-Auth-Request Message	7.0.0	(As per 6.3.11, G-S-U is ignored).
6.4.5	Re-Auth-Answer Message	7.0.0	NA
6.4.6	Capabilities-Exchange-Request Message	7.0.0	NA
6.4.7	Capabilities-Exchange-Answer Message	7.0.0	NA
6.4.8	Device-Watchdog-Request Message	7.0.0	NA
6.4.9	Device-Watchdog-Answer Message	7.0.0	NA
6.4.10	Disconnect-Peer-Request Message	7.0.0	NA
6.4.11	Disconnect-Peer-Answer Message	7.0.0	NA
6.4.12	Abort-Session-Request Message	7.0.0	NA
6.4.13	Abort-Session-Answer Message	7.0.0	NA
6.5	Other procedural description of the 3GPP charging applications	7.0.0	NA
6.5.1	Re-authorization	7.0.0	NA
6.5.1.1	Idle timeout	Non-compliant	Not applicable NA this is a traffic data concept (so not enforced by OCECAS)
6.5.1.2	Change of charging conditions	7.0.0 (Partial)	Only limited monitoring of trigger elements is possible, and none are configured by default.
6.5.1.3	Reporting quota usage	7.0.0	NA
6.5.1.4	Quota consumption	7.0.0	NA
6.5.2	Threshold based re-authorization triggers	7.0.0	NA
6.5.3	Termination action	7.0.0	NA
6.5.4	Quota consumption time	7.0.0 (Partial)	The Quota is reset with every update.
6.5.5	Service Termination	7.0.0	NA
6.5.6	Envelope reporting	Non-compliant	Not supported in 7.0.0
6.5.7	Combinational quota	Non-compliant	Not supported in 7.0.0
6.5.8	Online control of offline charging information	7.0.0	Not configured by default. This is possible, subject to the AVP restrictions listed in clause 7
6.5.9	Support of Multiple Service	7.0.0	NA
6.6	Bindings of the operation to protocol application	7.0.0	NA
6.6.1	Bindings of Charging Data Transfer to Accounting	7.0.0	NA
6.6.2	Bindings of Debit / Reserve Units to Credit-Control	7.0.0	NA
7	Summary of used Attribute Value Pairs	7.0.0	NA
7.1	Diameter AVPs	7.0.0 (Partial)	Compliance to all applicable AVPs are stated in individual 7.1.x sections.
7.1.1	Accounting-Input-Octets	7.0.0	Not needed for OCECAS use cases
7.1.2	void	7.0.0	NA
7.1.3	Accounting-Output-Octets	7.0.0	Not needed for OCECAS use cases
7.1.4	void	7.0.0	NA
7.1.5	Acct-Application-Id AVP	7.0.0	NA
7.1.6	Auth-Application-Id AVP	7.0.0	NA
7.1.7	Called-Station-Id	7.0.0	NA
7.1.8	Event-Timestamp AVP	7.0.0	NA
7.1.9	Multiple-Services-Credit-Control	7.0.0 (Partial)	MSCC is supported in 7.0.0. However not all AVPs inside the MSCC group are supported. See the individual 7.1.x sections for compliance.
7.1.10	Rating-Group AVP	7.0.0	NA
7.1.11	Result-Code AVP	7.0.0	NA
7.1.12	Service-Context-Id AVP	7.0.0	NA
7.1.13	Service-Identifier AVP	7.0.0	NA
7.1.14	Used-Service-Unit AVP	7.0.0	Note that Data charging is considered out of scope for OCECAS as the inbound interfaces do not collect octets used.
7.1.15	User-Name AVP	7.0.0	NA
7.1.16	Vendor-Id AVP	7.0.0	NA
7.1.17	User-Equipment-Info AVP	7.0.0	NA
7.2	3GPP specific AVPs	7.0.0 (Partial)	3GPP- named AVPs are not constructed by OCECAS, so can only be passed on if present in inbound messages. MMTel should not require these AVPs. Likewise, the following can only be passed on and not constructed: Access-Network-Charging-Identifier-Value AF-Charging-Identifier MBMS-Service-Area MBMS-Session-Identity MME-Number-for-MT-SMS TMGI User-Data User-Location-Info-Time
7.2.1	Access-Network-Information AVP	7.0.0	NA
7.2.1A	Access-Transfer-Information AVP	7.0.0	NA
7.2.1B	Access-Transfer-Type AVP	7.0.0	NA
7.2.2	Account-Expiration AVP	7.0.0	NA
7.2.3	Accumulated-Cost AVP	7.0.0	Note that Value and Exponent are kept as two separate fields by OCECAS
7.2.4	Adaptations AVP	7.0.0	Not needed for OCECAS use cases
7.2.5	Additional-Content-Information AVP	7.0.0	Not needed for OCECAS use cases
7.2.6	Additional-Type-Information AVP	7.0.0	Not needed for OCECAS use cases
7.2.7	Address-Data AVP	7.0.0	NA
7.2.8	Address-Domain AVP	7.0.0 (Partial)	The 3GPP-IMSI-MCC-MNC can only be passed on, not constructed by OCECAS.
7.2.9	Address-Type AVP	7.0.0	NA
7.2.10	Addressee-Type AVP	7.0.0	NA
7.2.11	AF-Correlation-Information AVP	7.0.0 (Partial)	The Flows and AF-Charging-Identifier can only be passed on, not constructed by OCECAS.
7.2.12	Alternate-Charged-Party-Address AVP	7.0.0	NA
7.2.13	AoC-Cost-Information AVP	7.0.0	Not configured by default.
7.2.14	AoC-Format AVP	7.0.0	Not configured by default.
7.2.15	AoC-Information AVP 101	7.0.0	Not configured by default.
7.2.16	AoC-Request-Type AVP	7.0.0	Not configured by default.
7.2.17	AoC-Service AVP	7.0.0	Not configured by default.
7.2.18	AoC-Service-Obligatory-Type AVP	7.0.0	Not configured by default.
7.2.19	AoC-Service-Type AVP	7.0.0	Not configured by default.
7.2.20	AoC-Subscription-Information AVP	7.0.0	Not configured by default.
7.2.21	Applic-ID AVP	7.0.0	Not needed for OCECAS use cases (it is MMS related)
7.2.22	Application-provided-Called-Party-Address AVP	7.0.0	NA
7.2.23	Application-Server AVP	7.0.0	NA
7.2.24	Application-Server-Information AVP	7.0.0	NA
7.2.25	Associated-Party-Address AVP	7.0.0	NA
7.2.26	Associated-URI AVP	7.0.0	NA
7.2.27	Authorised-QoS AVP	7.0.0	3GSPP 32.299 states that this AVP is not used.
7.2.28	Aux-Applic-Info AVP	7.0.0	Not needed for OCECAS use cases (it is MMS related)
7.2.29	Base-Time-Interval AVP	Non-compliant	Not supported in 7.0.0
7.2.30	Bearer-Service AVP	7.0.0	NA
7.2.31	Called-Asserted-Identity AVP	7.0.0	NA
7.2.32	Called-Party-Address AVP	7.0.0	NA
7.2.33	Calling-Party-Address AVP	7.0.0	NA
7.2.34	Carrier-Select-Routing-Information AVP	7.0.0	NA
7.2.35	Cause-Code AVP	7.0.0	NA
7.2.36	CG-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.37	Change-Condition AVP	7.0.0	NA
7.2.38	Change-Time AVP	7.0.0	NA
7.2.38A	Charge-Reason-Code AVP	7.0.0	NA
7.2.39	Charged-Party AVP	7.0.0	NA
7.2.39A	Charging-Characteristics-Selection-Mode AVP	7.0.0	NA
7.2.40	Class-Identifier AVP	7.0.0	NA
7.2.41	Client-Address	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.42	Content-Class AVP	7.0.0	NA
7.2.43	Content-Disposition AVP	7.0.0	NA
7.2.44	Content-Length AVP	7.0.0	NA
7.2.45	Content-Size AVP	7.0.0	Not needed for OCECAS use cases
7.2.46	Content-Type AVP	7.0.0	NA
7.2.46A	CSG-Access-Mode AVP	7.0.0	NA
7.2.46B	CSG-Membership-Indication AVP	7.0.0	NA
7.2.47	Current-Tariff AVP	7.0.0	NA
7.2.48	CUG-Information	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.49	Data-Coding-Scheme AVP	7.0.0	NA
7.2.50	DCD-Information AVP	7.0.0	NA
7.2.51	Deferred-Location-Event-Type AVP	7.0.0	Not needed for OCECAS use cases
7.2.52	Delivery-Report-Requested AVP	7.0.0	NA
7.2.53	Destination-Interface AVP	7.0.0	NA
7.2.54	Diagnostics AVP	7.0.0	NA
7.2.55	Domain-Name AVP	7.0.0	NA
7.2.56	DRM-Content AVP	7.0.0	Not needed for OCECAS use cases
7.2.57	Dynamic-Address-Flag AVP	7.0.0	NA
7.2.57A	Dynamic-Address-Flag-Extension AVP	7.0.0	NA
7.2.58	Early-Media-Description AVP	7.0.0 (Partial)	Only rudimentary access to the individual SDP lines is available.
7.2.59	Envelope AVP	Non-compliant	Not supported in 7.0.0
7.2.60	Envelope-End-Time AVP	Non-compliant	Not supported in 7.0.0
7.2.61	Envelope-Reporting AVP	Non-compliant	Not supported in 7.0.0
7.2.62	Envelope-Start-Time AVP	Non-compliant	Not supported in 7.0.0
7.2.63	Event AVP	7.0.0	NA
7.2.64	Event-Charging-TimeStamp AVP	7.0.0	NA
7.2.65	Event-Type AVP	7.0.0	NA
7.2.66	Expires AVP	7.0.0	NA
7.2.67	File-Repair-Supported AVP	7.0.0	NA
7.2.67A	From-Address AVP	7.0.0	NA
7.2.68	GGSN-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.69	IM-Information AVP	7.0.0	NA
7.2.70	Incremental-Cost AVP	7.0.0	Not needed for OCECAS use cases
7.2.70A	Instance-Id AVP	7.0.0	NA
7.2.71	Interface-Id AVP	7.0.0	NA
7.2.72	Interface-Port AVP	7.0.0	NA
7.2.73	Interface-Text AVP	7.0.0	NA
7.2.74	Interface-Type AVP	7.0.0	NA
7.2.74A	IMS-Application-Reference-Identifier AVP	7.0.0	NA
7.2.75	IMS-Charging-Identifier AVP	7.0.0	NA
7.2.76	IMS-Communication-Service-Identifier AVP	7.0.0	NA
7.2.76A	IMS-Emergency-Indicator AVP	7.0.0	NA
7.2.77	IMS-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.77A	IMS-Visited-Network-Identifier AVP	7.0.0	NA
7.2.78	IMSI-Unauthenticated-Flag AVP	7.0.0	NA
7.2.79	Incoming-Trunk-Group-ID AVP	7.0.0	NA
7.2.79A	Initial-IMS-Charging-Identifier AVP	7.0.0	NA
7.2.80	Inter-Operator-Identifier AVP	7.0.0	NA
7.2.80A	IP-Realm-Default-Indication AVP	7.0.0	NA
7.2.81	LCS-APN AVP	7.0.0	Not needed for OCECAS use cases
7.2.82	LCS-Client-Dialed-By-MS AVP	7.0.0	Not needed for OCECAS use cases
7.2.83	LCS-Client-External-ID AVP	7.0.0	Not needed for OCECAS use cases
7.2.84	LCS-Client-ID AVP	7.0.0	Not needed for OCECAS use cases
7.2.85	LCS-Client-Name AVP	7.0.0	Not needed for OCECAS use cases
7.2.86	LCS-Client-Type AVP	7.0.0	Not needed for OCECAS use cases
7.2.87	LCS-Data-Coding-Scheme AVP	7.0.0	Not needed for OCECAS use cases
7.2.88	LCS-Format-Indicator AVP	7.0.0	Not needed for OCECAS use cases
7.2.89	LCS-Information AVP	7.0.0	Not needed for OCECAS use cases
7.2.90	LCS-Name-String AVP	7.0.0	Not needed for OCECAS use cases
7.2.91	LCS-Requestor-ID AVP	7.0.0	Not needed for OCECAS use cases
7.2.92	LCS-Requestor-ID-String AVP	7.0.0	Not needed for OCECAS use cases
7.2.92A	Local-GW-Inserted-Indication AVP	7.0.0	NA
7.2.93	Local-Sequence-Number AVP	7.0.0	NA
7.2.94	Location-Estimate AVP	7.0.0	Not needed for OCECAS use cases
7.2.95	Location-Estimate-Type AVP	7.0.0	Not needed for OCECAS use cases
7.2.96	Location-Type AVP	7.0.0	Not needed for OCECAS use cases
7.2.97	Low-Balance-Indication AVP	7.0.0	NA
7.2.97A	Low-Priority-Indicator AVP	7.0.0	NA
7.2.98	MBMS-GW-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.99	MBMS-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.100	MBMS-User-Service-Type AVP	7.0.0	NA
7.2.101	Media-Initiator-Flag AVP	7.0.0	NA
7.2.102	Media-Initiator-Party AVP	7.0.0	NA
7.2.103	Message-Body AVP	7.0.0	NA
7.2.104	Message-Class AVP	7.0.0	NA
7.2.105	Message-ID AVP	7.0.0	NA
7.2.106	Message-Size AVP	7.0.0	NA
7.2.107	Message-Type AVP	7.0.0	NA
7.2.108	MM-Content-Type AVP	7.0.0	Not needed for OCECAS use cases
7.2.109	MMBox-Storage-Requested AVP	7.0.0	Not needed for OCECAS use cases
7.2.110	MMS-Information AVP	7.0.0	Not needed for OCECAS use cases
7.2.111	MMTel-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.111aA	MMTel-SService-Type AVP	7.0.0	NA
7.2.111bA	MTC-IWF-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.111A	Neighbor-Node-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.112	Next-Tariff AVP	7.0.0	NA
7.2.112A	NNI-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.112B	NNI-Type AVP	7.0.0	NA
7.2.113	Node-Functionality AVP	7.0.0	NA
7.2.114	Node-Id AVP	7.0.0	NA
7.2.115	Number-Of-Diversions AVP	7.0.0	NA
7.2.116	Number-Of-Messages-Sent AVP	7.0.0	NA
7.2.117	Number-Of-Participants AVP	7.0.0	NA
7.2.118	Number-Of-Received-Talk-Bursts AVP	7.0.0	NA
7.2.119	Number-Of-Talk-Bursts AVP	7.0.0	NA
7.2.120	Number-Portability-Routing-Information AVP	7.0.0	NA
7.2.121	Offline-Charging AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.122	Online-Charging-Flag AVP	7.0.0	NA
7.2.123	Originating-IOI AVP	7.0.0	NA
7.2.124	Originator AVP	7.0.0	NA
7.2.125	OriginatorNAAddress AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.126	Originator-Interface AVP	7.0.0	NA
7.2.127	Originator-Received-Address AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.128	Originator-SCCP-Address	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.128A	Outgoing-Session-Id AVP	7.0.0	NA
7.2.129	Outgoing-Trunk-Group-ID AVP	7.0.0	NA
7.2.130	Participants-Involved AVP	7.0.0	NA
7.2.131	Participant-Group AVP	7.0.0	NA
7.2.132	Participant-Access-Priority AVP	7.0.0	NA
7.2.133	Participant-Action-Type AVP	7.0.0	NA
7.2.134	PDG-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.135	PDG-Charging-Id AVP	7.0.0	NA
7.2.136	PDN-Connection-Charging-ID AVP	7.0.0	NA
7.2.137	PDP-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.137a	PDP-Address-Prefix-Length AVP	7.0.0	NA
7.2.138	PDP-Context-Type AVP	7.0.0	NA
7.2.139	PoC-Change-Condition AVP	7.0.0	NA
7.2.140	PoC-Change-Time AVP	7.0.0	NA
7.2.141	PoC-Controlling-Address AVP	7.0.0	NA
7.2.142	PoC-Event-Type AVP	7.0.0	NA
7.2.143	PoC-Group-Name AVP	7.0.0	NA
7.2.144	PoC-Information AVP	7.0.0	NA
7.2.145	PoC-Server-Role AVP	7.0.0	NA
7.2.146	PoC-Session-Id AVP	7.0.0	NA
7.2.147	PoC-Session-Initiation-Type AVP	7.0.0	NA
7.2.148	PoC-Session-Type AVP	7.0.0	NA
7.2.149	PoC-User-Role AVP	7.0.0	NA
7.2.150	PoC-User-Role-IDs AVP	7.0.0	NA
7.2.151	PoC-User-Role-info-Units AVP	7.0.0	NA
7.2.152	Positioning-Data AVP	7.0.0	Not needed for OCECAS use cases
7.2.153	Preferred-AoC-Currency AVP	7.0.0	Not needed for OCECAS use cases
7.2.154	Priority AVP	7.0.0	Not needed for OCECAS use cases
7.2.155	PS-Append-Free-Format-Data AVP	7.0.0	NA
7.2.156	PS-Free-Format-Data AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.157	PS-Furnish-Charging-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.158	PS-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.159	Quota-Consumption-Time AVP	7.0.0 (Partial)	The Quota is reset with every update.
7.2.160	Quota-Holding-Time AVP	Non-compliant	OCECAS is not aware of idle traffic, so can't enforce this
7.2.161	Rate-Element AVP	7.0.0	NA
7.2.162	Read-Reply-Report-Requested AVP	7.0.0	Not needed for OCECAS use cases
7.2.163	Void	7.0.0	NA
7.2.164	Real-Time-Tariff-Information AVP	7.0.0	NA
7.2.164A	Reason-Header AVP	7.0.0	NA
7.2.165	Received-Talk-Burst-Time AVP	7.0.0	NA
7.2.166	Received-Talk-Burst-Volume AVP	7.0.0	NA
7.2.167	Recipient-Address AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.168	Recipient-Info AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.169	Recipient-Received-Address AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.170	Recipient-SCCP-Address	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.171	Refund-Information AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.171A	Relationship-Mode AVP	7.0.0	NA
7.2.171B	Related-IMS-Charging-Identifier AVP	7.0.0	NA
7.2.171C	Related-IMS-Charging-Identifier-Node AVP	7.0.0	NA
7.2.172	Remaining-Balance AVP	7.0.0	Not needed for OCECAS use cases
7.2.173	Reply-Applic-ID AVP	7.0.0	Not needed for OCECAS use cases
7.2.174	Reply-Path-Requested AVP	7.0.0	NA
7.2.175	Reporting-Reason AVP	7.0.0	NA
7.2.176	Requested-Party-Address AVP	7.0.0	NA
7.2.177	Role-Of-Node AVP	7.0.0	NA
7.2.177A	Route-Header-Received AVP	7.0.0	NA
7.2.177B	Route-Header-Transmitted AVP	7.0.0	NA
7.2.178	Scale-Factor AVP	7.0.0	Not needed for OCECAS use cases
7.2.179	SDP-Answer-Timestamp AVP	7.0.0	Not configured by default. Requires extraction of the t= line, splitting and storing as an integer. (Both this and diameter use seconds since 1900)
7.2.180	SDP-Media-Component AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.181	SDP-Media-Description AVP	7.0.0 (Partial)	all attribute lines from the SDP layer are available, but determining which a= belongs to which m= may be difficult.
7.2.182	SDP-Media-Name AVP	7.0.0	Not configured by default.
7.2.183	SDP-Offer-Timestamp AVP	7.0.0	Not configured by default. Requires extraction of the t= line, splitting and storing as an integer. (Both this and diameter use seconds since 1900)
7.2.184	SDP-Session-Description AVP	7.0.0 (Partial)	All attribute lines from the SDP layer are available, but determining which a= belongs to which m= may be difficult.
7.2.185	SDP-TimeStamps AVP	7.0.0	Not configured by default. Requires extraction of the t= line, splitting and storing as an integer. (Both this and diameter use seconds since 1900)
7.2.186	SDP-Type AVP	7.0.0	Not configured by default.
7.2.186A	Session-Direction AVP	7.0.0	NA
7.2.187	Served-Party-IP-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.188	Void	7.0.0	NA
7.2.189	Service-Data-Container AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.190	Service-ID AVP	7.0.0	NA
7.2.191	Service-Generic-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.192	Service-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.193	Service-Mode AVP	7.0.0	NA
7.2.194	Service-Specific-Data AVP	7.0.0	NA
7.2.195	Service-Specific-Info AVP	7.0.0	NA
7.2.196	Service-Specific-Type AVP	7.0.0	NA
7.2.197	Void	7.0.0	NA
7.2.198	Serving-Node-Type AVP	7.0.0	NA
7.2.199	SGSN-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.199A	SGW-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.200	SGW-Change AVP	7.0.0	NA
7.2.201	SIP-Method AVP	7.0.0	NA
7.2.202	SIP-Request-Timestamp AVP	7.0.0	NA
7.2.203	SIP-Request-Timestamp-Fraction AVP	7.0.0	NA
7.2.204	SIP-Response-Timestamp AVP	7.0.0	NA
7.2.205	SIP-Response-Timestamp-Fraction AVP	7.0.0	NA
7.2.205A	SM-Device-Trigger-Indicator AVP	7.0.0	NA
7.2.205B	SM-Device-Trigger-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.206	SM-Discharge-Time AVP	7.0.0	NA
7.2.207	SM-Message-Type AVP	7.0.0	NA
7.2.208	SM-Protocol-Id AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.208A	SM-Sequence-Number AVP	7.0.0	NA
7.2.209	SM-Status AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.210	SM-User-Data-Header AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.211	SMS-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.212	SMS-Node AVP	7.0.0	NA
7.2.212A	SMS-Result AVP	7.0.0	NA
7.2.213	SM-Service-Type AVP	7.0.0	NA
7.2.214	SMSC-Address AVP	7.0.0 (Partial)	Can only be passed on, not constructed by OCECAS.
7.2.215	Start-Time AVP	7.0.0	NA
7.2.215A	Status-Code AVP	7.0.0	NA
7.2.216	Stop-Time AVP	7.0.0	NA
7.2.217	Submission-Time AVP	7.0.0	NA
7.2.218	Subscriber-Role AVP	7.0.0	NA
7.2.219	Supplementary-Service AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.220	Talk-Burst-Exchange AVP	7.0.0	NA
7.2.221	Talk-Burst-Time AVP	7.0.0	NA
7.2.222	Talk-Burst-Volume AVP	7.0.0	NA
7.2.223	Tariff-Information AVP	7.0.0	NA
7.2.224	Tariff-XML AVP	7.0.0	NA
7.2.225	Terminating-IOI AVP	7.0.0	NA
7.2.226	Time-First-Usage AVP	7.0.0	NA
7.2.227	Time-Last-Usage AVP	7.0.0	NA
7.2.228	Time-Quota-Mechanism	Non-compliant	Not supported in 7.0.0
7.2.229	Time-Quota-Threshold AVP	7.0.0	NA
7.2.230	Time-Quota-Type AVP	Non-compliant	Not supported in 7.0.0
7.2.231	Time-Stamps AVP	7.0.0	NA
7.2.232	Time-Usage AVP	7.0.0	NA
7.2.233	Traffic-Data-Volumes AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.233A	Transcoder-Inserted-Indication AVP	7.0.0	NA
7.2.233B	Transit-IOI-List AVP	7.0.0	NA
7.2.234	Token-Text AVP	7.0.0	Not needed for OCECAS use cases
7.2.235	Trigger AVP	7.0.0 (Partial)	Limited to capabilities of Control Flow Logic. Not configured by default.
7.2.236	Trigger-Type AVP	7.0.0	Limited to capabilities of Control Flow Logic. Not configured by default.
7.2.237	Trunk-Group-ID AVP	7.0.0	NA
7.2.237A	TWAN-BSSID AVP	7.0.0	NA
7.2.237B	TWAN-SSID AVP	7.0.0	NA
7.2.237C	TWAN-User-Location-Info AVP	7.0.0	NA
7.2.238	Type-Number AVP	7.0.0	NA
7.2.239	Unit-Cost AVP	7.0.0	Not needed for OCECAS use cases
7.2.240	Unit-Quota-Threshold AVP	7.0.0	Not needed for OCECAS use cases
7.2.240A	User-CSG-Information AVP	7.0.0	NA
7.2.241	User-Participating-Type AVP	7.0.0	NA
7.2.242	User-Session-Id AVP	7.0.0	NA
7.2.243	Volume-Quota-Threshold AVP	7.0.0	Not needed for OCECAS use cases
7.2.244	WAG-Address AVP	7.0.0 (Partial)	Can only be passed on; not constructed by OCECAS.
7.2.245	WAG-PLMN-Id AVP	7.0.0 (Partial)	Can only be passed on; not constructed by OCECAS.
7.2.246	WLAN-Information AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.247	WLAN-Radio-Container AVP	7.0.0 (Partial)	Compliant where contained AVPs are compliant
7.2.248	WLAN-Session-Id AVP	7.0.0	NA
7.2.249	WLAN-Technology AVP	7.0.0	NA
7.2.250	WLAN-UE-Local-IPAddress AVP	7.0.0 (Partial)	Can only be passed on; not constructed by OCECAS.
7.3	3GPP2 Accesses specific AVPs	7.0.0 (Partial)	Can only be passed on; not constructed by OCECAS.