Content for TS 29.175 Word version: 19.3.0

1…

3.1 Definitions 3.2 Symbols 3.3 Abbreviations

1 Scope p. 16

The present document specifies the stage 3 protocol and data model for the Nimsas Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the IMS AS.

The 5G System stage 2 architecture and procedures are specified in TS 23.501 and TS 23.502.

The IP Multimedia Subsystem (IMS) supporting DC architecture and procedures are specified in TS 23.228.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 and TS 29.501.

2 References p. 16

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 23.501: "System Architecture for the 5G System; Stage 2".

[3]

TS 23.502: "Procedures for the 5G System; Stage 2".

[4]

TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".

[5]

TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".

[6]

OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.

[7]

TR 21.900: "Technical Specification Group working methods".

[8]

TS 33.501: "Security architecture and procedures for 5G system".

[9]

RFC 6749: "The OAuth 2.0 Authorization Framework".

[10]

TS 29.510: "5G System; Network Function Repository Services; Stage 3".

[11]

RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".

[12]

RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".

[13]

RFC 7807: "Problem Details for HTTP APIs".

[14]

TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[15]

TS 29.562: "5G System; Home Subscriber Server (HSS) Services; Stage 3".

[16]

TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".

[17]

TS 29.176: "IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3".

[18]

TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[19]

TS 24.186: "IMS Data Channel applications; Protocol specification".

[20]

RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".

[21]

TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM); Core Network (CN) subsystem; Protocol specification".

3 Definitions, symbols and abbreviations p. 17

3.1 Definitions p. 17

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

For the purposes of the present document, the following terms and definitions given in TS 23.228 apply:

Bootstrap data channel
DC Application Server
Rich Call Data (RCD) server
Rich Call Data (RCD) server address
Rich Call Data (RCD) information
Rich Call Data (RCD) URL
Rich Call Data (RCD) properties

3.2 Symbols p. 17

For the purposes of the present document, the following symbols given in TS 23.228 apply:

DC1

Reference Point between an SBI capable IMS AS and DCSF.

DC2

Reference Point between an SBI capable IMS AS and MF.

3.3 Abbreviations p. 17

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

Augmented Reality

Data Channel

DCSF

Data Channel Signalling Function

HSS

Home Subscriber Server

Media Function

NEF

Network Exposure Function

RCD

Rich Call Data

4 Overview p. 17

The IP Multimedia Subsystem (IMS) architecture supporting the Data Channel services is defined in TS 23.228.

The IP Multimedia Subsystem (IMS) Application Server (AS) is enhanced to offer services to e.g. DCSF, HSS, NEF or trusted AF via the Nimsas service-based interface (see TS 23.228) and support the following functionalities:

The IMS AS interacts with the DCSF via DC1 for event notifications;
The IMS AS receives the data channel control instructions from the DCSF and accordingly interacts with the MF via DC2 for data channel media resource management;
The IMS AS receives the data channel management requirement from NEF or trusted AF and interacts with the DCSF and MF for data channel management.
The IMS AS interacts with the HSS/NEF for subscriber related events subscription, and notifies the NEF with the subscriber related events which are subscribed, and interacts with the NEF for non-subscriber related events subscription and notification, e.g. subscriptions to any UE;
The IMS AS receives the provisioning information (e.g. RCD properties) from NEF or trusted AF and stores in HSS repository data to support the 3rd party user identity.

Figure 4-1 provides the reference model (in service-based interface representation and in reference point representation), with focus on the IMS AS.

Copy of original 3GPP image for 3GPP TS 29.175, Fig. 4-1: Reference model - IMS AS

Figure 4-1: Reference model - IMS AS
(⇒ copy of original 3GPP image)

DC1 is the reference point between an SBI capable IMS AS and DCSF.

N92 is the reference point between an SBI capable IMS AS and NEF.

N71 is the reference point between an SBI capable IMS AS and HSS.