Tech-invite3GPPspaceIETF RFCsSIP
indexN21222324252627282931323334353637384‑5x

Content for  TS 23.228  Word version:  18.2.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…

 

AA (Normative)  Support of SBA in IMS |R16|p. 344

AA.1  Generalp. 344

AA.1.0  Overviewp. 344

This Annex AA describes support for SBA for IMS nodes. This Annex is intended to be used in conjunction with 5GC.

AA.1.1  Architectural Supportp. 344

Figure AA.1.1-1 shows the architecture to support SBA interactions between IMS entities.
Reproduction of 3GPP TS 23.228, Fig. AA.1.1-1: System Architecture to support SBA in IMS
Up
Figure AA.1.1-2 shows the architecture using the reference point representation.
Reproduction of 3GPP TS 23.228, Fig. AA.1.1-2: System Architecture to support SBA in IMS in reference point representation
Up

AA.1.2  Reference point to support SBA in IMSp. 344

Following reference points are realized by service-based interfaces in IMS:
N5:
Reference point between the PCF and an AF.
N70:
Reference point between an SBI capable I/S-CSCF and an SBI capable HSS.
N71:
Reference point between an SBI capable IMS AS and an SBI capable HSS.
DC1:
Reference point between an SBI capable IMS AS and DCSF.
DC2:
Reference point between an SBI capable IMS AS and DCMF.
N72:
Reference point between DCSF and an SBI capable HSS.

AA.1.3  Service based interface to support SBA in IMSp. 345

Npcf:
Service-based interface exhibited by PCF.
Nhss:
Service-based interface exhibited by an SBI capable HSS.
These SBI services provide equivalent functionality to the Diameter Rx and Cx/Sh reference points.
Nimsas:
Service-based interface exhibited by an SBI capable IMS AS.
Ndcmf:
Service-based interface exhibited by DCMF.
These SBI services provide functionality to support data channel management and media handling in IMS network.
To support co-existence of IMS nodes supporting SBA services and IMS nodes not supporting SBA services SBI enabled IMS nodes may support both SBI and non-SBI interfaces.
Up

AA.2  IMS SBA Servicesp. 345

AA.2.1  HSS Servicesp. 345

AA.2.1.1  Generalp. 345

The following Table shows the services exposed by an SBI capable HSS.
Service Service Operations Operation Semantics Example Consumer(s)
imsSubscriber Data Management (_ImsSDM)GetRequest/ResponseS-CSCF, I-CSCF, AS
SubscribeSubscribe/NotifyS-CSCF, AS
UnsubscribeSubscribe/NotifyS-CSCF, AS
NotificationSubscribe/NotifyS-CSCF, AS
UpdateRequest/ResponseAS
imsUE Context Management (_ImsUECM)RegistrationRequest/ResponseS-CSCF
DeregistrationNotificationSubscribe/NotifyS-CSCF
DeregistrationRequest/ResponseS-CSCF
AuthorizeRequest/ResponseI-CSCF
UpdateRequest/ResponseS-CSCF
RestorationInfoGetRequest/ResponseS-CSCF
RestorationInfoUpdateRequest/ResponseS-CSCF
ImsUE AuthenticationGetRequest/ResponseS-CSCF
Up

AA.2.1.2  Nhss_ImsUEContextManagement (ImsUECM) servicep. 346

