Originating Identification Presentation

In Release 15, the specifications for the Originating Identification Presentation (OIP) function were updated to clarify its behavior in conjunction with enhanced Calling Name (eCNAM) and across various call forwarding and deflection scenarios. The release explicitly defined that for users subscribed to both OIP and eCNAM, the originating party's identity and eCNAM data must be delivered together, with the terminating provider extracting the telephone number from the OIP information to retrieve the eCNAM data. Furthermore, it was specified that the original originating party's identity must be presented to a forwarded or deflected-to party provided with the OIP service, unless the originating party has invoked Originating Identification Restriction (OIR).

• Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.608CR0029
• Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.616CR0026
• Interwork of Connected subaddress IE carried in ISUP CON message TS 29.163CR1026
• Reference Update for the ISUP location parameter TS 29.163CR1018
• Reference Update for the ISUP location parameter TS 29.163CR1020
• Reference Update for the ISUP location parameter TS 29.163CR1023

+ 14 more changes

In Release 16, the OIP function was enhanced to ensure the original calling party's identity is correctly presented across various forwarding and deflection scenarios, such as CFU, CFB, and CD, when the originating party has not invoked restriction. Furthermore, specifications were updated to define the mapping of the History-Info header field to the ISUP Original Called Number parameter for improved interworking with legacy networks.

• Reference Update for the ISUP Cause Location Parameter Draft TS 29.163CR1057
• Reference Update for the ISUP Cause Location Parameter Draft TS 29.163CR1061
• Mapping of History-Info header field to ISUP Original called number TS 29.163CR1069

In Release 17, the key new feature for the Originating Identification Presentation (OIP) function was the introduction of configuration support for Standalone Non-Public Networks (SNPN). This enhancement ensures that the OIP service, which provides the terminating party with the identity of the originating party, can be properly configured and operated within SNPN deployments. The update addresses the specific requirements for presenting the originating party's identity in these isolated network environments.

• SNPN configuration for OIP/OIR TS 24.417CR0002

In Release 18, a new procedure was introduced for the Originating IMS Application Server upon receiving a BDC establishment request, specifically enhancing the OIP (Originating Identification Presentation) function. This addition provides a defined mechanism for handling the initial request that triggers caller identity delivery. The update ensures the OIP service can operate in conjunction with underlying network analytics and forwarding services as described in the existing framework.

• Procedure of originating IMS AS on receiving the BDC establishment request TS 24.186CR0018

In Release 19, the enhancement for the Originating Identification Presentation (OIP) function introduced a new procedure for application data channel interworking via a DC AS for the originating UE. This addition specifically defines how the originating user equipment can interact through a Data Channel Application Server to support the OIP service.

• Procedure of application data channel interworking via DC AS for originating UE TS 24.186CR0065