Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.228  Word version:  19.0.0

Top   Top   Up   Prev   None
1…   3…   4…   4.2.4…   4.3…   4.4…   4.13…   4.16…   5…   5.2…   5.3…   5.4…   5.4.7…   5.4.8…   5.4a…   5.5…   5.5.3…   5.6…   5.6.3…   5.7…   5.7.3…   5.7.5…   5.7.8…   5.8…   5.10…   5.11…   5.11.3…   5.11.3.3   5.11.3.4   5.11.4…   5.11.5…   5.11.5.3…   5.11.6…   5.12…   5.16…   5.16.2…   5.19…   5.20…   A…   E…   E.2.2…   G…   G.5…   H   I…   J…   K…   L…   M…   M.3…   N…   P…   Q…   Q.2.5…   R…   S…   T…   U…   U.2…   V…   W…   X…   Y…   Z…   AA…   AA.3…   AB…   AC…   AC.7…   AC.7.2…   AC.7.2.2   AC.7.2.3…   AC.7.4…   AC.9…   AC.10… 
AC.10 Standalone IMS Data Channel Sessions  AC.10.1 General  AC.10.2 Procedures  AC.10.2.1 Originating Standalone Bootstrap DC Setup using PSI  AC.10.2.2 Adding Application DC to Standalone IMS DC Session with Bootstrap DC  AC.10.2.3 Combined Standalone Bootstrap DC and Application DC Setup  AC.10.2.4 Adding MMTel Media to Standalone IMS Data Channel Session  AC.10.2.5 Removing MMTel Media from IMS Data Channel Session  $ Change history 

 

AC.10  Standalone IMS Data Channel Sessions |R19|  p. 393

AC.10.1  General  p. 393

Data channels can also be established in a standalone IMS data channel session. A standalone IMS data channel session with only standalone bootstrap DC is used for downloading application list and applications from DCSF. A standalone IMS data channel session with a combination of standalone bootstrap DC and application DC is used to establish application DC for a downloaded application to the remote UE, which allows the remote UE to download the application if not yet downloaded after accepting the bootstrap DC, and update the session to use the application in the same session.
When standalone IMS data channel session is supported, the UE can also establish standalone IMS data channel session with only bootstrap DC, or with combination of standalone bootstrap DC and application DC, or update standalone IMS data channel session with bootstrap DC by adding application DC to the session.
When standalone IMS data channel session is allowed, based on operator policy, additional subscription information for standalone data channel service may be included in service subscription for IMS Data Channel to be used by the IMS AS to determine whether to accept a standalone IMS data channel session.
When subscription to standalone IMS data channel session is needed, and if a UE that has not subscribed to standalone IMS data channel session establishes a standalone IMS data channel session, the IMS AS shall reject the session establishment.
Standalone IMS data channel sessions use SIP session timer as per RFC 4028 to avoid hanging resources in the UE and the network. Usage of SIP session timer in IMS is specified in TS 24.229.
The standalone IMS data channel session is terminated by the existing session release procedure specified in clause AC.7.6. The session release may be triggered by the expiry of the session timer or by sending a SIP BYE request.
Up

AC.10.2  Procedures  p. 393

AC.10.2.1  Originating Standalone Bootstrap DC Setup using PSI  p. 393