AA.2.1.2.1  Nhss_ImsUECM_Registration service operationp. 346
Service operation name:
Nhss_ImsUECM_Registration
Description:
This service operation registers the serving S-CSCF assigned to an IMS User. If authentication is not to be performed, this operation also sets the registration state. The S-CSCF is implicitly subscribed to be notified when it is deregistered in HSS. This notification is done by means of Nhss_ImsUECM_DeregistrationNotification operation.
Inputs, Required:
Public Identity, S-CSCF name, Registration Type (e.g. Initial Registration, Unregistered).
Inputs, Optional:
Private Identity.
Outputs, Required:
Result indication.
Outputs, Optional:
List of registered Private Identities sharing the same Public Identity which is being registered, S-CSCF Restoration indication.
Up
AA.2.1.2.2  Nhss_ImsUECM_Deregistration service operationp. 346
Service operation name:
Nhss_ImsUECM_Deregistration
Description:
This service operation deregisters the S-CSCF allocated to a public identity.
Inputs, Required:
S-CSCF name, Deregistration Type.
Inputs, Optional:
User Identity (Private Identity and/or Public Identity), P-CSCF Restoration indication, Session Priority.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
AA.2.1.2.3  Nhss_ImsUECM_DeregistrationNotification service operationp. 346
Service operation name:
Nhss_ImsUECM_DeregistrationNotification
Description:
This service operation enables HSS to inform a S-CSCF which has previously registered in HSS of a Public Identity deregistration. This notification corresponds to an implicit subscription.
Inputs, Required:
Private Identity, Reason for Deregistration.
Inputs, Optional:
Public Identity, Associated Private Identities.
Outputs, Required:
Result indication.
Outputs, Optional:
Associated Private Identities, Identities with Emergency Registration.
AA.2.1.2.4  Nhss_ImsUECM_Authorize service operationp. 346
Service operation name:
Nhss_ImsUECM_Authorize
Description:
This service operation is used by the I-CSCF to request authorization from HSS for:
  • The registration of a Public Identity by a UE in a P-CSCF network identifier according to the IMS User's subscription and operator limitations/restrictions.
  • The reception of a terminating request based on the user state and IMS user's subscription (e.g. IMS User's barring status).
If the IMS User is authorized, the HSS may provide the address of the S-CSCF assigned to the Public Identity if any.
Additionally, this service operation is used to authorize in HSS a S-CSCF reselection (e.g. after I-CSCF detection if a S-CSCF failure).
Inputs, Required:
Public Identity, Authorization Type.
Inputs, Optional:
Private User Identity, P-CSCF network identifier.
Outputs, Required:
Result indication.
Outputs, Optional:
S-CSCF name.
Up
AA.2.1.2.5  Nhss_ImsUECM_Update service operationp. 347
Service operation name:
Nhss_ImsUECM_Update
Description:
This service operation updates the registration state of a Public Identity or Private Identity in HSS i.e. to update the registration state from Not Registered or Unregistered to Registered state.
Inputs, Required:
Public Identity, S-CSCF name.
Inputs, Optional:
Private Identity.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
AA.2.1.2.6  Nhss_ImsUECM_RestorationInfoGet service operationp. 347
Service operation name:
Nhss_ImsUECM_RestorationInfoGet
Description:
This service operation is used between the S-CSCF and the HSS to retrieve information from HSS to support the S-CSCF procedures.
Inputs, Required:
Public Identity.
Inputs, Optional:
Private Identity.
Outputs, Required:
Result Indication.
Outputs, Optional:
Restoration data.
AA.2.1.2.7  Nhss_ImsUECM_RestorationInfoUpdate service operationp. 347
Service operation name:
Nhss_ImsUECM_RestorationInfoUpdate
Description:
This service operation is used between the S-CSCF and the HSS to update information in HSS to support the S-CSCF Restoration procedures.
Inputs, Required:
Private Identity, Public Identity, Restoration data.
Inputs, Optional:
None.
Outputs, Required:
Result indication.
Outputs, Optional:
None.

AA.2.1.3  Nhss_ImsSubscriberDataManagement (ImsSDM) servicep. 347

