Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.228  Word version:  18.3.0

Top   Top   Up   Prev   Next
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.7.4  NF service registration and discoveryp. 380

If the NRF is used for NF registration and discovery, the DCSF and the MF shall register their services at the NRF before providing services to consumers, and existing NRF based mechanism needs to be extended with DC specific profiles according to clause 4.17.1 of TS 23.502.

AC.7.4.1  DCSF Registration and Discoveryp. 380

The DCSF profile includes NF type=DCSF and may include IMPU ranges for calling identities or called identities of users it serves.
The DCSF can update and deregister in the NRF after registration and the procedures are specified in clauses 4.17.2 and 4.17.3 of TS 23.502.
After registration in the NRF, the DCSF can be discovered by other consumer NFs as specified in clauses 4.17.4 and 4.17.5 of TS 23.502.
Up

AC.7.4.2  MF Registration and Discoveryp. 381

The MF profile includes NF type=MF and may include MF location information to select a local MF to minimize transmission delays in the media path.
The MF can update and deregister in the NRF after registration and the procedures are specified in clauses 4.17.2 and 4.17.3 of TS 23.502.
After registration in the NRF, the MF and its services can be discovered by other consumer NFs as specified in clauses 4.17.4 and 4.17.5 of TS 23.502.
Up

AC.7.5  Providing subscriber specific graphical user interface to the UEp. 381

According to clause 6.2.10.1 of TS 26.114, the UE can send a HTTP GET Request for the root ("/") URL through the bootstrap data channel which is replied with a data channel application describing the graphical user interface and the logic needed to handle any further data channel usage beyond the bootstrap data channel itself. The graphical user interface can e.g. contain a menu of applications, from which the user can choose one or several. The graphical user interface should be subscriber specific and contain only applications for which the user has subscribed to and is authorized to use. To provide the graphical user interface containing subscriber specific data channel applications via the bootstrap data channel to the UE, the DCSF, when receiving a call event notification including subscriber specific information and optionally stream ID from the IMS AS, creates the URL identifying the graphical user interface corresponding to the stream ID (if available) for this subscriber.
Up

AC.7.6  Termination of IMS Data Channelp. 381

When a bootstrap data channel is established successfully, the bootstrap data channel shall be kept available during the IMS MMTel session, and it shall be terminated along with the release of the call.
The application data channel shall be terminated along with the release of the call or be terminated by closing this application separately. In the latter case, the UE triggers a SDP negotiation to release the application data channel.
The termination of application data channel shall not have any impact on the audio or video within the IMS sessions.
Up

AC.7.7  QoS requirement of IMS Data Channelp. 381

The appropriate 5QI/QCI for the QoS flows of the IMS data channel media, as defined in TS 26.114, shall be applied over the 5GS system or EPS system for IMS data channel.

AC.7.8  Mr'/Cr Procedurep. 381

To enable the use of MRF as media resource function for IMS DC, there is a need to map the MF MRM SBI services, operations, and attributes to Mr'/Cr requests and responses. Table AC.7.8-1 defines a high level mapping between MF MRM SBI services, operation and Mr'/Cr Requests:
Nmf_MediaResourceManagement (MRM) service operation name Source Destination Mr'/Cr Request
Nmf_MRM_Create (create one media context including one media termination)IMS ASMRFCINVITE <media context service information>
Nmf_MRM_Update (add new media termination to existing media context with one or multiple media streams)IMS ASMRFCINVITE <media context service information>
Nmf_MRM_Update (modifying the 'DC Media Specification' data of one or multiple media streams of a media termination)IMS ASMRFCINFO
Nmf_MRM_Update (add/update/delete media stream of an existing media termination)IMS ASMRFCreINVITE
Nnf_MRM_Delete (media context delete)IMS ASMRFCBYE
Up

AC.8  Proceduresp. 382

AC.8.1  IMS DC capability negotiationp. 382

The IMS network and the UE need to mutually negotiate the capability of supporting IMS data channel mutually.
IMS data channel capability negotiation includes two aspects:
  • The network discovers the data channel capability of the UE.
  • The UE discovers the data channel capability of the network.
When the UE supporting IMS data channel registers on the IMS network, it includes the media feature tag as specified in TS 26.114 in the Contact header field of the initial REGISTER request to allow the home IMS network discovers its IMS data channel capability.
If the IMS network supports IMS data channel, the S-CSCF includes a Feature-Caps header field indicating its data channel capability in the 200 OK response to the initial and any subsequent REGISTER request, which is used by the UE to discover the IMS data channel capability of its home IMS network.
When the UE supporting IMS data channel initiates an IMS session, it includes the media feature tag as specified in TS 26.114 in the Contact header field of the initial INVITE or a re-INVITE request to remote UE, regardless of data channel media being part of the SDP or not.
The UE shall not include data channel media description in the SDP offer of the initial INVITE request or any subsequent re-INVITE, if the S-CSCF has not included the data channel capability indication in the Feature-Caps header field in the 200 OK response either to the REGISTER or subsequent REGISTER request.
Up

Up   Top   ToC