The standalone IMS data channel session setup with only bootstrap DC is triggered by a UE or the user of a UE for downloading application list and/or applications. After standalone bootstrap DC is established, the UE downloads the application list via the bootstrap DC, and may display the list of application information to the user for selection, downloading, and/or initiating standalone application DC. The UE terminates the standalone IMS data channel session when the session timer expired.
Figure AC.10.2.1-1 depicts a signalling flow diagram for establishing a standalone bootstrap data channel using PSI.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. AC.10.2.1-1: Originating Standalone Bootstrap DC Setup using PSI
Figure AC.10.2.1-1: Originating Standalone Bootstrap DC Setup using PSI
(⇒ copy of original 3GPP image)
Up
Step 1.
UE#1 sends the SIP INVITE request with an initial SDP to the IMS AS, through P-CSCF and S-CSCF in the originating network. The Request URI of the SIP INVITE message is a specific target URI, such as a specific PSI indicating standalone bootstrap DC. The initial SDP contains offers only for the bootstrap data channel establishment request with bootstrap DC stream ID.
Step 2-4.
Steps 2-4 of clause AC.7.1 apply.
Step 5.
Since the SessionEstablishmentRequestEvent indicates that served user is offered local bootstrap media, DCSF, based on the value of the Called ID (i.e. the specific PSI) and the content of the initial SDP, determines that UE#1 requests to establish a standalone bootstrap DC and reserves only originating side MDC1 media information, which are used to receive UE request for application downloading from MF or MRF.
Step 6.
DCSF invokes the Nimsas_MediaControl_MediaInstruction (Session ID, Media Instruction Set) operation based on its policies instructing the IMS AS how to set up bootstrap data channel with MF for originating side and to terminate the session. The MediaInstructionSet provided by the DSCF, includes its MDC1 media endpoint addresses created in step 5, DC Stream ID, and the replacement HTTP URL representing the application list offered via the MDC1 interface.
Step 7.
Step 7 of clause AC.7.1 applies.
Step 8.
IMS AS invokes Nmf_MRM_Create (List of Media Termination Descriptors) service operation to instruct MF to allocate required data channel media resources for originating side only. IMS AS request creation of only one Media Termination which representing the local bootstrap media to be terminated.
Step 9-10.
Steps 9-10 of clause AC.7.1 apply.
Step 11.
IMS AS terminates the IMS session based on the specific Request URI and sends 18X response with the SDP answer through S-CSCF and P-CSCF to UE#1.
Step 12-13.
The session with bootstrap data channel is established.
Step 14.
The bootstrap data channels have been established between originating MF or MRF and UE#1. The UE#1 sends application request messages to MF or MRF to request a data channel application or an application list if multiple DC applications are available, via the established bootstrap data channel with its data channel capabilities. The MF or MRF replaces the root URL with the replacement URL received in steps 8 and forwards the message to received media point of DCSF. The DCSF provides the application list and proper data channel applications further to UE#1 based on their data channel capabilities and their choices through MF or MRF.
Step 15-16.
If the established bootstrap DC is not used for a period of time (expiry of the session timer), UE#1 sends SIP BYE to release the bootstrap DC to save power.
Up

AC.10.2.2  Adding Application DC to Standalone IMS DC Session with Bootstrap DC  p. 395

The standalone IMS data channel session setup between two UEs is triggered by the user of an originating UE. If the user selected DC application has not been downloaded yet, the originating UE initiates standalone bootstrap DC setup during the IMS session setup procedure. The standalone bootstrap DC setup is performed separately by originating UE and terminating UE with DCSF. The originating UE downloads the DC application selected by the user via the bootstrap DC, updates the IMS session to add application DC with the terminating UE and indicates the selected DC application to the terminating UE. If the indicated DC application is not downloaded yet, the terminating UE downloads the indicated DC application via the bootstrap DC.
In this procedure, the assumption is that the alert to terminating user will only happen after the originating UE downloaded the application and updated the application DC, i.e. when the indicated DC application is downloaded, the terminating UE alerts the user and displays the application information including the required rights to the user.
When the user of the terminating UE accepts to use the DC application for the communication, the IMS session is answered by the terminating UE.
The procedure specified in clause AC.7.1 applies with the following differences:
  • In step 1, UE#1 sends the initial INVITE request with an SDP offer only including media component for bootstrap data channel for originating side and optional for terminating side.
  • In step 2, the IMS AS determines whether the IMS session is a standalone IMS data channel session, and determines if the session is allowed to be established based on local configuration or subscription data. If standalone IMS data channel session is not allowed, the IMS AS shall reject the request.
  • In step 11, the media component for bootstrap data channel for terminating side may be included in an SDP early offer to enable the terminating side downloading the DC Application selected by the user of UE#1 before ringing.
  • In step 14, SIP precondition is not needed, and after the bootstrap DC is established, the UE#1 sends SIP UPDATE message to add an application DC selected by the user of UE#1.
  • Steps 23-24 may be skipped.
  • In step 25, the UE#2 alerts the user of UE#2 after the corresponding DC Application is downloaded, and answers the IMS session when the user of UE#2 accepts to use the corresponding DC Application.
Up

AC.10.2.3  Combined Standalone Bootstrap DC and Application DC Setup  p. 395