AA.2.1.3.1  Generalp. 347
IMS Subscriber data types used in the Nhss_ImsSDM Service are defined in Table AA.2.1.3.1-1 below.
IMS Subscriber data Description
Service Profile Data This may include e.g. service parameters, the S-CSCF allocated to a public identity or the list of S-CSCFs and their capabilities, Application Server address, triggers, information on subscribed media, profile parameters (e.g. barring indicator, etc.) as defined in TS 29.228.
Service Profile Data is consumed by CSCF.
Repository Data Data that is understood syntactically but not semantically by the HSS (unstructured Data). It is data that an AS may store in the HSS to support its service logic. One example is data that an AS stores in the HSS, using it as a repository.
Service Indication identifies the set of service related transparent data associated to a Public Identity.
Repository Data is consumed by IMS-AS.
Non-Transparent Data Data that is understood both syntactically and semantically by the HSS e.g. location information. Non-Transparent Data is structured using data references as defined in TS 29.328.
Non-Transparent Data is consumed by IMS-AS.
At least a mandatory key is required for each IMS Subscriber Data Type to identify the corresponding data as defined in Table AA.2.1.3.1-2 below.
IMS Subscriber Data Types Data Key Data Sub Key
Service Profile DataPublic Identity
Repository DataPublic IdentityService Indication
Non-Transparent DataSee NOTE 1
NOTE 1:
TS 29.328 defines the data keys/subkeys required by each data reference.
Up
AA.2.1.3.2  Nhss_ImsSDM_Get service operationp. 348
Service operation name:
Nhss_ImsSDM_Get
Description:
This service operation enables the NF consumer to fetch the service profile data, repository data, and non-transparent data references for an IMS User.
The HSS shall check that the requested NF consumer is authorized to fetch the requested data. In the case that the requested data is Repository data, the HSS may also authorize based on service indication.
Inputs, Required:
NF Type, IMS Subscriber data type(s), Key for each IMS Subscriber data type(s).
Inputs, Optional:
Application Service Identity.
Outputs, Required:
Result indication.
Outputs, Optional:
Requested Data.
Up
AA.2.1.3.3  Nhss_ImsSDM_Subscribe service operationp. 348
Service operation name:
Nhss_ImsSDM_Subscribe
Description:
The NF consumer subscribes for updates to requested data. HSS shall check that the requested NF consumer is authorized to subscribe to requested updates.
Inputs, Required:
NF Type, IMS Subscriber data type(s), Key for each IMS Subscriber data type(s).
Inputs, Optional:
Application Server Identity.
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional:
None.
AA.2.1.3.4  Nhss_ImsSDM_Unsubscribe service operationp. 349
Service operation name:
Nhss_ImsSDM_Unsubscribe
Description:
The NF consumer unsubscribes for updates to Requested data.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
AA.2.1.3.5  Nhss_ImsSDM_Notification service operationp. 349
Service operation name:
Nhss_ImsSDM_Notification
Description:
This service operation enables HSS to notify a NF of any changes to what the NF subscribed to.
Inputs, Required:
IMS Subscriber data type(s), Key for each IMS Subscriber data type(s).
Inputs, Optional:
None.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
AA.2.1.3.6  Nhss_ImsSDM_Update service operationp. 349
Service operation name:
Nhss_ImsSDM_Update
Description:
The NF consumer updates HSS subscription data if authorized to do so.
Inputs, Required:
NF Type, IMS Subscriber data type(s), Key for each IMS Subscriber data type(s).
Inputs, Optional:
Application Service Identity.
Outputs, Required:
Result.
Outputs, Optional:
None.

AA.2.1.4  Nhss_ImsUEAuthentication servicep. 349

AA.2.1.4.1  Nhss_ImsUEAuthenticate_Get service operationp. 349
Service operation name:
Nhss_ImsUEAuthenticate_Get
Description:
This service operation is used between the S-CSCF and the HSS to exchange information to support the authentication between the end user and the home IMS network.
Inputs, Required:
Private User Identity, Public User Identity, Authentication Data (Authentication Scheme).
Inputs, Optional:
Authentication Data (Authentication Context, Authorization Information).
Outputs, Required:
Result Indication.
Outputs, Optional:
User Identity, Authentication Data (e.g. AV).

AA.2.2  Mapping of Cx and Sh operations and terminology to HSS SBI servicesp. 350

AA.2.2.1  Generalp. 350

This clause gives mappings from Cx and Sh operations to HSS SBI services and service operations.

