Content for TR 23.700-77 Word version: 19.0.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 Architectural Assumptions and Principles
...
...
1 Scope p. 11
This technical report studies further enhancements to the IMS network architecture, interfaces and procedures to support the next generation real time communication services requirements on the following aspects:
-
Study on the enhancements to framework for exposure of IMS capability in the context of IMS data channel session, including:
- enhancing the IMS architecture to define an event subscription mechanism to enable subscription to various IMS events of IMS data channel services;
- how to enhance NF services of IMS and 5GC to expose existing IMS services (e.g. IMS voice/video call, message) in the context of an IMS data channel session, i.e. when DC is established.
- Study how to provide IMS data channel applications to the subscriber who is using a MTSI UE where it is appropriate depending on the applications.
- Study how IMS architecture and procedures are enhanced to support verified OIP service for 3rd party in IMS session using SA WG3 work on third party identity authentication as basis.
-
Study on the enhancements to IMS data channel related services and operational aspects, including:
- whether and how to support standalone IMS data channel without accompanying audio/video/messaging media in an IMS session;
- how to support 3GPP PS Data Off for IMS data channel and applications over IMS data channel;
- study enhancements of IMS DC architecture and procedure to support multiplexing a SCTP connection for multiple DC applications.
- Study whether and how to enhance IMS architecture, procedures, interfaces for supporting avatar call (including multi-party communication) and communication with accessibility as specified in clause 5.2.2 of TS 22.156.
2 References p. 11
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]
[19]
[20]
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 23.503: "Policy and Charging Control Framework for the 5G System".
[5]
TS 23.228: "IP Multimedia Subsystem (IMS)".
[6]
TS 26.114: "Media handling and interaction".
[7]
TS 22.261: "Service requirements for the 5G system".
[8]
[9]
TS 22.156: "Mobile Metaverse Services".
[10]
TS 24.229: "IP Multimedia Call Control based on SIP and SDP; Stage 3".
[11]
TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem".
[12]
TS 29.175: "IP Multimedia Subsystem; IP Multimedia Subsystem (IMS) Application Server (AS) Services Stage 3 (Release 18)".
[13]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[14]
RFC 3725: "Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)".
[15]
TS 24.341: "Support of SMS over IP networks".
[16]
TR 22.873: "Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service".
[17]
ATIS-1000074: "Signature-based Handling of Asserted information using Tokens (SHAKEN)".
[18]
draft-ietf-stir-passport-rcd-26: "PASSporT Extension for Rich Call Data".
draft-ietf-sipcore-callinfo-rcd-08: "SIP Call-Info Parameters for Rich Call Data".
RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
[21]
TR 22.856: "Feasibility Study on Localized Mobile Metaverse Services".
[22]
TS 22.011: "Service accessibility".
3 Definitions of terms and abbreviations p. 12
3.1 Terms p. 12
For the purposes of the present document, the terms given in TR 21.905, in TS 23.501 , in TS 23.228 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, in TS 23.501 or in TS 23.228.
Animated Avatar:
Rendered Avatar representation by performing animation based on the user physical data (e.g. facial expression, body movement information) during the Avatar communication.
Automatic Speech Recognition:
Automatic Speech Recognition, also known as ASR, is the use of Machine Learning (ML) or Artificial Intelligence (AI) technology to process human speech into readable text.
Avatar representation:
The digital representation associated with a user in Avatar communication.
Data channel multiplexing:
When multiple data channels are used in an IMS session, the UE and IMS network support transporting streams of multiple data channels in the same SCTP connection.
Data channel de-multiplexing:
When the streams of different data channels multiplexed in the same SCTP connection have different remote endpoints, e.g. two streams for different application in the UE, or one application data channel to the UE and one application data channel to the DC application server, the UE and IMS network terminates the multiplexing of these streams and forks different streams to corresponding remote endpoints.
IMS Avatar Communication:
The communication between two or more users using Avatar representation associated with the user based on IMS architecture.
Gesture:
A change in the pose that is considered significant, i.e. as a discriminated interaction with a mobile metaverse service.
Sign Language Recognition:
Sign Language Recognition is a computer vision and natural language processing task that involves automatically recognizing and translating sign language gestures into written or spoken language.
Speech to Sign Language:
Speech to Sign Language is to translate spoken speech into video sign language.
3.2 Abbreviations p. 13
For the purposes of the present document, the abbreviations given in TR 21.905, in TS 23.501 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 or in TS 23.501.
3PCC
3rd Party Call Control
API
Application Programming Interface
ASR
Automatic Speech Recognition
BAR
Base Avatar Repository
CAPIF
Common API Framework
DAC
Digital Asset Container
DC
Data Channel
DCSF
Data Channel Signalling Function
IMS
IP Multimedia Subsystem
IMSEF
IMS Exposure Function
MF
Media Function
NEF
Network Exposure Function
NF
Network Function
OIP
Originating Identification Presentation
OMA
Open Mobile Alliance
SLR
Sign Language Recognition
SSL
Speech to Sign Language
TTS
Text To Speech
UUID
Universally Unique Identifier
4 Architectural Assumptions and Principles p. 13
The following architectural assumptions and principles shall be considered during the study:
- IMS reference architecture defined in TS 23.228 is used as basis architecture.
- Solutions should have minimal impact to IMS architecture and procedures.
- IMS enhancements to support media handling of avatar calls should consider alignment with SA WG4 and should take SA WG4 output in TR 26.813 [8] as a baseline.
- For exposure of IMS capability, existing OMA specifications should be considered.