The standalone IMS data channel session setup between two UEs is triggered by the user of an originating UE. If the user selected DC application has been downloaded, the originating UE initiates combined standalone bootstrap DC and application DC setup during the IMS session setup procedure. The standalone bootstrap DC setup is performed separately by originating UE and terminating UE with DCSF, the application DC is established between the originating UE and terminating UE. If the selected DC application is not downloaded yet, the terminating UE downloads the selected DC application via the bootstrap DC.
In this procedure, the assumption is that the alert to terminating user will only happen after the originating UE downloaded the application and updated the application DC, i.e. when the selected DC application is downloaded, the terminating UE alerts the user and displays the application information including the required rights to the user.
When the user of the terminating UE accepts to use the application for the communication, the IMS session is answered by the terminating UE.
The procedure specified in clause AC.7.2.1 applies with the following differences:
  • In step 1, UE#1 sends initial INVITE request with an SDP offer including the combination of bootstrap DC and application DC components.
  • In steps 7 and 8, the media component for bootstrap data channel for terminating side may be included in an SDP early offer to enable the terminating side downloading application before ringing.
  • In step 10, if the UE#2 has not yet downloaded the application, the UE#2 returns a 183 with the SDP answer for bootstrap DC and set ports of application DC to zero, and downloads the corresponding DC Application signalled in the SDP offer.
  • In step 18, the UE#1 sends a SIP UPDATE with an updated SDP contains the bootstrap data channel information, as well as the requested application data channel and the associated DC application binding information, according to TS 26.114. When the corresponding DC Application is downloaded, the UE#2 sends 200 OK with SDP answer response for the SIP UPDATE, then the application DC is established. The UE#2 start to play ringtone for the user of UE#2 and sends 180 Ringing response to UE#1 after the DC application has been downloaded and the application DC is established. The UE#2 returns a 200 OK response for SIP INVITE if the user of UE#2 accepts to use the DC application requested by UE#1.
Up

AC.10.2.4  Adding MMTel Media to Standalone IMS Data Channel Session  p. 396

When a standalone IMS data channel session between two UEs is ongoing, any of the UE may be triggered by the corresponding user to add audio/video/messaging media into the IMS session, which turns the standalone IMS data channel session to IMS data channel session.
Figure AC.10.2.4-1 depicts a signalling flow diagram for adding audio/video/messaging media to standalone IMS data channel session between two UEs.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. AC.10.2.4-1: Adding Audio/Video/Messaging Media to standalone IMS data channel session
Figure AC.10.2.4-1: Adding Audio/Video/Messaging Media to standalone IMS data channel session
(⇒ copy of original 3GPP image)
Up
Step 1.
A standalone application data channel has been established between UE-A and UE-B.
Step 2.
UE-A sends SIP re-INVITE which include the media description of both standalone application data channel and audio/video/messaging media description.
Step 3.
The IMS AS, DCSF and UE-B handles the SIP re-INVITE as specified in clause AC.7.2.1.
Step 4.
UE-B sends 200 responses to UE-A through IMS AS, indicating the call has been established. IMS AS sends notify message to DCSF as specified in Rel-18.
Up

AC.10.2.5  Removing MMTel Media from IMS Data Channel Session  p. 397

When a IMS data channel session between two UEs is ongoing, any of the UE may be triggered by the corresponding user to remove audio/video media from the IMS session, which turns the IMS data channel session to standalone IMS data channel session.
Figure AC.10.2.5-1 depicts a signalling flow diagram for removing audio/video media from IMS data channel session between two UEs.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. AC.10.2.5-1: Removing Audio/Video/Messaging Media from IMS data channel session
Figure AC.10.2.5-1: Removing Audio/Video/Messaging Media from IMS data channel session
(⇒ copy of original 3GPP image)
Up
Step 1.
An IMS DC session has been established between UE-A and UE-B, which include audio/video and IMS DC media.
Step 2.
UE-A sends SIP re-INVITE with an SDP containing media information for audio/video media and data channel, which sets the port number of audio/video media stream to zero, as specified in RFC 3264.
Step 3.
The IMS AS, DCSF and UE-B handles the SIP re-INVITE.
Step 4.
UE-B sends 200 responses to UE-A through IMS AS, indicating the audio/video media has been removed. IMS AS sends notify message to DCSF as specified in Rel-18.
Up

$  Change history  p. 399

Up   Top