AA.2.2.2  Mapping of Cx messages to HSS SBI servicesp. 350

The following Table defines the mapping between stage 2 Cx messages and HSS SBI services and service operations:
Cx message Source Destination HSS SBI service operation name
Cx-QueryI-CSCFHSS Nhss_ImsUECM_Authorize
Cx-Select-PullI-CSCFHSS Nhss_ImsSDM_Get (see NOTE 1)
Cx-PutS-CSCFHSS Nhss_ImsUECM_Registration (see NOTE 2)
Nhss_ImsUECM_Deregistration (see NOTE 3)
Nhss_ImsUECM_Update (see NOTE 4)
Nhss_ImsUECM_RestorationInfoUpdate (see NOTE 5)
Cx-PullS-CSCFHSS Nhss_ImsSDM_Get (see NOTE 6)
Nhss_ImsSDM_Subscribe (see NOTE 6)
Nhss_ImsSDM_Unsubscribe
Nhss_ImsUECM_RestorationInfoGet (see NOTE 7)
Cx-Location-QueryI-CSCFHSS Nhss_ImsUECM_Authorize
Nhss_ImsSDM_Get (see NOTE 8)
Cx-AuthDataReqS-CSCFHSS Nhss_ImsUECM_Registration (see NOTE 9)
Nhss_ImsUEAuthenticate_Get
Cx-DeregisterHSSS-CSCF Nhss_ImsUECM_DeregistrationNotification
Cx-Update_Subscr_DataHSSS-CSCF Nhss_ImsSDM_Notification
NOTE 1:
Corresponds to Cx-Select-Pull for the requests of S-CSCF capabilities from I-CSCF to the HSS.
NOTE 2:
Corresponds to Cx-Put for Registration of S-CSCF in HSS during Registration/Re-registration and Unregistered cases.
NOTE 3:
Corresponds to Cx-Put for de-registration of S-CSCF in HSS.
NOTE 4:
Corresponds to Cx-Put message for updating the registration state of Public Identity in HSS.
NOTE 5:
Corresponds to Cx-Put message for storing S-CSCF Restoration data during IMS registration procedures.
NOTE 6:
Corresponds to Cx-Pull when S-CSCF needs to fetch and subscribe to notification of changes in IMS User's Service Profile Data.
NOTE 7:
Corresponds to Cx-Pull for retrieval of S-CSCF Restoration data from HSS.
NOTE 8:
Corresponds to Cx-Location-Query for the requests of S-CSCF capabilities from I-CSCF to the HSS.
NOTE 9:
Corresponds to Cx-Put for the assignment of a S-CSCF during execution of the authentication of the IMS User.
Up

AA.2.2.3  Mapping of Sh messages to HSS SBI servicesp. 350

The following Table defines the mapping between stage 2 Sh messages and HSS SBI services and service operations:
Sh message Source Destination HSS SBI service operation name
Sh-PullASHSSNhss_ImsSDM_Get
Sh-UpdateASHSSNhss_ImsSDM_Update
Sh-Subs-NotifASHSS Nhss_ImsSDM_Subscribe
Nhss_ImsSDM_Unsubscribe
Nhss_ImsSDM_Get
Sh-NotifHSSASNhss_ImsSDM_Notification
Up

AA.2.4  IMS AS Services |R18|p. 351

AA.2.4.1  Generalp. 351

The following Table shows the IMS AS Services and IMS AS Service Operations.
Service Name Service Operations Operation Semantics Example Consumer(s)
Nimsas_SessionEventControlSubscribeSubscribe/NotifyDCSF
NotifySubscribe/NotifyDCSF
Nimsas_MediaControlMediaInstructionRequest/ResponseDCSF
Up

AA.2.4.2  Nimsas_SessionEventControlp. 351

