8 Messages/Procedures and contents
23.3333GPPMultimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptionsRelease 17TS
8.1 General
This clause describes logical signalling procedures between the MRFC and MRFP. The procedures within this clause are intended to be implemented using the standard H.248 procedure as defined in ITU recommendation H.248.1 [3] with appropriate parameter combinations.
8.2 Send tone
This procedure is used to send a tone.
Table 8.2.1: Procedures between MRFC and MRFP: Send Tone
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Send Tone MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the tone is sent. |
||
Tone |
M |
This information element indicates the tone to be generated. |
||
Notify Tone Completion |
O |
This information element requests a notification of a completed tone. |
||
Tone Direction |
O |
This information element indicates the tone direction in the bearer termination. |
||
Tone Timing |
O |
This information element indicates the time for the tone. |
||
DTMF trigger |
O |
This information element indicates the MRFP to detect the DTMF and the MRFP should stop the tone when a DTMF digit is detected. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Send Tone Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.3 Stop tone
This procedure is used to stop the tone.
Table 8.3.1: Procedures between MRFC and MRFP: Stop Tone
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop Tone |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the tone is stopped. |
||
Stop Tone |
M |
This information element requests that tone generation is stopped. |
||
Stop Tone Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.4 Tone completed
This procedure is used to notify the completed tone.
Table 8.4.1: Procedures between MRFC and MRFP: Tone Completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Tone Completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the tone was completed. |
||
Tone Completed |
M |
This information element indicates completion of the tone. |
||
Cause |
M |
This information element indicates the cause of tone completion. |
||
Tone Completed Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.5 Start announcement
This procedure is used to request to start announcement.
Table 8.5.1: Procedures between MRFC and MRFP: Start announcement
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start announcement MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the announcement is sent. |
||
Announcement identifier |
M |
This information element indicates the announcement or announcement list to be played. |
||
Audio file format |
O |
This information element indicates the audio file type, such as the 3GPP file type. |
||
Direction |
O |
This information element indicates the announcement direction in the bearer termination. |
||
Iterations |
O |
This information element indicates the number of times the announcement shall be played |
||
Variable List |
O |
This information element indicates the variable or variable list to be played. |
||
Notify Announcement Completed |
O |
This information element requests a notification of a completed announcement. |
||
DTMF stop announcement |
O |
This information element indicates whether the MRFP should stop the announcement when a DTMF digit is detected. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start announcement Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.6 Stop Announcement
This procedure is used to stop the announcement.
Table 8.6.1: Procedures between MRFC and MRFP: Stop Announcement
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop Announcement |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the announcement is stopped. |
||
Stop Announcement |
M |
This information element requests that announcement playing is stopped. |
||
Stop Announcement Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.7 Announcement Completed
This procedure is used to notify the completed announcement.
Table 8.7.1: Procedures between MRFC and MRFP Announcement Completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Announcement Completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the announcement was completed. |
||
Announcement Completed |
M |
This information element indicates completion of the announcement. |
||
Cause |
M |
This information element indicates the cause of announcement completion. |
||
Announcement Completed Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.8 Start audio record
This procedure is used to start the audio record.
Table 8.8.1: Procedures between MRFC and MRFP: Start audio record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start audio record MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the audio is recorded. |
||
Record file Identifier |
M |
This information element indicates the record file Identifier or a request to the MRFP to create the record file Identifier. |
||
Record file Format |
O |
This information element indicates the audio record file format. |
||
Maximum Record Timer |
O |
This information element indicates the maximum allowable length of the recording |
||
Notify audio record Completed |
O |
This information element requests a notification of a completed audio record. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start audio record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
||
Record File identifier |
O |
This information element indicates the file identifier created by the MRFP if the MRFC request to create a file URI. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.9 Stop audio record
This procedure is used to stop the audio record.
Table 8.9.1: Procedures between MRFC and MRFP: Stop audio record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop audio record |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the audio record is stopped. |
||
Stop audio record |
M |
This information element requests that audio record is stopped. |
||
Stop audio record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.10 Audio record completed
This procedure is used to report the audio record completed.
Table 8.10.1: Procedures between MRFC and MRFP: Report audio record completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Audio Record Completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the audio record was completed. |
||
audio record Completed |
M |
This information element indicates the audio record completed. |
||
Cause |
M |
This information element indicates the return code of audio record. |
||
Audio record Completed Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.11 Detect DTMF
This procedure is used to request detection of a DTMF digit.
Table 8.11.1: Procedures between MRFC and MRFP: Detect DTMF
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Detect DTMF |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the DTMF digit detection is requested. |
||
Start_DTMF_Detection |
M |
This information element requests MRFP to detect a DTMF digit. |
||
Detect DTMF Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.12 Stop DTMF Detection
This procedure is used to stop detection of the DTMF digit.
Table 8.12.1: Procedures between MRFC and MRFP: Stop DTMF Detection
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop DTMF Detection |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the DTMF digit detection is stopped. |
||
Stop DTMF Detection |
M |
This information element requests that DTMF digit detection is stopped. |
||
Stop DTMF Detection Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.13 Report DTMF
This procedure is used to report a detected DTMF digit.
Table 8.13.1: Procedures between MRFP and MRFC: Report DTMF
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report DTMF |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the DTMF digit was detected. |
||
Digit |
M |
This information element reports the detected DTMF digit. |
||
Report DTMF Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.14 Start playing multimedia
This procedure is used to start playing multimedia.
Table 8.14.1: Procedures between MRFC and MRFP: start playing multimedia
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start playing multimedia MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the multimedia is sent. |
||
Multimedia identifier |
M |
This information element indicates the multimedia or list of multimedia to be played. This may be a single identifier or one identifier per media type. |
||
Multimedia file format |
O |
This information element indicates the multimedia file type, such as the 3GP file type. |
||
Iterations |
O |
This information element indicates the number of times the multimedia shall be played |
||
Direction |
O |
This information element indicates the direction of the multimedia to be sent. |
||
Notify multimedia completed |
O |
This information element requests a notification when the playing multimedia is completed. |
||
DTMF stop multimedia |
O |
This information element indicates the MRFP to detect the DTMF digits and stop the playing multimedia when a pre-defined DTMF digit is detected. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start playing multimedia Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.15 Stop playing multimedia
This procedure is used to stop playing multimedia.
Table 8.15.1: Procedures between MRFC and MRFP: Stop playing multimedia
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop playing multimedia |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Stop playing multimedia |
M |
This information element requests that multimedia playing is stopped. |
||
stop playing multimedia Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.16 Playing multimedia completed
This procedure is used to report the playing multimedia completed.
Table 8.16.1: Procedures between MRFC and MRFP: Report playing multimedia completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report playing multimedia completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Playing Completed |
M |
This information element indicates completed of the multimedia play. |
||
Cause |
M |
This information element indicates the return code of playing multimedia. |
||
Report playing multimedia completed ACK |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.17 Start multimedia record
This procedure is used to start the multimedia record.
Table 8.17.1: Procedures between MRFC and MRFP: Start multimedia record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start multimedia |
Record MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the multimedia is recorded. |
||
Multimedia file identifier |
M |
This information element indicates the multimedia record file identification or a request to the MRFP to create a file identifier. |
||
Multimedia file Format |
O |
This information element indicates the multimedia record file format. |
||
Maximum Record Timer |
O |
This information element indicates the maximum allowable length of the recording |
||
Notify multimedia record Completed |
O |
This information element requests a notification of a completed multimedia record. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start multimedia record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
||
File identifier |
O |
This information element indicates the file identification created by the MRFP if the MRFC request to create a file identifier. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.18 Stop multimedia record
This procedure is used to stop the multimedia record.
Table 8.18.1: Procedures between MRFC and MRFP: Stop multimedia record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop Multimedia Record |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Stop multimedia record |
M |
This information element requests that multimedia record is stopped. |
||
Stop Multimedia record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command is executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.19 Multimedia record completed
This procedure is used to report the multimedia record completed.
Table 8.19.1: Procedures between MRFC and MRFP: Report multimedia record completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report multimedia record completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Multimedia record Completed |
M |
This information element indicates the multimedia record completed. |
||
Cause |
M |
This information element indicates the return code of multimedia record. |
||
Report multimedia record completed ACK |
MRFC |
Context |
M |
This information element indicates the context where the command is executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.20 Reserve and Configure IMS Resources
This procedure is used to reserve multimedia-processing resources for an Mp interface connection; it is based on the procedure of the same name defined in 3GPP TS 29.163 [9].
Table 8.20.1: Procedures between MRFC and MRFP: Reserve and Configure IMS Resources
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Reserve and Configure IMS Resources |
MRFC |
Context/Context Request |
M |
This information element indicates the existing context or requests a new context for the bearer termination. |
Priority information |
O |
This information element requests the MRFP to apply priority treatment for the terminations and bearer connections in the specified context. |
||
IMSTermination Request |
M |
This information element indicates the existing bearer termination or requests a new IMS termination for the bearer to be established. |
||
Local IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
ReserveValue |
O |
This information element indicates if multiple local IMS resources are to be reserved |
||
Remote IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall send data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Local Connection Address Request |
M |
This information element requests an IP address and port number(s) on the MRFP that the remote end can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Remote Connection Address |
M |
This information element indicates the remote IP address and port number(s) that the MRFP can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Notify Released Bearer |
O |
This information element requests a notification of a released bearer. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. Otherwise the information element is optional. |
||
ECN Enable |
O |
This information element requests the MRFP to apply ECN. |
||
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the MRFP to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. |
||
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN related error occurs It may be included only if ECN is enabled.. |
||
Diffserv Code Point |
O |
This information element requests the MRFP to apply a specific Diffserv Code Point to the IP headers. |
||
Extended RTP Header for CVO |
O |
This information element requests the MRFP to pass on the CVO extended RTP header as defined by IETF RFC 5285 [27]. |
||
Generic Image Attributes |
O |
This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [28]. |
||
STUN server request |
O |
This information element is present if MRFC requests the MRFP to answer STUN connectivity checks for ICE. |
||
ICE Connectivity Check |
C |
This information element requests the MRFP to perform ICE connectivity check as defined by IETF RFC 5245 [29]. It is only applicable for full ICE. |
||
Notify ICE Connectivity Check Result |
C |
This information element requests the MRFP to perform ICE connectivity check as defined by IETF RFC 8445 [66]. It is only applicable for full ICE. |
||
ICE password request |
O |
This information element is present if MRFC requests an ICE password. |
||
ICE Ufrag request |
O |
This information element is present if MRFC requests an ICE ufrag. |
||
ICE host candidate request |
O |
This information element is present if MRFC requests an ICE host candidate. |
||
ICE pacing request |
O |
This information element is present if MRFC requests a pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
ICE received candidate |
O |
This information element is present if MRFC indicates a received candidate for ICE. |
||
ICE received password |
O |
This information element is present if MRFC indicates a received password for ICE. |
||
ICE received Ufrag |
O |
This information element is present if MRFC indicates a received Ufrag for ICE. |
||
ICE received pacing |
O |
This information element is present if MRFC indicates a received pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
MSRP URI Path request |
O |
This information element requests the MSRP URI path information that the MRFP will insert in the MSRP message "From‑Path" header field. |
||
MSRP URI Path |
O |
This information element provides the MSRP URI path information that the MRFP will insert in the MSRP message "To‑Path" header field. |
||
Establish TCP connection |
O |
This information element requests the MRFP to take a TCP client role and to initiate a TCP connection establishment. |
||
Notify TCP connection establishment Failure Event |
O |
This information element requests a notification if a TCP connection establishment failure occurs. |
||
Establish (D)TLS session |
O |
This information element requests the MRFP to take a (D)TLS client role and to initiate a (D)TLS session establishment. |
||
Notify (D)TLS session establishment Failure Event |
O |
This information element requests a notification if a (D)TLS session establishment failure occurs. |
||
Pre-Shared Key |
O |
This information element is present if the MRFC wants that the media is protected using TLS tunnel established with MIKEY-TICKET procedures. It indicates the Traffic-Encrypting key associated with the Crypto Session that shall be used in TLS handshake. |
||
Allowed RTCP APP message types |
O |
This information element is present if the MRFC allows the MRFP to send RTCP APP packets of the indicated types. The MRFP shall not send other RTCP APP packets. If the parameter is not supplied, the MRFP shall not send any RTCP APP packets. |
||
Local certificate fingerprint Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local certificate fingerprint. |
||
Remote certificate fingerprint |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote certificate fingerprint. |
||
Local SCTP Port Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local SCTP Port. |
||
Remote SCTP Port |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote SCTP port. |
||
SCTP Stream ID |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the the actual SCTP stream identifier to realize the CLUE data channel. |
||
Subprotocol ID |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the protocol "CLUE" to exchange via the data channel. |
||
Local max message size Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local max message size. |
||
Remote max message size |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote max message size. |
||
Extended RTP Header for Sent ROI |
O |
This information element requests the MRFP to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [27] and 3GPP TS 26.114 [23]. |
||
Predefined ROI Sent |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Predefined ROI Received |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Arbitrary ROI Sent |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
|||
Arbitrary ROI Received |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
|||
Notify CLUE Message Received Event |
O |
This information element requests a reporting of the received CLUE message. |
||
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
Additional Bandwidth Properties |
O |
This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [23]. |
||
CCM BASE |
O |
This information element indicates that the MRFP shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [61]) to the end user. |
||
MMCMH policy |
O |
This information element indicates that interconnection of video media streams with different stream identities (StreamIDs) is allowed in the context and that the MRFP shall handle incoming RTP media streams autonomously according to MMCMH policies defined in clause 5.11.3.5. |
||
Stream content |
O |
This information element indicates the content of the media stream as defined in IETF RFC 4796 [59]. |
||
Simulcast desc |
O |
This information element requests the MRFP to configure a termination with a simulcast capability. For the indicated media stream, it contains the list of simulcast RTP streams using the "a=simulcast" attribute defined IETF RFC 8853 [57]. |
||
Simulcast format |
O |
This information element indicates the identity and the format of the simulcast RTP stream using the "a=rid" attribute defined in IETF RFC 8851 [58]. |
||
CCM pause-resume |
O |
This information element requests the MRFP to apply "RTP-level pause and resume" procedures as defined in IETF RFC 7728 [62] and indicates to the MRFP which RTCP feedback "CCM PAUSE-RESUME" messages the MRFP may send to the end user. |
||
Autonomous request |
O |
This information element indicates whether the MRFP is allowed to autonomously send RTCP feedback CCM PAUSE and RESUME messages. |
||
Autonomous response |
O |
This information element indicates whether the MRFP is allowed to autonomously send response to a CCM PAUSE and RESUME requests i.e. RTCP feedback CCM PAUSED and REFUSED messages. |
||
Concurrent Codec Capabilities |
O |
This information element indicates the concurrent codec capabilities of an MMCMH conference participant in a compact representation using the "a=ccc_list" SDP attribute defined in 3GPP TS 26.114 [23]. |
||
DBI |
O |
This information element indicates that the MRFP shall be prepared to receive and is allowed to send, respectively, the RTCP feedback messages for "DBI" signalling (as defined in 3GPP TS 26.114 [23] clause 7.3.8). |
||
Reserve and Configure IMS Resources Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
IMSTermination |
M |
This information element indicates the Bearer Termination where the command was executed. |
||
Local IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Remote IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall send data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Local Connection Address |
M |
This information element indicates the IP address and port number(s) the MRFP shall receive user plane data from IMS. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Remote Connection Address |
M |
This information element indicates the remote IP address and port number(s) that the MRFP can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
ICE password |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the MRFP. |
||
ICE Ufrag |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the MRFP. |
||
ICE host candidate |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the MRFP. |
||
ICE pacing |
C |
This information element shall be present only if it was contained in the request. It indicates a desired pacing value for connectivity checks (Ta timer value). |
||
ICE lite indication |
C |
This information element shall be present only if an ICE host candidate request was contained in the request, and the MRFP supports ICE lite, but not full ICE. It indicates that the MRFP only supports ICE lite. |
||
MSRP URI Path |
C |
This information element may be present only if the MSRP URI Path request was contained in the request. This information element provides the MSRP URI path information that the MRFP will insert in the MSRP message "From‑Path" header field. |
||
Local certificate fingerprint |
C |
This information element may be present only if the Local certificate fingerprint Request was contained in the request. It indicates the local certificate fingerprint. |
||
Local SCTP Port |
C |
This information element may be present only if the Local SCTP Port Request was contained in the request. It indicates the local SCTP Port. |
||
SCTP Stream ID |
C |
This information element shall be present if it was contained in the request. It indicates the SCTP stream identifier that the MRFP used to realize the CLUE data channel. |
||
Subprotocol ID |
C |
This information element shall be present if it was contained in the request. It indicates the the protocol "CLUE" to exchange via the data channel. |
||
Local max message size |
C |
This information element may be present only if the Local max message size Request was contained in the request. It indicates the local max message size. |
||
SDPCapNeg configuration |
C |
This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
8.21 Reserve IMS Resources Procedure
This procedure is used to reserve local connection addresses and local resources in MRFP; it is based on the procedure of the same name defined in 3GPP TS 29.163 [9].
Table 8.21.1: Procedures between MRFC and MRFP: Reserve IMS Resources
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Reserve IMS Resources |
MRFC |
Context /Context Request |
M |
This information element indicates the existing context or requests a new context for the bearer termination. |
Priority information |
O |
This information element requests the MRFP to apply priority treatment for the terminations and bearer connections in the specified context. |
||
IMS Termination Request |
M |
This information element requests a new bearer termination |
||
Local IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
ReserveValue |
O |
This information element indicates if multiple local IMS resources are to be reserved. |
||
Local Connection Address Request |
M |
This information element requests an IP address and port number(s) on the MRFP that the remote end can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Notify Released Bearer |
O |
This information element requests a notification of a released bearer. |
||
Notify termination heartbeat |
M |
This information element requests termination heartbeat indications. |
||
ECN Enable |
O |
This information element requests the MRFP to apply ECN. |
||
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the MRFP to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. |
||
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN related error occurs. It may be included only if ECN is enabled. |
||
Diffserv Code Point |
O |
This information element requests the MRFP to apply a specific Diffserv Code Point to the IP headers. |
||
Extended RTP Header for CVO |
O |
This information element requests the MRFP to pass on the CVO extended RTP header as defined by IETF RFC 5285 [27]. |
||
Generic Image Attributes |
O |
This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [28]. |
||
ICE password request |
O |
This information element is present if MRFC requests an ICE password. |
||
ICE Ufrag request |
O |
This information element is present if MRFC requests an ICE ufrag. |
||
ICE host candidate request |
O |
This information element is present if MRFC requests an ICE host candidate. |
||
ICE pacing request |
O |
This information element is present if MRFC requests a pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
STUN server request |
O |
This information element is present if MRFC requests the MRFP to answer STUN connectivity checks for ICE. |
||
MSRP URI Path request |
O |
This information element requests the MSRP URI path information that the MRFP will insert in the MSRP message "From‑Path" header field. |
||
Notify TCP connection establishment Failure Event |
O |
This information element requests a notification if a TCP connection establishment failure occurs. |
||
Local certificate fingerprint Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local certificate fingerprint. |
||
Local SCTP Port Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local SCTP Port. |
||
SCTP Stream ID |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the the actual SCTP stream identifier to realize the CLUE data channel. |
||
Subprotocol ID |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the the protocol "CLUE" to exchange via the data channel. |
||
Local max message size Request |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It requests the MRFP to provide a local max message size. |
||
Extended RTP Header for Sent ROI |
O |
This information element requests the MRFP to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [27] and 3GPP TS 26.114 [23]. |
||
Predefined ROI Sent |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Predefined ROI Received |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Arbitrary ROI Sent |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
||
Arbitrary ROI Received |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
||
Notify CLUE Message Received Event |
O |
This information element requests a reporting of the received CLUE message. |
||
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
MMCMH policy |
O |
This information element indicates that interconnection of video media streams with different stream identities (StreamIDs) is allowed in the context and that the MRFP shall handle incoming RTP media streams autonomously according to MMCMH policies defined in clause 5.11.3.5. |
||
Stream content |
O |
This information element indicates the content of the media stream as defined in IETF RFC 4796 [59]. |
||
Simulcast desc |
O |
This information element requests the MRFP to configure a termination with a simulcast capability. For the indicated media stream, it contains the list of simulcast RTP streams using the "a=simulcast" attribute defined IETF RFC 8853 [57]. |
||
Simulcast format |
O |
This information element indicates the identity and the format of the simulcast RTP stream using the "a=rid" attribute defined in IETF RFC 8851 [58]. |
||
CCM pause-resume |
O |
This information element requests the MRFP to apply "RTP-level pause and resume" procedures as defined in IETF RFC 7728 [62] and indicates to the MRFP which RTCP feedback "CCM PAUSE-RESUME" messages the MRFP may send to the end user. |
||
Autonomous request |
O |
This information element indicates whether the MRFP is allowed to autonomously send RTCP feedback CCM PAUSE and RESUME messages. |
||
Autonomous response |
O |
This information element indicates whether the MRFP is allowed to autonomously send response to a CCM PAUSE and RESUME requests i.e. RTCP feedback CCM PAUSED and REFUSED messages. |
||
Reserve IMS Resources Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
||
Local IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Local Connection Address |
M |
This information element indicates the IP address and port number(s) the MRFP shall receive user plane data from IMS. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
ICE password |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the MRFP. |
||
ICE Ufrag |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the MRFP. |
||
ICE host candidate |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the MRFP. |
||
ICE pacing |
C |
This information element shall be present only if it was contained in the request. It indicates a desired pacing value for connectivity checks (Ta timer value). |
||
ICE lite indication |
C |
This information element shall be present only if an ICE host candidate request was contained in the request, and the MRFP supports ICE lite, but not full ICE. It indicates that the MRFP only supports ICE lite. |
||
MSRP URI Path |
C |
This information element may be present only if the MSRP URI Path request was contained in the request. This information element provides the MSRP URI path information that the MRFP will insert in the MSRP message "From‑Path" header field. |
||
Local certificate fingerprint |
C |
This information element may be present only if the Local certificate fingerprint Request was contained in the request. It indicates the local certificate fingerprint. |
||
Local SCTP Port |
C |
This information element may be present only if the Local SCTP Port Request was contained in the request. It indicates the local SCTP Port. |
||
SCTP Stream ID |
C |
This information element shall be present if it was contained in the request. It indicates the SCTP stream identifier that the MRFP used to realize the CLUE data channel. |
||
Subprotocol ID |
C |
This information element shall be present if it was contained in the request. It indicates the the protocol "CLUE" to exchange via the data channel. |
||
Local max message size |
C |
This information element may be present only if the Local max message size Request was contained in the request. It indicates the local max message size. |
||
SDPCapNeg configuration |
C |
This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
8.22 Configure IMS Resources Procedure
This procedure is used to select multimedia-processing resources for an Mp interface connection; it is based on the procedure of the same name defined in 3GPP TS 29.163 [9].
Table 8.22.1: Procedures between MRFC and MRFP: Configure IMS Resources Procedure
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Configure IMS Resources |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
IMS Termination |
M |
This information element indicates the existing bearer termination. |
||
Local IMS Resources |
O |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Remote IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall send data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Local Connection Address |
O |
This information element indicates the IP address and port number(s) on the MRFP that the IMS user can send user plane data to. For terminations supporting video any combination of video, audio and messaging may contain multiple addresses. |
||
Remote Connection Address |
M |
This information element indicates the remote IP address and port number(s) that the MRFP can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Notify termination heartbeat |
O |
This information element requests termination heartbeat indications. |
||
ECN Enable |
O |
This information element requests the MRFP to apply ECN procedures. |
||
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the MRFP to perform IP header settings as an ECN endpoint. It may be included if ECN is enabled. |
||
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN related error occurs. It may be included if ECN is enabled. |
||
Extended RTP Header for CVO |
O |
This information element requests the MRFP to pass on the CVO extended RTP header as defined by IETF RFC 5285 [27].. |
||
Generic Image Attributes |
O |
This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [28]. |
||
ICE Connectivity Check |
C |
This information element requests the MRFP to perform ICE connectivity check as defined by IETF RFC 8445 [66]. It is only applicable for full ICE. |
||
Notify ICE Connectivity Check Result |
C |
This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. |
||
Notify New Peer Reflexive Candidate |
C |
This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. |
||
Additional ICE Connectivity Check |
C |
This information element requests the MRFP to perform additional ICE connectivity check as defined by IETF RFC 8445 [66]. It is only applicable for full ICE. |
||
ICE received candidate |
O |
This information element is present if MRFC indicates a received candidate for ICE. |
||
ICE received password |
O |
This information element is present if MRFC indicates a received password for ICE. |
||
ICE received Ufrag |
O |
This information element is present if MRFC indicates a received Ufrag for ICE. |
||
ICE received pacing |
O |
This information element is present if MRFC indicates a received pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
MSRP URI Path |
O |
This information element provides the MSRP URI path information that the MRFP will insert in the MSRP message "To‑Path" header field. |
||
Establish TCP connection |
O |
This information element requests the MRFP to take a TCP client role and to initiate a TCP connection establishment. |
||
Notify TCP connection establishment Failure Event |
O |
This information element requests a notification if a TCP connection establishment failure occurs. |
||
Establish (D)TLS session |
O |
This information element requests the MRFP to take a (D)TLS client role and to initiate a (D)TLS session establishment. |
||
Notify (D)TLS session establishment Failure Event |
O |
This information element requests a notification if a (D)TLS session establishment failure occurs. |
||
Pre-Shared Key |
O |
This information element is present if the MRFC wants that the media is protected using TLS tunnel established with MIKEY-TICKET procedures. It indicates the Traffic-Encrypting key associated with the Crypto Session that shall be used in TLS handshake. |
||
Allowed RTCP APP message types |
O |
This information element is present if the MRFC allows the MRFP to send RTCP APP packets of the indicated types. The MRFP shall not send other RTCP APP packets. If the parameter is not supplied, the MRFP shall not send any RTCP APP packets. |
||
Extended RTP Header for Sent ROI |
O |
This information element requests the MRFP to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [27] and 3GPP TS 26.114 [23]. |
||
Predefined ROI Sent |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Predefined ROI Received |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Predefined ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [23]. |
||
Arbitrary ROI Sent |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-sending client, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
||
Arbitrary ROI Received |
O |
This information element requests the MRFP to support the RTCP feedback message capability for "Arbitrary ROI" type toward the ROI-receiving clients, expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [23]. |
||
Remote certificate fingerprint |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote certificate fingerprint. |
||
Remote sctp port |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote SCTP port. |
||
Remote max message size |
O |
This information element is present if the MRFC requests the MRFP to establish the CLUE data channel. It indicates the remote max message size. |
||
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
Additional Bandwidth Properties |
O |
This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [23]. |
||
CCM BASE |
O |
This information element indicates that the MRFP shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [61]) to the end user. |
||
Stream content |
O |
This information element indicates the content of the media stream as defined in IETF RFC 4796 [59]. |
||
Simulcast desc |
O |
This information element requests the MRFP to configure a termination with a simulcast capability. For the indicated media stream, it contains the list of simulcast RTP streams using the "a=simulcast" attribute defined IETF RFC 8853 [57]. |
||
Simulcast format |
O |
This information element indicates the identity and the format of the simulcast RTP stream using the "a=rid" attribute defined in IETF RFC 8851 [58]. |
||
CCM pause-resume |
O |
This information element requests the MRFP to apply "RTP-level pause and resume" procedures as defined in IETF RFC 7728 [62] and indicates to the MRFP which RTCP feedback "CCM PAUSE-RESUME" messages the MRFP may send to the end user. |
||
Autonomous request |
O |
This information element indicates whether the MRFP is allowed to autonomously send RTCP feedback CCM PAUSE and RESUME messages. |
||
Autonomous response |
O |
This information element indicates whether the MRFP is allowed to autonomously send response to a CCM PAUSE and RESUME requests i.e. RTCP feedback CCM PAUSED and REFUSED messages. |
||
Concurrent Codec Capabilities |
O |
This information element indicates the concurrent codec capabilities of an MMCMH conference participant in a compact representation using the "a=ccc_list" SDP attribute defined in 3GPP TS 26.114 [23]. |
||
DBI |
O |
This information element indicates that the MRFP shall be prepared to receive and is allowed to send, respectively, the RTCP feedback messages for "DBI" signalling (as defined in 3GPP TS 26.114 [23] clause 7.3.8). |
||
Configure IMS Resources Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
IMS Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
||
Local IMS Resources |
O |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall be prepared to receive user data For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Remote IMS Resources |
M |
This information element indicates the resource(s) (i.e. codecs) for which the MRFP shall send data. For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. |
||
Local Connection Address |
O |
This information element indicates the IP address and port number(s) on the MRFP that the IMS user can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
||
Remote Connection Address |
M |
This information element indicates the remote IP address and port number(s) that the MRFP can send user plane data to. For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. |
8.23 Release IMS Termination
This procedure is used to release a termination towards the IMS and free all related resources; it is based on the procedure of the same name defined in 3GPP TS 29.163 [9].
Table 8.23.1: Procedures between MRFC and MRFP: Release IMS Termination
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Release IMS Termination |
MRFC |
Context |
M |
This information element indicates the existing context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination to be released. |
||
Release IMS Termination Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.24 Start TTS
This procedure is used to request to start TTS.
Table 8.24.1: Procedures between MRFC and MRFP: Start TTS
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start TTS |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the TTS is sent. |
||
Direction |
O |
This information element indicates the direction of the TTS to be sent. |
||
Notify TTS Completed |
O |
This information element requests a notification of a completed TTS. |
||
DTMF stop TTS |
O |
This information element indicates the MRFP to detect the DTMF digits and stop the TTS when a pre-defined DTMF digit is detected. |
||
SSML |
M |
This information element indicates the text to be spoken as SSML script. |
||
Iterations |
O |
This information element indicates the number of times the TTS shall be played. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start TTS Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.25 Stop TTS
This procedure is used to stop TTS.
Table 8.25.1: Procedures between MRFC and MRFP: Stop TTS
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop TTS |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the TTS is stopped. |
||
Stop TTS |
M |
This information element requests that TTS is stopped. |
||
Stop TTS Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.26 TTS Completed
This procedure is used to report the TTS result.
Table 8.26.1: Procedures between MRFC and MRFP: TTS Completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
TTS Completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the TTS is requested. |
||
TTS Completed |
M |
This information element indicates completed of the TTS. |
||
Cause |
M |
This information element indicates the return code of TTS. |
||
TTS Completed Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.27 Start ASR
This procedure is used to request to start ASR.
Table 8.27.1: Procedures between MRFC and MRFP: Start ASR
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start ASR |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the ASR is requested. |
||
Recognition Mode |
O |
This information element indicates the recognition mode: Normal Recognition Mode, Hotword Recognition Mode. |
||
Notify ASR completion |
O |
This information element requests a notification of a completed ASR. |
||
DTMF stop ASR |
O |
This information element indicates the MRFP to detect the DTMF digits and stop the ASR when a pre-defined DTMF digit is detected. |
||
SRGS Grammar |
M |
This information element indicates the SRGS format grammar as script or URI. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start ASR Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.28 Stop ASR
This procedure is used to stop ASR.
Table 8.28.1: Procedures between MRFC and MRFP: Stop ASR
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop ASR |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the ASR is stopped. |
||
Stop ASR |
M |
This information element requests that ASR is stopped. |
||
Stop ASR Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.29 ASR completed
This procedure is used to report the ASR result.
Table 8.29.1: Procedures between MRFC and MRFP: ASR completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
ASR completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination where the ASR is requested. |
||
ASR Completed |
M |
This information element indicates completed of the ASR. |
||
Cause |
M |
This information element indicates the return code of ASR. |
||
Recognition Result |
O |
This information element reports the ASR result. |
||
Text Token |
O |
This information element indicates a text token correspond to tokens as defined by the SRGS grammar. The ASR may return multiple results. |
||
Result Interpretation |
O |
This information element indicates interpretation of application specific for each result. |
||
Confidence Score |
O |
This information indicates the quality of the input for each result. The confidence score is a number in the range from 0.0 to 1.0 inclusive. |
||
Input Time |
O |
This information indicates the time of the speech input for each result. |
||
ASR completed Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.30 MRFP Out-of-Service or Maintenance Locked
This procedure is used to indicate that the MRFP will go out of service or is maintenance locked.
Table 8.30.1: Procedures between MRFC and MRFP: MRFP Out-of-Service
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Out-of-Service |
MRFP |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
MRFP Out-of-Service Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.31 MRFP Communication Up
This procedure is used to indicate that the MRFP is back in service.
Table 8.31.1: Procedures between MRFC and MRFP: MRFP Communication Up
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Communication Up |
MRFP |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
MRFP Communication Up Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.32 MRFP Restoration
This procedure is used to indicate the MRFP failure or recovery.
Table 8.32.1: Procedures between MRFC and MRFP: MRFP Restoration
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Restoration |
MRFP |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for the service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
MRFP Restoration Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.33 MRFC Restoration
This procedure is used to indicate the MRFC failure or recovery.
Table 8.33.1: Procedures between MRFC and MRFP: MRFC Restoration
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFC Restoration |
MRFC |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for the service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
MRFC Restoration Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.34 MRFP Re-register
This procedure is used to re-register the MRFP.
Table 8.34.1: Procedures between MRFC and MRFP: MRFP Re-register
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Re-register |
MRFP |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for the service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
Protocol Version |
M |
This information element indicates the protocol version for Mp interface requested by the MRFP. |
||
Service Change Profile |
M |
This information element indicates the profile for the Mp interface requested by the MRFP. |
||
MRFP Re-register Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
||
Protocol Version |
O |
This information element indicates the protocol version for Mp interface supported by the MRFC. |
||
Service Change Profile |
O |
This information element indicates the profile for the Mp interface supported by the MRFC. |
8.35 MRFC Re-registration Ordered by MRFC
This procedure is used by the MRFC to request the MRFP to register itself.
Table 8.35.1: Procedures between MRFC and MRFP: MRFC Ordered Re-register
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFC Ordered Re- register |
MRFC |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for the service change. |
||
MRFC Address |
O |
This information element indicates the MRFC signalling address. |
||
MRFC Ordered Re- register Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.36 Audit Value
This procedure is used to audit values of different object(s).
Table 8.36.1: Procedures between MRFC and MRFP: Audit Value
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Audit Value |
MRFC |
Context |
M |
This information element indicates the context for the command. |
Bearer Termination |
M |
This information element indicates the bearer termination(s) for the command. |
||
Object(s) |
M |
This information element indicates the object(s) to be audited. |
||
Audit Value Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
||
Value(s) |
M |
This information element indicates the value(s) of the object(s). |
8.37 Audit Capability
This procedure is used to audit capabilities of different object(s).
Table 8.37.1: Procedures between MRFC and MRFP: Audit Capability
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Audit Capability |
MRFC |
Context |
M |
This information element indicates the context for the command. |
Bearer Termination |
M |
This information element indicates the bearer termination(s) for the command. |
||
Object(s) |
M |
This information element indicates the object(s) which capability is requested. |
||
Audit Capability Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
||
Capabilities(s) |
M |
This information element indicates the capabilities of the object(s). |
8.38 Capability Update
This procedure is used to indicate update of an object capability.
Table 8.38.1: Procedures between MRFC and MRFP: Capability Update
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Capability Update |
MRFP |
Context |
M |
This information element indicates the context for the command. |
Bearer Termination |
M |
This information element indicates the bearer termination(s) for the command. |
||
Reason |
M |
This information element indicates the reason for service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
Capability Update Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.39 MRFC Out of Service
This procedure is used to indicate that MRFC has gone out of service.
Table 8.39.1: Procedures between MRFC and MRFP: MRFC Out of Service
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFC Out of Service |
MRFC |
Context |
M |
This information element indicates the context for the command. |
Root Termination |
M |
This information element indicates the root termination for the command. |
||
Reason |
M |
This information element indicates the reason for the service change. |
||
Method |
M |
This information element indicates the method for service change. |
||
MRFC Out of Service Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Root Termination |
M |
This information element indicates the root termination where the command was executed. |
8.40 MRFP Resource Congestion Handling – Activate
This procedure is used to activate the congestion handling mechanism.
Table 8.40.1: Procedures between MRFC and MRFP: MRFP Resource Congestion Handling – Activate
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Resource Congestion Handling – Activate |
MRFC |
Context |
M |
This information element indicates that all context are applicable for the root termination. |
Root Termination |
M |
This information element indicates that root termination is where the congestion mechanism is activated. |
||
Congestion Activate |
M |
This information element requests to activate the congestion mechanism. |
||
MRFP Resource Congestion Handling – Activate Ack |
MRFP |
Context |
M |
This information element indicates that all context are where the command was executed. |
Root Termination |
M |
This information element indicates that root termination is where the command was executed. |
8.41 MRFP Resource Congestion Handling – Indication
This procedure is used to inform the MRFC that traffic restriction is advised.
Table 8.41.1: Procedures between MRFC and MRFP: MRFP Resource Congestion Handling – Indication
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
MRFP Resource Congestion Handling – Indication |
MRFP |
Context |
M |
This information element indicates all context are applicable for the root termination. |
Root Termination |
M |
This information element indicates that root termination is where the congestion mechanism was activated. |
||
Reduction |
M |
This information element indicates the load percentage to be reduced. |
||
MRFP Resource Congestion Handling – Indication Ack |
MRFC |
Context |
M |
This information element indicates all context are where the command was executed. |
Root Termination |
M |
This information element indicates that root termination is where the command was executed. |
8.42 Command Reject
This command is used to reject the received command request. It may be used as response to any of the procedures.
Table 8.42.1: Procedures between (G)MSC server and MGW: Command Reject
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Command Reject |
Both |
Context |
M |
This information element indicates the context where the command was rejected. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was rejected. |
||
Error |
M |
This information element indicates the error that caused command rejection. |
8.43 Termination heartbeat indication
This procedure is used to report indication of hanging termination.
Table 8.43.1: Procedures between MRFC and MRFP: Hanging termination indication
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Termination heartbeat indication |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which the termination heartbeat is reported. |
||
Termination heartbeat |
M |
Hanging Termination event, as defined in 3GPP TS 29.333 [16]. |
||
Termination heartbeat indication Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.44 Configure BFCP Termination
This procedure is used to configure a termination to support BFCP protocol
Table 8.44.1: Procedures between MRFC and MRFP: Configure BFCP Termination
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Configure BFCP Termination |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination or requests a new bearer termination. |
||
Local BFCP Connection Address Request |
M |
This information element requests an IP address and port number(s) on the MRFP to serve BFCP/TCP protocol |
||
Remote BFCP Connection Address |
M |
This information element indicates the remote IP address and port number(s) that the MRFP can send BFCP/TCP to. |
||
User Identifier |
M |
This information element indicates the user Identifier to identify the BFCP client when receiving BFCP requests. |
||
Available Floors |
M |
This information Element defines the list of Floor Ids that may be requested (via BFCP) to be used by the client represented by this termination. |
||
Establish TCP connection |
O |
This information element requests the MRFP to take a TCP client role and to initiate a TCP connection establishment. |
||
Notify TCP connection establishment Failure Event |
O |
This information element requests a notification if a TCP connection establishment failure occurs. |
||
Notify TLS session establishment Failure Event |
O |
This information element requests a notification if a TLS session establishment failure occurs. |
||
Pre-Shared Key |
O |
This information element is present if the MRFC wants that the media is protected using TLS tunnel established with MIKEY-TICKET procedures. It indicates the Traffic-Encrypting key associated with the Crypto Session that shall be used in TLS handshake. |
||
Configure BFCP Termination Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
||
NOTE: The above procedure may be combined with other procedures in ADD or MOD commands. |
8.45 Configure Conference For Floor Control
This procedure is used to configure or modify a conference for floor control and indicate the Floor policy for a conference.
Table 8.45.1: Procedures between MRFC and MRFP: Configure Conference For Floor Control
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Indicate Floor Policy |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Conference Identifier |
M |
This information element indicates the Identifier for the conference for BFCP purposes. |
||
Floor-Resource Associations |
M |
This information element indicates the resource associated with specific Floor Ids for the MRFP to identify the Floor(s) when receiving BFCP requests. |
||
Floor Control Algorithm |
M |
This information element indicates for a specific floor, the algorithm to be used in granting the Floor. |
||
Maximum Floor Holder Number |
M |
This information element indicates for a specific floor, the maximum number of users who can hold the same Floor at the same time. |
||
Indicate Floor Policy Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
NOTE: The above procedure applies to a context instead of a termination. The H.248v3 shall be supported. The procedure may be combined with other procedures in ADD or MOD commands. |
8.46 Designate Floor Chair
This procedure is used to designate a Floor Chair to a conference.
Table 8.46.1: Procedures between MRFC and MRFP: Designate Floor Chair
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Designate Floor Chair |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination. |
||
Floor Chair |
M |
This information element indicates that the termination represents a Floor Chair in accordance with BFCP [20]. |
||
Floor Controlled By Chair |
O |
This information element indicates the Floor(s) the Floor Chair controls. |
||
Designate Floor Chair Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.47 Floor Request Decision
This procedure is used to request the MRFP to report the Floor request decision.
Table 8.47.1: Procedures between MRFC and MRFP: Floor Request Decision
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Floor Request Decision |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination. |
||
Notify Floor Request Decision |
M |
This information element requests MRFP to notify the decision of the FCS to Floor requests. |
||
Floor Request Decision Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.48 Report Floor Request Decision
This procedure is used to report the Floor request status .
Table 8.48.1: Procedures between MRFP and MRFC: Report Floor Request Decision
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report Floor Request Decision |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination to which the Floor request is associated. |
||
Floor Request Status |
M |
This information element reports the Floor Id or Floor Ids to which the Floor Request is associated and the Floor request status of specific Floor or Floors.. |
||
Report Floor Request Decision Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.49 Confirm Media Update
This procedure is used to indicate whether the media properties associated with a Floor Request have been modified successfully or not..
Table 8.49.1: Procedures between MRFC and MRFP: Confirm Media Update
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Confirm Media Update |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination to which the floor request is associated. |
||
Floor Request Status |
M |
This information element indicates the Floor Id or Ids and requested status to which the Confirm Media Result applies.. |
||
Result |
M |
This information element indicates whether the media properties associated with a Floor Request have been modified successfully or not. |
||
Confirm Media Update Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.50 Configure Granted Quota
This procedure is used to configure the granted quota.
Table 8.50.1: Procedures between MRFC and MRFP: Configure Granted Quota
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Configure Granted Quota |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination to configure the granted quotas. |
||
Quota for number of messages sent |
O |
This information element indicates the quota for the number of messages sent. |
||
Quota for number of messages received |
O |
This information element indicates the quota for the number of messages received. |
||
Quota for volume of messages sent |
O |
This information element indicates the quota for the volume of messages sent. |
||
Quota for volume of messages received |
O |
This information element indicates the quota for the volume of messages received. |
||
Valid Time |
O |
This information element indicates the valid time for collecting message statistics, upon expiry the MRFP shall report the current message statistics. |
||
Configure Granted Quota Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.51 Report Message Statistics
This procedure is used to report statistics for the sent and received messages.
Table 8.51.1: Procedures between MRFP and MRFC: Report Message Statistics
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report Message Statistics |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination to report statistics. |
||
Number of messages sent |
O |
This information element indicates the number of messages sent. |
||
Number of messages received |
O |
This information element indicates the number of messages received. |
||
Volume of messages sent |
O |
This information element indicates the volume of messages sent. |
||
Volume of messages received |
O |
This information element indicates the volume of messages received. |
||
Reason For Report |
M |
Indicates reason for the report (e.g. expiry of time, granted quotas reached) |
||
Report Message Statistics Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
8.52 Configure Filtering Rules
This procedure is used to configure the filtering rules.
Table 8.52.1: Procedures between MRFC and MRFP: Configure Filtering Rules
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Configure Filtering Rules |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination to config the filtering rules. |
||
Sender address |
O |
This information element indicates the filtering criteria of sender address. |
||
Message size |
O |
This information element indicates the filtering criteria of message size. |
||
Message content type |
O |
This information element indicates the filtering criteria of message content type. |
||
Message content format |
O |
This information element indicates the filtering criteria of message content format. |
||
Message subject |
O |
This information element indicates the filtering criteria of message subject. |
||
Message treatment |
O |
This information element indicates to the MRFP the message treatment when the filtering criteria is reached. The message treatment can be: Block the delivery of the message content. Store the message content Redirect the message to another address. |
||
Store URL |
O |
This information element indicates the store URL. |
||
Redirect URL |
O |
This information element indicates the redirect URL. |
||
Configure Filtering Rules Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the Bearer Termination where the command was executed. |
||
Store URL |
O |
This information element indicates the store URL. |
8.53 Start message record
This procedure is used to start the message record.
Table 8.53.1: Procedures between MRFC and MRFP: Start message record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start message Record |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the message is recorded. |
||
Message file identifier |
M |
This information element indicates the message record file identification. The MRFC may also request the MRFP to create file identifier. |
||
Maximum Record Timer |
O |
This information element indicates the maximum allowable length of time of the recording |
||
Notify message record Completed |
O |
This information element requests a notification of a completed message record. |
||
Start message record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
||
File identifier |
O |
This information element indicates the file identification created by the MRFP if the MRFC request to create a file identifier. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.54 Stop message record
This procedure is used to stop the message record.
Table 8.54.1: Procedures between MRFC and MRFP: Stop message record
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop Message Record |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Stop message record |
M |
This information element requests that message record is stopped. |
||
Stop Message record Ack |
MRFP |
Context |
M |
This information element indicates the context where the command is executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.55 Message record completed
This procedure is used to report the message record completed.
Table 8.55.1: Procedures between MRFC and MRFP: Report message record completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report message record completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Message record Completed |
M |
This information element indicates the message record completed. |
||
Cause |
M |
This information element indicates the return code of message record. |
||
Report message record completed ACK |
MRFC |
Context |
M |
This information element indicates the context where the command is executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.56 Start playing message
This procedure is used to start playing message.
Table 8.56.1: Procedures between MRFC and MRFP: start playing message
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Start playing message |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination/Bearer Termination Request |
M |
This information element indicates the existing bearer termination or requests a new bearer termination where the message is sent. |
||
Message identifier |
M |
This information element indicates the message or list of message to be played. This may be a single identifier or one identifier per media type. |
||
Direction |
O |
This information element indicates the direction of the message to be sent. |
||
Notify message completed |
O |
This information element requests a notification when the playing message is completed. |
||
Notify termination heartbeat |
C |
This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. |
||
Start playing message Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
NOTE This procedure may be combined with other procedures such as to ADD bearer connections.
8.57 Stop playing message
This procedure is used to stop playing message.
Table 8.57.1: Procedures between MRFC and MRFP: Stop playing message
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Stop playing message |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Stop playing message |
M |
This information element requests that message playing is stopped. |
||
Stop playing message Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.58 Playing message completed
This procedure is used to report the playing message completed.
Table 8.58.1: Procedures between MRFC and MRFP: Report playing message completed
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Report playing message completed |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
Playing Completed |
M |
This information element indicates completed of the message play. |
||
Cause |
M |
This information element indicates the return code of playing message. |
||
Report playing message completed ACK |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.59 Modify Media
This procedure is used to modify the media and stream properties for a given Floor Request (as indicated by the Report Floor Request Decision, Clause 8.48).
Table 8.59.1: Procedures between MRFC and MRFP: Modify Media
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
Modify Media |
MRFC |
Context |
M |
This information element indicates the existing context for the bearer termination or requests a new context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination to which the floor request is associated. |
||
Stream |
M |
This information element indicates the existing stream to which the floor request is associated |
||
Stream Mode |
M |
Stream mode properties associated to the floor request. |
||
Media Properties |
M |
Media properties associated to the floor request |
||
Modify Media Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.60 ECN Failure Indication
This procedure is used to indicate an ECN related Error.
Table 8.60.1: Procedures between MRFC and MRFP: ECN Failure indication
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
ECN Failure Indication |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the existing bearer termination. |
||
ECN Failure Indication |
M |
This information element indicates an ECN failure event. |
||
ECN Failure Indication ACK |
MRFC |
Context |
M |
This information element indicates the context where the command is executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.61 ICE Connectivity Check Result Notification
This procedure is used to report ICE connectivity check result for Full ICE (see clause 6.2.18.3).
Table 8.61.1: Procedures between MRFC and MRFP: ICE Connectivity Check Result Notification
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
ICE Connectivity Check Result Notification |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. |
||
ICE Connectivity Check Result |
M |
This information element indicates an ICE Connectivity Check Result event. |
||
ICE Connectivity Check Result Notification Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.62 ICE New Peer Reflexive Candidate Notification
This procedure is used to report ICE new peer reflexive candidate for Full ICE (see clause 6.2.18.4).
Table 8.62.1: Procedures between MRFC and MRFP: ICE New Peer Reflexive Candidate Notification
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
ICE New Peer Reflexive Candidate Notification |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported. |
||
ICE New Peer Reflexive Candidate |
M |
This information element indicates an ICE New Peer Reflexive Candidate event. |
||
ICE New Peer Reflexive Candidate Notification Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.63 Notify TCP connection establishment Failure Indication
This procedure is used to report TCP connection establishment failures.
Table 8.63.1: Procedures between MRFC and MRFP: TCP connection establishment Failure Indication
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
TCP connection establishment Failure Indication |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which a TCP connection establishment failure is reported. |
||
TCP connection establishment Error Indication |
M |
This information element indicates a TCP connection establishment failure event. |
||
TCP connection establishment Failure Indication Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.64 Notify TLS session establishment Failure Indication
This procedure is used to report TLS session establishment failures.
Table 8.64.1: Procedures between MRFC and MRFP: TLS session establishment Failure Indication
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
TLS session establishment Failure Indication |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which a TLS session establishment failure is reported. |
||
TLS session establishment Error Indication |
M |
This information element indicates a TLS session establishment failure event. |
||
TLS session establishment Failure Indication Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
8.65 CLUE Message Send
This procedure is used in a telepresence session by the MRFC to request the MRFP to send a CLUE message (see clause 6.2.21.2).
Table 8.65.1: Procedures between MRFC and MRFP: CLUE Message Send
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
CLUE Message Send |
MRFC |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which the CLUE information is reported. |
||
CLUE Message Content |
M |
This information element indicates the CLUE message content to send. |
||
CLUE Message Send Ack |
MRFP |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
8.66 CLUE Message Received Notification
This procedure is used in a telepresence session by the MRFP to report the received CLUE message to the MRFC (see clause 6.2.21.2).
Table 8.66.1: Procedures between MRFC and MRFP: CLUE Message Received Notification
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
CLUE Message Received Notification |
MRFP |
Context |
M |
This information element indicates the context for the bearer termination. |
Bearer Termination |
M |
This information element indicates the bearer termination for which the CLUE information is reported. |
||
CLUE Message Content |
M |
This information element indicates a content of the received CLUE message. |
||
CLUE Message Received Notification Ack |
MRFC |
Context |
M |
This information element indicates the context where the command was executed. |
Bearer Termination |
M |
This information element indicates the bearer termination where the command is executed. |
Annex A (informative): Change history
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New |
2006-05 |
CT4#31 |
Draft Skeleton |
0.1.0 |
||||
2006-07 |
CT4#31 |
Approval of the ad-hoc meeting TDs: C4-060934, C4-060935, C4-060938, C4-060939, C4-060940, C4-060963, C4-060964, C4-060965, C4-060966, C4-060967, C4-060968. |
0.2.0 |
||||
2006-09 |
CT4#32 |
Approval of the meeting TDs: C4-061324,C4-061474,C4-601475,C4-061476, C4-061477,C4-061478 |
0.3.0 |
||||
2006-11 |
CT4#33 |
Approval of the meeting TDs: C4-061797, C4-061798, C4-061799, C4-061801, C4-061802, C4-061804, C4-061805, C4-061806, C4-061594,C4-061646 |
0.4.0 |
||||
2006-11 |
Sent to CT#34 information |
1.0.0 |
|||||
2007-02 |
CT4#34 |
Approval of the meeting TDs: C4-070282, C4-070285, C4-070357, C4-070246, C4-070290, C4-070056, C4-070291, C4070358 |
1.1.0 |
||||
2007-03 |
CT#35 |
CP-070037 |
Sent to CT#35 for approval |
2.0.0 |
|||
2007-03 |
CT#35 |
CP-070261 |
Chapter numbering corrected |
2.1.0 |
|||
2007-03 |
CT#35 |
Approved as v7.0.0 |
7.0.0 |
||||
2007-06 |
CT#36 |
CP-070472 |
0002 |
1 |
Clarify the TTS requirement |
7.1.0 |
|
CP-070472 |
0003 |
3 |
Alignment of procedures and normative text |
||||
CP-070472 |
0005 |
5 |
Clarify ASR function requirement |
||||
CP-070324 |
0004 |
1 |
Correction to DTMF handling |
||||
CP-070324 |
0007 |
1 |
Multimedia Play |
||||
CP-070324 |
0010 |
1 |
Remove editor notes |
||||
CP-070324 |
0011 |
1 |
Correction of Play Announcement |
||||
CP-070324 |
0012 |
1 |
Addition of Non-call Related procedures to chapter 8 |
||||
2007-09 |
CT#37 |
CP-070539 |
0013 |
1 |
Remove option to signal max number of participants in conference |
7.2.0 |
|
CP-070539 |
0014 |
2 |
Removal of floor control functions |
||||
CP-070539 |
0015 |
2 |
Correction of stop audio and multimedia record procedures |
||||
CP-070539 |
0017 |
2 |
Clarify recording requirement and procedure |
||||
2007-12 |
CT#38 |
CP-070745 |
0020 |
Maximum Number of Participants in a conference |
7.3.0 |
||
CP-070745 |
0021 |
Clarification of Topology Handling During a Recording |
|||||
CP-070745 |
0022 |
Amend iterations parameter in start TTS procedure |
|||||
CP-070745 |
0023 |
Clarification of record file storage |
|||||
CP-070745 |
0024 |
1 |
Clean-up of hanging contexts and terminations |
||||
CP-070745 |
0025 |
Eliminate the duplicate definitions on the ASR completion scenario |
|||||
CP-070745 |
0027 |
1 |
Implementation of multiple signals played simultaneously |
||||
CP-070745 |
0028 |
1 |
Clarification of the connection address and port |
||||
2008-03 |
CT#39 |
CP-080021 |
0030 |
1 |
Introduction of support for Messaging on Mp Interface |
8.0.0 |
|
CP-080017 |
0031 |
1 |
Alignment of IMS resources procedures’ title |
||||
CP-080021 |
0032 |
Mandatory use termination heartbeat |
|||||
CP-080021 |
0034 |
2 |
Clarify floor control requirement |
||||
2008-03 |
CT#39 |
Corrupted table structure fixed in tables: 8.17.1, 8.20.1, 8.21.1, 8.22.1, 8.24.1, 8.27.1 by MCC |
8.0.1 |
||||
2008-06 |
CT#40 |
CP-080263 |
0035 |
1 |
Clarify messaging conference requirements |
8.1.0 |
|
CP-080263 |
0038 |
1 |
Clarify floor control requirements and procedures |
||||
CP-080263 |
0039 |
1 |
Introduction of procedure for Messaging Conference |
||||
2008-09 |
CT#41 |
CP-080465 |
0041 |
2 |
Clarification of message storage requirement and procedure |
8.2.0 |
|
CP-080465 |
0042 |
2 |
Clarification of playing messaging requirement and procedure |
||||
CP-080465 |
0044 |
1 |
Improvement of Floor control procedures |
||||
2008-12 |
CT#42 |
CP-080694 |
0045 |
Remove Editor’s Note on Message File Format |
8.3.0 |
||
2009-12 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
|
2010-12 |
CT#50 |
CP-100685 |
0048 |
3 |
Support of ECN |
10.0.0 |
|
2011-03 |
CT#51 |
CP-110058 |
0049 |
2 |
ECN Support in Mp Interface |
10.1.0 |
|
2011-06 |
CT#52 |
CP-110368 |
0050 |
1 |
Adding ECN IEs to Connection Point procedures |
10.2.0 |
|
2011-12 |
CT#54 |
CP-110789 |
0051 |
1 |
ECN Improvements |
10.3.0 |
|
2012-06 |
CT#56 |
CP-120226 |
0055 |
1 |
Reference update: draft-ietf-avtcore-ecn-for-rtp |
10.4.0 |
|
2012-11 |
Change history table corrected |
11.0.1 |
|||||
2012-12 |
CT#58 |
CP-120723 |
0059 |
– |
Reference update: RFC 6679 |
11.1.0 |
|
CP-120734 |
0060 |
1 |
Additional Text for Support of Multimedia Priority Service (MPS) over Mp Interface |
||||
2013-09 |
CT#61 |
CP-130452 |
0061 |
3 |
Introduction of support for Coordination of Video Orientation (CVO) |
12.0.0 |
|
0062 |
3 |
Introduction of support for Generic Image Attribute/signalling of image size |
|||||
2013-12 |
CT#62 |
CP-130619 |
0063 |
2 |
CVO handling in MRF |
12.1.0 |
|
CP-130619 |
0067 |
1 |
Correction of CVO description |
||||
CP-130636 |
0064 |
1 |
Usage of generic image attributes |
||||
CP-130636 |
0068 |
1 |
Correction of Image Size description |
||||
2014-06 |
CT#64 |
CP-140248 |
0069 |
2 |
ICE support for MRF in Mp interface |
12.2.0 |
|
2014-09 |
CT#65 |
CP-140504 |
0070 |
2 |
Mp requirements for e2e media security |
12.3.0 |
|
2014-12 |
CT#66 |
CP-140786 |
0074 |
1 |
Generic procedure to support session based messaging (MSRP) |
12.4.0 |
|
CP-140786 |
0075 |
1 |
TCP bearer connection control |
||||
CP-140786 |
0076 |
1 |
E2e media security procedures for TCP based media (MSRP, BFCP) using TLS and KMS |
||||
CP-140788 |
0077 |
2 |
Adding support for EVS codec |
||||
2015-03 |
CT#67 |
CP-150030 |
0078 |
1 |
TLS session renegotiation on the Mp interface |
12.5.0 |
|
CP-150026 |
0079 |
3 |
Support of CLUE bearer level signalling |
||||
CP-150026 |
0080 |
2 |
CLUE carriage over Mp interface |
||||
2015-06 |
CT#68 |
CP-150259 |
0081 |
1 |
EVS corrections |
12.6.0 |
|
CP-150260 |
0082 |
2 |
Bearer Termination in ICE Acknowledgements |
||||
CP-150255 |
0083 |
1 |
IETF Updates on IMS Telepresenc |
||||
CP-150258 |
0084 |
– |
3GPP TLS profile reference |
||||
2015-12 |
CT#70 |
CP-150755 |
0088 |
3 |
Reference update: IETF drafts |
12.7.0 |
|
2015-12 |
CT#70 |
CP-150786 |
0086 |
6 |
Support of SDP capability negotiation |
13.0.0 |
|
CP-150783 |
0087 |
6 |
Support for Video Enhancements by Region-of-Interest Information Signalling |
||||
2016-03 |
CT#71 |
CP-160015 |
0093 |
1 |
Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling |
13.1.0 |
|
CP-160048 |
0090 |
1 |
Removal of references to TS 26.235 |
||||
CP-160034 |
0091 |
1 |
Support of enhanced bandwidth negotiation mechanism for MTSI sessions |
||||
2016-06 |
CT#72 |
CP-160229 |
0094 |
– |
Rate adaptation clarification |
13.2.0 |
|
2016-06 |
CT#72 |
CP-160229 |
0095 |
– |
Clarifications related to the rate adaptation for media endpoints |
13.2.0 |
|
2016-07 |
Version number number corrected |
13.2.1 |
|||||
2016-12 |
CT#74 |
CP-160647 |
0098 |
1 |
Handling of dtx and dtx-recv MIME parameters in SDP offer/answer |
13.3.0 |
|
2016-12 |
CT#74 |
CP-160684 |
0096 |
2 |
Support of multi-party multimedia conference using simulcast |
14.0.0 |
|
2017-03 |
CT#75 |
CP-170023 |
0106 |
– |
RFC 4572 obsoleted by draft-ietf-mmusic-4572-update |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170051 |
0101 |
3 |
MMCMH conference establishment procedure |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170051 |
0102 |
2 |
MMCMH "dial-out" conference establishment requirements |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170051 |
0103 |
2 |
Including new MMCMH related IEs in procedures in clause 8 |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170033 |
0107 |
– |
Correcting reference identity for RFC 6714 |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170051 |
0104 |
2 |
MMCMH Updates |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170051 |
0108 |
1 |
RTCP Codec Control Commands and Indications |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171015 |
0110 |
– |
Reference update: RFC 8122 |
14.2.0 |
|
2017-06 |
CT#76 |
CP-171013 |
0110 |
– |
Reference update: draft-ietf-clue-datachannel |
14.2.0 |
|
2017-06 |
CT#76 |
CP-171037 |
0114 |
2 |
Support of "Compact Concurrent Codec Negotiation and Capabilities" |
14.2.0 |
|
2017-06 |
CT#76 |
CP-171014 |
0117 |
– |
Reference update: draft-ietf-mmusic-sctp-sdp |
14.2.0 |
|
2017-06 |
CT#76 |
CP-171037 |
0118 |
– |
Reference update: MMCMH related IETF drafts |
14.2.0 |
|
2017-06 |
CT#76 |
CP-171037 |
0119 |
1 |
Removal IE for voice activity detection and "MMCMH policies" clarification |
14.2.0 |
|
2017-12 |
CT#78 |
CP-173014 |
0121 |
– |
Reference update: draft-ietf-mmusic-dtls-sdp |
14.3.0 |
|
2018-06 |
CT#80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2019-06 |
CT#84 |
CP-191053 |
0122 |
2 |
Update Mp interface procedures for DBI |
16.0.0 |
|
2020-12 |
CT#90e |
CP-203024 |
0128 |
– |
Reference update: telepresence related IETF drafts |
16.1.0 |
|
2020-12 |
CT#90e |
CP-203025 |
0131 |
– |
Reference update: MMCMH related IETF drafts |
16.1.0 |
|
2021-03 |
CT#91e |
CP-210064 |
0136 |
– |
Reference update: RFC 8841, RFC 8850 and RFC 8864 |
16.2.0 |
|
2021-03 |
CT#91e |
CP-210065 |
0140 |
– |
Reference update: RFC 8842 |
16.2.0 |
|
2021-03 |
CT#91e |
CP-210067 |
0143 |
– |
Reference update: RFC 8851 and RFC 8853 |
16.2.0 |
|
2021-12 |
CT#94e |
CP-213104 |
0144 |
– |
B |
Alignment with SA3 supported TLS profiles |
17.0.0 |
2022-03 |
CT#95e |
CP-220052 |
0145 |
1 |
B |
Update of IETF references for ICE |
17.1.0 |