hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17 Solution #17: Solution for support of IMS avatar communication using data channel | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.1 Description | Figure 6.17.1-1: Architecture to support IMS avatar communication
To support of IMS avatar communication, the architecture is enhanced as follows:
Digital Asset Container (DAC):
- The Digital Asset Container is used for storing and retrieving the avatar model from 5GC. DAC can be internal to the PLMN, e.g. a new networ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.2 Procedures | Supporting IMS avatar communication including providing avatar or a reference to one or several avatars in the IMS signalling, downloading and negotiating the avatar with B-party. In the proposed solutions of this document, avatar can be transferred via data channel, and rendering of avatar media can be performed by ne... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.2.1 Network centric IMS avatar call flow using data channel | Based on Figure AC.9.3.2-1 in clause AC.9.3.2 of TS 23.228 [5], Figure 6.17.2.1-1 depicts a call flow to establish a network centric IMS avatar call with rendering in the network. UE-A avatar media are transmitted to UE-B via MF/MRF.
Figure 6.17.2.1-1: Establishment of network centric IMS avatar call using data channel... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.2.2 UE-A centric IMS avatar call flow using data channel | Based on Figure AC.9.3.1-1 in clause AC.9.3.1 of TS 23.228 [5], Figure 6.17.2.2-1 depicts a call flow procedure to establish a UE centric IMS avatar call with rendering in the UE-A.
Figure 6.17.2.2-1: Establishment of UE-A centric IMS avatar call using data channel
The main steps in the call flow are as follows:
1. The... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.2.3 UE-B centric IMS avatar call flow using data channel | Based on Figure AC.9.3.1-1 in clause AC.9.3.1 of TS 23.228 [5], Figure 6.17.2.3-1 depicts a call flow procedure to establish a UE centric IMS avatar call with rendering in the UE-B.
Figure 6.17.2.3-1: Establishment of UE-B centric IMS avatar call using data channel
The main steps in the call flow are as follows:
1. The... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.17.3 Impacts on existing nodes and functionality | Impacted nodes and functionality are listed as follows:
- DAC: stores avatar model, names, and further data, based on avatar ID.
- XR Application Server: retrieves avatar model from DAC based on avatar ID and user identity, triggers MF/MRF rendering/transcoding.
- IMS AS: supports avatar call, provide avatar ID to XR A... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18 Solution #18: Supporting of network initiated IMS Data Channels | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.1 Description | The use case of network initiated IMS data channel is identified by GSMA NG UPG, and highlighted to 3GPP for supporting. Following clarification is contained in the LS to SA WG2 (S2-2400034):
GSMA NG UPG#08 has identified the use case when network-initiated IMS Data Channel mid-call setup is required.
In some cases, e.... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.2.1 Network initiated IMS DC establishment | Figure 6.18.2 -1 depicts IMS DC establishment procedures requested by a DC AS, including the establishment of both bootstrap data channel and application data channel.
In this procedure, UE-A represents the customer of an enterprise. UE-B represents service representative or automatic IVR in the enterprise network. DC ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.2.2 Additional Services and Operations | NOTE: The additional servicers and operations for generic IMS session event subscription and notification may refer to the solutions against KI#1, e.g. clause 6.1.2.3. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.2.2.1 Enhancements to Nimsas Services | Service provided by IMS AS are enhanced to enable NF consumers e.g. NEF to request IMS AS to create/update/delete data channels within an existing IMS session. To that effect, a new service is introduced for IMS DC control as depicted below.
Table 6.18.2.2.1-1
Service
Service Operations
Operation Semantics
Example Cons... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.2.2.2 Enhancements to Nnef Services | A new service is introduced for NF consumers (e.g. DC AS) to request NEF for creation/updating/deletion one or more IMS data channels within an existing IMS Session control as depicted below:
Table 6.18.2.2.2-1
Service
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_imsDCControl (Ims_DCC)
Create
Request... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.18.3 Impacts on existing services, entities and interfaces | NEF impacts:
- Receive data channel request from AFs for establishment, update or release of bootstrap data channel and application data channel.
- Send data channel request to IMS AS.
- Receive notifications of requested IMS events from the IMS AS.
- Send notifications of requested IMS events to the AF.
IMS AS impacts... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.19 Solution #19: Standalone IMS Data Channel decoupled from Multimedia Telephony | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.19.1 Description | This clause provides a solution for Key Issue #6 on Support of Standalone IMS Data Channel.
The solution uses the functional entities supporting the IMS data channel as specified in TS 23.228 [5] as the basis and decouples the data channel from the MMTel session.
Main principles of this solution are:
- The standalone I... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.19.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.19.2.1 Establishment of an IMS session with standalone P2P Application Data Channel | Figure 6.19.2.1-1 depicts a signalling flow for establishing a standalone application data channel in a person-to-person use case. In this scenario, the MF is not used to anchor the application data channel.
In the call flow, it is assumed that the UEs have already established a bootstrap data channel, for example duri... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.19.3 Impacts on existing nodes and functionality | Impacted nodes and functionality are listed as follows:
- UE: support standalone IMS data channel and SIP session timer according to RFC 4028 [20].
- IMS AS: support standalone IMS data channel and SIP session timer according to RFC 4028 [20].
- DCSF: support standalone IMS data channel (standalone bootstrap DC, standa... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20 Solution #20: Support Standalone Bootstrap Data Channel and Standalone Application Data Channel without Subscription and Media Negotiation. | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1 Description | This solution addresses the Key Issue#6 "Support of Standalone IMS Data Channel Sessions".
This solution proposes that no additional subscription or negotiation procedure is needed to support standalone data channel. If any party along the media negotiation does not support standalone data channel, e.g. originating net... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.1 Subscription of Standalone Data Channel | In Rel-18, TS 23.228 [5] has defined the subscription mechanism of IMS Data Channel. The use of standalone IMS Data Channel shall be included as a part of the IMS Data Channel subscription information. No additional subscription information is needed for standalone DC. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.2 Standalone Data Channel Capability Negotiation | It is proposed that the standalone data channel does not need extra capability negotiation. When receiving an SDP offer with standalone data channel, the network or UE that does not support standalone data channel shall return SIP 400 Bad Request response to inform the offerer that it does not recognize the syntax of t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.3 Support of Standalone Bootstrap Data Channel | The standalone bootstrap data channel could be used to extract DC application menu, subscriber specific graphical user interface or specific application.
In order to establish standalone bootstrap data channel, the request-URI can be set as the PSI of the DCSF. The UE may be configured of the PSI of the DCSF by the HPL... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.4 Support of Standalone Application Data Channel | The standalone application data channel shall support P2P, P2A/A2P and P2A2P application data channel.
In the P2A/A2P scenario, the request-URI is set as the PSI of the DCSF. DCSF should route the application data channel to the correct DC AS based on the binding information of a DC application.
Standalone application ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.5 Adding Audio/Video/Messaging Media to Established Standalone Data Channel | Only the standalone data channel session that between two UEs, i.e. the request-URI is the UE, could be updated to add audio/video/messaging media through a SIP re-INVITE message.
The standalone data channel session that only contains standalone bootstrap data channel and/or standalone P2A/A2P application data channel,... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.1.6 Removing Audio/Video/Messaging Media from an IMS Session that Contains IMS Data Channel Media | Only IMS session that between two UEs, i.e. the request-URI is the UE, could be updated to remove audio/video/messaging media through a SIP re-INVITE message.
The IMS session that only contains bootstrap data channel and/or standalone P2A/A2P application data channel, i.e. the request-URI is the PSI of the DCSF, shall ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.2 Procedures | Editor's note: The procedure of upgrading a standalone data channel to a MMTel session and downgrading a MMTel session to a standalone data channel is FFS. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.2.1 Standalone Application Data Channel Establishment when Both Ends have Version Compatible DC App | Figure 6.20.2.1-1
1. UE-A starts the standalone application data channel by sending a SIP INVITE/re-INVITE message. The message shall contain the binding information and version control information of the data channel application.
2. The IMS AS notifies the DCSF when receive the SIP INVITE/re-INVITE message, in the not... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.2.2 Standalone Application Data Channel Establishment when Originating UE does not have Version Compatible DC App | Figure 6.20.2.2-1
1. UE-A starts the standalone application data channel by sending a SIP INVITE/re-INVITE message. The message shall contain the binding information and version control information of the data channel application.
2. The IMS AS notifies the DCSF when receive the SIP INVITE/re-INVITE message, in the not... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.2.3 Standalone Application Data Channel Establishment when Terminating UE does not have Version Compatible DC App | Figure 6.20.2.3-1
1. UE-A starts the standalone application data channel by sending a SIP INVITE/re-INVITE message. The message shall contain the binding information and version control information of the data channel application.
2. The IMS AS notifies the DCSF when receive the SIP INVITE/re-INVITE message, in the not... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.20.3 Impacts on Existing Nodes and Functionality | The impacts on the DCSF:
- Support to establish standalone data channel
- Support to compare the version control information send by UE and instruct the IMS AS accordingly.
The impacts on the IMS AS:
- Support to notify DCSF when receive SIP message that only contains IMS data channel media description.
- Support to up... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.21 Solution #21: Standalone DC setup with backward compatibility | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.21.1 Description | In this solution, it is assumed that both the UE and the network should have the capability to support standalone data channel session management, not only the capability to support IMS DC session management. The network which supports standalone data channel session management checks whether the UE has the subscriptio... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.21.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.21.2.1 Establishment of a standalone data channel session | The Figure 6.21.2.1-1 illustrates the procedure of establishment of a standalone data channel session. The bootstrap data channel and application data channel set up procedures specified in clause AC.7 of TS 23.228 [5] applies with the following differences:
- Based on the UE capability and subscription of supporting s... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.21.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to exiting entities and interfaces:
UE:
- Initiates IMS DC session with a SDP offer with request only for IMS data channels without simultaneous media request for audio/video/messaging.
S-CSCF:
- Validates whether the network and the UE supports standalone IMS DC sessions, a... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22 Solution #22: Multiplexing multiple DC streams over single SCTP connection | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.1 General | This solution addresses Key Issue #7 Support multiplexing multiple DC applications over single SCTP connection.
The solution supports the following scenarios:
- Multiplexing a SDP media description by local bootstrap data channel and remote bootstrap data channel during IMS session setup;
- Multiplexing a SDP media des... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.2 Example scenarios for multiplexing and de-multiplexing | There are different scenarios for multiplexing and de-multiplexing due to different capabilities of UE and IMS network or the different types of data channels with different remote endpoints. This clause provides some example scenarios of multiplexing and de-multiplexing to demonstrate where and how the data for differ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.3 Capability negotiation | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.3.1 Capability negotiation between UE and network | It is needed to negotiate the capability of supporting data channel multiplexing between UE and network and between originating and terminating network, in order to decide where and how to multiplex and de-multiplex as demonstrated in clause 6.22.1.2.
The UE and the IMS network mutually negotiate their capability of da... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.3.2 Capability negotiation between originating and terminating network | The originating and terminating IMS network also need to negotiate their support of data channel multiplexing during IMS session initiation and modification if they decide to use this feature. The originating S-CSCF includes the Feature-Caps header field indicating support of data channel multiplexing in initial INVITE... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.4 Determination of multiplexing and de-multiplexing | When the IMS AS receives the INVITE request with data channel multiplexing, it reports the event to the DCSF for data channel management. The DCSF determines whether the data channel multiplexing is allowed and whether serving network needs to de-multiplex the data channel traffic. If the data channel traffic needs to ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.5 media management for multiplexing and de-multiplexing | If the UE decides to use data channel multiplexing, when the UE generates SDP offer in INVITE or re-INVITE request, the DC stream IDs associated with the data channels to be multiplexed and the application ids combined with the data channels are included in the SDP offer for a single m line.
NOTE 1: How the application... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.1.6 MF/MRF selection | If a MF or MRF needs to be selected, the IMS AS selects a MF or MRF supporting data channel multiplexing by including data channel multiplexing indication in the Nnrf_NFDiscovery_Request service operation. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.1 Bootstrap data channel establishment | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.1.1 Bootstrap data channels multiplexing in originating network | Figure 6.22.2.1.1-1: Multiplexing bootstrap data channels in originating network
1. When the UE wants to multiplex its bootstrap data channels, e.g. local bootstrap data channel and remote bootstrap data channel, the UE includes multiplexed SDP media description in initial INVITE request as described in clause 6.22.1.5... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.1.2 Bootstrap data channel multiplexing in terminating network | Figure 6.22.2.1.2-1: Multiplexing bootstrap data channels in terminating network
1. The originating network sends initial INVITE request with SDP offer for remote bootstrap data channel to UE#2.
2-3. The IMS AS selects and reports event to DCSF.
4. The DCSF determines that local bootstrap and remote bootstrap data chan... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.2 Application data channel establishment | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.2.1 Application data channel multiplexing when both originating and terminating networks support data channel multiplexing | Figure 6.22.2.2.1-1: Application data channel multiplexing when both originating and terminating networks support data channel multiplexing
1. When the UE#1 wants to multiplex its application data channels for app#1, #2 and #3, the UE includes multiplexed SDP media description in initial INVITE request as described in ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.2.2 Application data channel multiplexing when terminating network does not support data channel multiplexing | Figure 6.22.2.2.2-1: Application data channel multiplexing when terminating network does not support data channel multiplexing
1. When the UE#1 wants to multiplex its application data channels for app#1, #2 and #3, the UE includes multiplexed SDP media description in initial INVITE request as described in clause 6.22.1... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.2.3 Option of capability discovery between the originating IMS network and terminating IMS network | Figure 6.22.2.3-1: Capability Discovery between the originating IMS network and terminating IMS network
Key steps:
1. At the system initial running phase, the IBCF-A in IMS-A sends OPTIONS to other interconnected IBCFs to detect the data channel multiplexing capability of its IMS networks. In this case, the IBCF-A send... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.22.3 Impacts on existing nodes and functionality | This solution has impacts to the existing IMS nodes and UE below:
UE:
- includes a Feature-Caps header field indicating its capability of supporting data channel multiplexing in the REGISTER request;
- includes the DC stream IDs associated with the data channels to be multiplexed and the application ids combined with t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.23 Solution #23: Download avatar representation in bootstrap data channel from avatar repository | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.23.1 Description | This solution addresses Key Issue #8 " Support of IMS Avatar Communication " and focuses on how to store the avatar information and how to obtain the avatar representation for the subscriber in the bootstrap data channel.
Figure 6.23.1-1: Architecture option of IMS supporting DC usage (Avatar repository separate with D... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.23.2 Procedures | Figure 6.23.2-1: Person-to-Application (P2A) Application Data Channel set up Signalling Procedure
The steps in the call flow are as follows:
Step 0-24 from clause AC.7.1 (Bootstrap Data Channel Setup Signalling procedure) in TS 23.228 [5] is performed with the differences that:
In step 20, bootstrap data channels have ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.23.3 Impacts on Existing Nodes and Functionality | This solution has some requirements on the existing IMS nodes below:
DCSF:
- Provide avatar ID list in the bootstrap data channel to UE.
Avatar Repository:
- Store avatar representation corresponding with avatar ID.
UE:
- Request and receive avatar ID list through bootstrap data channel.
- Select and download avatar re... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24 Solution #24: Transition Between Avatar and Audio/Video Communication | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.1 Description | Two UEs can communicate with each other through either audio/video communication or Avatar communication. If one UE wants to switch from one of the communication modes to another, the UE triggers the negotiation with DCSF and peer UE for the Avatar media and establishes data channel. Media Function fetches Avatar repre... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.2 Architecture for Avatar Communication | Figure 6.24.2-1 depicts architecture for Avatar communication.
Figure 6.24.2-1: Architecture for Avatar communication
Avatar communication architecture is based on the Data Channel architecture as specified in clause AC.2.1 in TS 23.228 [5].
In the architecture, new added functional entities include:
- Media Function:
... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.3 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.3.1 Transition from audio/video communication to Avatar communication | Figure 6.24.3.1-1 depicts a flow diagram for transition procedure from audio/video communication to Avatar communication.
Figure 6.24.3.1-1: Transition procedure from audio/video communication to Avatar communication
Editor's note: The Figure 6.24.3.1-1 may be restructured to reflect different Avatar rendering options.... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.3.2 Transition from Avatar communication to audio/video communication | Figure 6.24.3.2-1 depicts a flow diagram for transition procedure from Avatar communication to audio/video communication.
Figure 6.24.3.2-1: Transition procedure from Avatar communication to audio/video communication
The steps in the transition procedure are as follows:
0. UE A has Avatar communication with UE B.
1. UE... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.24.4 Impacts on Existing Nodes and Functionality | UE:
- Support capturing sensing data of users and sending it as Avatar data to Media Function;
- Support displaying Avatar representation.
- Optionally support rendering Avatar representation.
Media Function:
- Support rendering Avatar representation based on received Avatar data;
- Support retrieving Avatar representa... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25 Solution #25: Supporting network-based avatar communication by media capability invocation | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.1.1 General | This solution defines the solution for network-based avatar communication addressing the following aspects that defined in the KI#8:
- Study how to enable transcoding between speech and gesture (or text) in an IMS Avatar communication.
- Study how to enable UE based and network-based rendering in case of IMS Avatar com... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.1.2 Architecture | Figure 6.25.1.2-1: Architecture to support network-based avatar communication
To support IMS avatar communication, the architecture is enhanced as follows:
Base Avatar Repository (BAR):
- The Base Avatar Repository is used to store and retrieve the avatar models. BAR can be inside the PLMN, e.g. a new network function,... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.1.3 Reference points | The following reference point is added to support avatar communication service in IMS:
- MC1:
- Reference point between the DCSF and the MF/MRF.
- DCx:
- Reference point between XR AS and BAR.
NOTE: The DCx is out of scope of SA WG2.
The MC1 reference point is used by DCSF to instruct MF the specific media capabilities... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.2.1 Network-based procedure for avatar communication | Figure 6.25.2.1-1: Procedures of network-based avatar communication
Figure 6.25.2.1-1 depicts a typical call flow procedure of network-based avatar communication. The main steps in the call flow are as follows:
0. IMS session and bootstrap data channel has been established, and UE#1 has downloaded and run the avatar co... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.2.2 Transcoding between speech and gesture (or text) in communication | Figure 6.25.2.2-1 depicts a flow diagram for transcoding between speech and gesture (or text) in communication.
Figure 6.25.2.2-1: Transcoding procedure between speech and gesture (or text) in communication
The steps in the transition procedure are as follows:
0. Audio/video IMS session and Bootstrap data channel estab... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.25.3 Impacts on Existing Nodes and Functionality | XR AS impact:
- Support the subscription of avatar communication service and session control for avatar communication service.
DCSF impact:
- Support identification the service media control request and send to MF/MRF.
IMS AS impact:
- Support selecting a MF/MRF instance for avatar call based on the service type.
MF/MR... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26 Solution #26: Support for Avatars in AR Calls | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26.1.1 Function Mapping | The NG-RTC IMS architecture is defined in clause AC.9.2 of TS 23.228 [5] and is shown below.
Figure 6.26.1.1-1: Architecture to support AR communication (Rel-18)
The AR Application Server is responsible for setting up the scene and adding the participant's Avatars to the scene. It performs the functionality of Scene Ma... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26.1.2 Architecture Enhancements | As discussed in 6.26.1.1, enhancements to the IMS architecture are anticipated to provide support for Avatars in AR calls. The following figure depicts the enhanced architecture for AR calls with Avatars.
Figure 6.26.1.2-1: Enhanced architecture for AR calls with Avatars
The Digital Asset Repository (DAR):
- The DAR st... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26.2 Procedures | The procedures in this clause are based on the following assumptions:
- Animation of the Avatar is either done on the receiving UE (UE-B) or is delegated to the MF/MRF.
- Network rendering is not performed but can easily be added as an independent step to the AR call.
The following figure depicts the call flow that is ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.26.3 Impacts on existing services, entities and interfaces | DAR impacts:
- Receive uploaded Avatar representation from UE.
- Store or update Avatar representation.
- Receive requests of Avatar representation.
- Authorize access of Avatar representation.
- Share Avatar representation to the authorized UE.
MF/MRF impacts:
- Receive animation streams.
- Send animation streams.
- G... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27 Solution #27: Early capability negotiation for IMS Avatar Communication | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.1 General | SA WG4 introduces Avatar Reference Architecture, as shown in clause 7 of TR 26.813 [8], and defines Base Avatar and Animation Data, which are combined and produces Animated Avatar. This solution relies on those SA WG4 definitions. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.2 Architecture | Rel-18 IMS DC architecture depicted in Figure AC.2.1-1 of TS 23.228 [5] is assumed. In addition, a new entity called DAC (i.e. Digital Asset Container) is introduced with an interface with NEF.
Figure 6.27.1.2-1: DAC |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.3 Capability negotiation | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.3.1 Definition of Avatar type and Required UE avatar capability | This solution assumes that a user chooses and uses one of multiple Base Avatars, and each Base Avatar is defined as a combination of Avatar type and Required UE avatar capability. Avatar type can be "official" or "private" or else. Required UE avatar capability is a capability that UE is required to have to handle a ce... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.3.2 Negotiation steps | A caller chooses an Avatar type of the caller. An originating UE A sends Offered Required UE avatar capability list to a terminating UE B. UE B sends Accepted Required UE avatar capability list to UE A. UE A sends Selected Required UE avatar capability, and Base Avatar and default Animation Data of the caller according... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.4 Avatar objects storage and access | Base Avatar and default Animation Data in the above description are actually a pointer (e.g. URL) to retrieve them. This solution proposes to introduce DAC (i.e. Digital Asset Container) to store Base Avatar and default Animation Data among others. UE B receives a URL from UE A and accesses NEF of PLMN of UE A by using... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.1.5 Transcoding of Avatar | There are cases that UE B does not have a capability necessary to handle avatar and that UE A still wants to show avatar. This solution proposes to introduce a pro-active transcoding for those cases. It is assumed that Animation Data is sent and received by using an application data channel. DCSF in PLMN of UE A instru... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.2.1 Storing Avatar objects into DAC | Figure 6.27.2.1-1: Storing Avatar objects into DAC
1. UE application behaves as if an AF and requests NEF to store Base Avatar and default Animation Data.
2. NEF requests DAC to store Base Avatar and default Animation Data.
3. DAC stores Base Avatar and default Animation Data. DAC sends a response containing a URL to a... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.2.2 Early capability negotiation and transcoding | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.2.2.1 Transcoding is not needed | Figure 6.27.2.2.1-1: Early capability negotiation and transcoding is not needed
1. Caller selects an Avatar type and makes a call. UE A sends SIP INVITE containing SDP offer for an audio media and an application DC media with Offered Required UE avatar capability list.
2. IMS AS sends a message to DCSF.
3. DCSF instruc... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.2.2.2 Transcoding is needed | Figure 6.27.2.2.2-1: Early capability negotiation and transcoding is needed
1-6. The same as in the previous figure.
7-8. IMS AS receives 18X containing SDP answer for an audio media and a recvonly video media.
9. IMS AS sends a message to DCSF.
10. DCSF recognizes that UE B cannot handle avatar communication and updat... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.27.3 Impacts on services, entities and interfaces | The solution has the following impacts:
DAC:
- This stands for Digital Asset Container. DAC is a new NF that stores Base Avatar and default Animation Data among others.
NEF:
- NEF is to be capable of handling a mapping of an external URL and an internal URL to DAC.
UE:
- UE is to be capable of performing the avatar cap... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28 Solution #28: Configuration of PS Data Off exemption on IMS DC | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28.1 Description | Based on the clarification in clause 10.2 of TS 22.011 [22], "Services over IMS Data Channel" is configured as a whole service in 3GPP PS Data Off Exempt. Operators may further control whether each individual DC application is allowed when the PS Data Off Exempt of services over IMS Data Channel is on.
In summary, foll... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.