AA.2.4.2.1  Generalp. 351
Service description: This service enables the consumer to be notified about session events when served IMS subscribers takes part in IMS sessions.
The following operations are available for this service:
  • Explicit subscription to receive session events. This is not specified in this Release. In this Release an implicit subscription is assumed where the IMS AS notifies a configured or discovered DSCF of a call event through a Notify.
  • Notifying IMS session control events of a specific IMS subscriber to NFs.
    This service operation reports the event to the consumer that has subscribed implicitly via configuration in the IMS AS.
IMS AS processing of the session event is paused until the consumer acknowledges reception of the session event notification. The consumer is given the possibility to apply session media control and policies by invoking the Nimsas_MediaControl service before giving IMS AS a session event notification acknowledgement.
If the consumer does not apply media control/policies to a session event, IMS AS continues processing and forwards the event as is (including the media state) to calling/called party.
Up
AA.2.4.2.2  Nimsas_SessionEventControl_Notify service operationp. 351
Service operation name:
Nimsas_SessionEventControl_Notify
Description:
This service operation enables IMS AS to notify consumers of session events related to a specific served IMS subscriber requesting use of IMS data channel media.
Inputs, Required:
Session ID, Event ID,
Session ID is the identity of the IMS session for which the event relates to.
Event ID is the event triggered within the IMS session.
Inputs, Optional:
Calling ID, Called ID, Session case, Event initiator, Media info list.
Calling ID is the public identity of the calling IMS subscriber. Called ID is the public identity of the called IMS Subscriber. Session case indicates if this is an originating or terminating IMS session. Event initiator indicates initiator of the event, i.e. 'served IMS subscriber' vs 'remote IMS subscriber'. Media info list includes for each media in the list:
  • media ID: uniquely identifies this media item within the list. The identity is allocated by IMS AS,
  • media specification: This depends on media type including relevant media attributes of interest to the consumer. The media specification includes the following media description attributes:
    • Media Type: Data_Channel, Audio, or Video.
      When the media type is Data Channel, the elements below are derived from the SDP received by the IMS AS in an SIP INVITE or a re-INVITE related to an IMS Data Channel and the corresponding DTLS connection.
      • Data Channel Mapping and Configuration Information: This attribute is applicable to Data Channel and includes relevant configuration Information, including the stream ID of the Data Channel.
      • Maximum Message Size: This attribute defines the maximum size to be expected.
      • Data Channel Port: This attribute identifies the port for the Data Channel.
      • Security Setup: This attribute identifies the security set up of the DTLS connection.
      • Security Certificate Fingerprint: This attribute identifies the security certificate fingerprint.
      • Security Transport Identity: This attribute identifies transport layer identity.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
The Table below presents supported EventIDs and related parameters.
EventID Parameters
SessionEstablishmentRequestEventCalling ID, Called ID, Session case, Media info list
SessionEstablishmentProgressEventMedia info list
SessionEstablishmentAlertingEventMedia info list
SessionEstablishmentSuccessEventMedia info list
SessionEstablishmentFailureEvent
MediaChangeRequestEvent.Event initiator, Media info list
MediaChangeSuccessEventMedia info list
MediaChangeFailureEventMedia info list
SessionTerminationEventSession case
Up

AA.2.4.3  Nimsas_MediaControl Servicep. 352

AA.2.4.3.1  Generalp. 352
Service description:
This service enables the consumer to control IMS AS handling of media flow within an IMS session. The service can be used by the consumer before responding to a Nimsas_SessionEventControl_Notity request.
AA.2.4.3.2  Nimsas_MediaControl_MediaInstruction service operationp. 352
Service operation name:
Nimsas_MediaControl_MediaInstruction
Description:
This operation provides instructions to the IMS AS for all media flows a consumer wants to control based on its policies for the received IMS session event, and that may require resource reservation in media resource e.g. MF or MRF.
For the case when a specific media flow needs to be terminated in MF media resource (i.e. termination of a Data Channel media descriptor offered by one of the IMS subscribers) or originated by the MF or MRF (i.e. origination of a data channel media descriptor to be offered towards one of the IMS subscribers), the consumer must provide a complete MF media specification including information required by MF to know how to terminate or originate the media flow.
Inputs, Required:
Session ID, Media instruction set
Session ID specifies the IMS session for which the MediaInstruction operation applies.
Media instruction set includes a set of instructions for each media flow to control. Each instruction includes:
  • media ID: used by the producer (IMS AS) and the consumer for referencing purposes. The consumer reuses the media ID it received from the IMS AS for referencing the same media. This field will be null for instructions related to originating new media.
  • Media resource capability: Identify the Media Resource capabilities the Media instruction is intended for (e.g. DCMF, ARMF).
  • Media instruction: includes instructions to the producer (IMS AS) for handling the media. The following instructions are supported:
    • "TerminateMedia": Terminate the offered media descriptor of the UE in the mediaResource, i.e. this media descriptor will not be exposed to the other UE.
    • "OriginateMedia": Originate and offer a media descriptor from the mediaResource to the UE. The media ID representing the new media flow will be provided by the IMS AS in the response.
    • "TerminateAndOriginateMedia": Terminate the offered media flow in the mediaResource from the UE and originate the same media flow from the mediaResource to the other UE, i.e. the offered media descriptor of the originating UE will be replaced by the mediaResource provided media descriptor, which is sent towards the other UE.
    • "UpdateMedia": Update a media flow of the mediaResource previously allocated by the instructions "TerminateMedia", "OriginateMedia" and "TerminateAndOriginateMedia"
    • "DeleteMedia": Delete a media flow of the mediaResource previously allocated by the instructions "TerminateMedia", "OriginateMedia" and "TerminateAndOriginateMedia".
    • "RejectMedia": Remove an offered media flow, i.e. the offered media descriptor will be removed both from the offer sent to the remote UE and from the answer returned to the initiator of the offer.
  • DC Media Specification: Description of additional media specification information needed for data channel media stream from application layer, which includes:
    • Media proxy configuration (HTTP or UDP) applicable to the media flow.
    • MDC1/MDC2 media endpoint address of the application layer.
    • Replacement HTTP URL per stream ID allocated by the application layer representing the application list (e.g. graphical user interface) provided to the IMS subscriber via the MDC1 interface.
    • Data Channel Mapping and Configuration information when originating/terminating data channel media flows on the Mb interface.
  • AR Media Specification: Description of additional media specification information needed for AR communication services from application layer, which includes:
    • Media Processing Specification: It specifies the how the media stream should be processed.
Inputs, Conditional:
None.
Inputs, Optional:
None.
Outputs, Required:
operation result indication.
Outputs, Optional:
media resource information set:
This set includes entries corresponding to each instruction in the received media instruction set. Each entry in the set includes the media ID (same as received or new for new media) and includes the media type according to SDP. Each entry may optionally contain DC Media Specification and/or AR Media Specification. The DC Media Specification shall exist only with media type "DC" and contains additional media resource information, e.g. allocated media address for MDC2 interface when an offer must be provided to Data Channel Application Server. The AR Media Specification contains media processing instruction for MF on how to process the media.
Up

AA.2.5  MF Services |R18|p. 354

AA.2.5.1  Generalp. 354

The following Table illustrates the MF Services and Service Operations.
NF service Service Operations Operation Semantics Example Consumer(s)
Nmf_MediaResourceManagement (MRM)CreateRequest/ResponseIMS AS
UpdateRequest/ResponseIMS AS
DeleteRequest/ResponseIMS AS
Up

AA.2.5.2  Nmf_MediaResourceManagement (MRM) servicep. 354

AA.2.5.2.1  Generalp. 354
Service description:
This service enables the consumer to create, update and delete media resources related to IMS Data Channel.
The media resource represents a media context including one or multiple media terminations. A media termination includes media resources for one or multiple media streams on the Mb interface.
Each media stream is identified by a media ID.
Up
AA.2.5.2.2  Nmf_MRM_Create service operationp. 354
Service operation name:
Nmf_MRM_Create
Description:
The consumer NF requests the MF to create a media context including one or multiple media terminations and reserve media resources for one or multiple media streams of Mb interface in each termination. The consumer NF may also include media resource descriptions requested by the upper layer, e.g. DCSF, to be reserved on the MF.
Inputs, Required:
List of Media Termination Descriptors.
Each Media Termination Descriptor of the list includes:
  • List of Media Stream Descriptors belonging to the Termination.
Each Media Stream Descriptor of the list includes:
  • Media ID: A unique identity of the media stream within the media context instance. The MediaID value is set by the consumer.
  • Remote Mb Specification: Media Specification specifying SDP parameters of a media endpoint e.g. IP address and ports of the UE. This parameter is used to establish IMS DC or audio/video media path between MF and UE.
  • Media Specifications:
    • Media Type: Identify the media type the Media instruction is intended for (e.g. DC, AR).
If the Media Type is "DC":
  • DC Media Specification: Description of additional media specification information needed for data channel media stream from application layer, which includes:
    • Media proxy configuration (HTTP or UDP) applicable to the media flow.
    • MDC1/MDC2 media endpoint address.
    • Replacement HTTP URL per Stream ID allocated by the application layer representing the application list (e.g. graphical user interface) provided to the IMS subscriber via the MDC1 interface.
If the Media Type is "AR":
  • AR Media Specification: Description of additional media specification information needed for AR communication services from application layer, which includes:
    • Media Processing Specification: It specifies the how the media stream should be processed.
Inputs, Optional:
None.
Outputs, Required:
Result indication, Media Resource Context ID, List of allocated Media Termination Descriptor Resource information.
Media Resource Context ID uniquely identifies the media resources created by the MF. This identity shall be used as reference when updating or deleting the created media resource.
List of allocated Media Termination Descriptor Resource information includes one or multiple Media Termination Descriptor resources allocated. The list will include same number of terminations, in the same order as provided in the request.
Media Termination Descriptor Resource includes:
  • Termination ID: Unique identity allocated by the consumer. The identity shall be used when updating/deleting the Media Termination.
  • List of Media Stream Descriptor Resource information elements allocated within the media termination.
Media Stream Descriptor resource information includes:
  • Media ID: Unique identity of the media stream within the media context instance allocated by the consumer.
  • Local Mb Specification: Media specification specifying SDP parameters representing the media endpoint of the provider e.g. IP address and ports used in SDP response etc.
  • DC Media Resource Description: Optional application specific media resource specification specifying the information of data channel, which includes:
  • MF MDC1/MDC2 media point information (IP address/port number, etc.) which shall be relayed to the DCSF by the consumer NF.
Outputs, Optional:
None.
Up
AA.2.5.2.3  Nmf_MRM_Update service operationp. 356
Service operation name:
Nmf_MRM_Update
Description:
The consumer NF requests the MF to update one or multiple media resources within a specific media resource context. Terminations and/or Media Streams can be added, modified or deleted within an Update request.
Inputs, Required:
Media Resource Context ID, List of Media Termination Descriptors to be updated.
Media Resource Context ID specifies the media context resource to be updated.
List of Media Termination Descriptors includes one of multiple updated Media Stream Descriptors, which provides the media stream information that needs to be updated.
Inputs, Optional:
None.
Outputs, Required:
Result indication, List of Media Termination Descriptor Resource information.
List of Media Termination Descriptors includes one or multiple updated Media Stream Descriptors, which provides the media stream information that needs to be updated.
Outputs, Optional
None.
Up
AA.2.5.2.4  Nmf_MRM_Delete service operationp. 356
Service operation name:
Nmf_MRM_Delete
Description:
The consumer NF requests the MF to delete a specific media context resource including all existing terminations and media streams.
Inputs, Required:
Media Context Resource ID.
Media Context Resource ID specifies the media context resource to be deleted.
Inputs, Optional:
None.
Outputs, Required:
Result indication.
Outputs, Optional:
None.

Up   Top   ToC