Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4   5…   5A…   6…   7…   7A…   8…   9…   10…   11…   12…   12.2…   12.3…   12.4…   12.5…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…   B…   C…   D…   E…   F…   G…   H…   I…   J…   L…

 

11  IMS Conference Services |R8|

11.1  Background for IMS Conference Services

The entire clause 11 is a national option and is subject to national regulations. The covered cases are where the conference services are in the domain of the intercepting operator. The following cases are covered.
  1. A target's conference call is the target. This may be where the target is the head of the conference. IRI and CC for this conference is reported. The following are examples of information that is reported.
    1. For example, the starting and ending of a conference as well as any parties joined or removed from the conference call are reported.
    2. Reporting of CC for held conferences initiated by the target.
  2. A conference that itself is directly the target of interception. This case is applicable only provided that the conference is identified by a proper identity for LI in IMS domain (Conference URI or Conference Factory URI). The IRI and CC for this conference is reported.
    1. For example, the starting and ending or a conference as well as any parties joined or removed from the conference call are reported.
The case when an target joins an associate's conference is for further study.
The key elements for interception of conference services are the AS/MRFC and MRFP. IRI associated with the conference services that are to be intercepted is reported by the AS/MRFC while the CC associated with the conference service is reported by the MRFP.
National regulations on a per interception basis may limit delivery of communications (CC and IRI) of an outbound international roaming target by the HPLMN as described in clause 5.1.4 of TS 33.106.
If roaming interception is not allowed and it is determined that the target is outside the country, the HPLMN shall act as follows:
  • The HPLMN shall not report IRI and CC for the target's conferencing services while the target is in the VPLMN and is connected to the HPLMN conferencing service.
Non-communications-associated IRI (e.g. those identified by the HSS) are not affected by this requirement.
Up

11.1A  Start of Interception for IMS Conference Services |R9|Word‑p. 104
Interception (as defined in 11.1) for IMS Conference Services is started when the first of any one of the following occurs:
  • When a target requests that a conference be created
  • When a target successfully provisions a conference
  • When a target provisioned or requested conference is started (i.e., the first party is joined to the conference)
  • When a conference that is a target of interception is started (i.e., the first party is joined to the conference)
  • When interception is activated (on a conference or a conference owner) during an ongoing conference
  • When parties have joined a conference and communication is started or enabled by the conference server in cases where the conference is a target of interception or when it is a target's conference.
If the target of interception has provisioned or requested a conference to be created, interception on IMS Conference Services shall begin regardless whether the target of interception has joined the conference. Interception of IMS Conference Services shall continue if the target of interception is on hold and the conference continues.
Up

11.2  Provision of Intercepted Content of Communication - IMS Conference Services

11.2.0  General |R12|

The access method for the delivery of IMS conference services intercept content of communication (CC) is based on duplication of packets without modification at the MRFP for conferences that are to be intercepted. The duplicated packets with additional information in the header, as described in the following sections, are sent to DF3 for further delivery. For a target's conference call held by the target, the MRFP duplicates the CC for conference call held by the target, in accordance with national regulations. For a conference call that is the target of interception, the MRFP duplicates the CC for the conference.
There is an issue of combined versus separated delivery. With combined delivery, one method for intercepting the CC would be to create a virtual conference port (not visible to others) through which a copy of the combined CC is passed over the X3 interface (Y conferees means 1 content stream). With the separated delivery approach, each conferee's connection to the conference shall be intercepted and passed over the X3 interface (Y conferees, means Y pairs of bi-directional content streams).
[not reproduced yet]
Figure 11.1: Configuration for interception of IMS Conference Services CC
Up

11.2.1  X3-interfaceWord‑p. 105
In addition to the intercepted content of communications, the following information may need to be transferred from the MRFP to the DF3 in order to allow the DF3 to perform its functionality:
  • identity used for interception;
  • correlation number.
Information passed between the MRFC and MRFP for correlation shall uniquely identify the mixing of associated media streams for a conference distinct from any other mixing or media handling. An example is how H.248 uses a context identifier to do this.
  • the identity of source (i.e., conference party identity) of a media stream;
  • time stamp - optional;
  • direction (incoming or outgoing stream) - optional.
Up

11.3  Provision of Intercept Related Information for IMS Conference Service

11.3.0  General |R12|

Figure 11.2 shows the transfer of intercept related information to the DF2. If an event for / from or associated with a conference server occurs, the AS/MRFC sends the relevant data to the DF2.
[not reproduced yet]
Figure 11.2: Provision of Intercept Related Information for IMS Conferencing
Up

11.3.1  X2-interfaceWord‑p. 106
The following information may need to be transferred from the AS/MRFC to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMPU, IMPI, Conference URI);
  • events and associated parameters as defined in section 11.3.3 "Structure of Conference Events" may be provided;
  • Correlation number;
  • Bandwidth and media descriptions (e.g., as associated with SDP negotiation) associated with the parties' bearer connection to the conference.
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

11.3.2  IMS Conference Events and Event Information

The following events are applicable to AS/MRFC:
  • Start of Conference
  • Party Join;
  • Party Leave;
  • Conference Bearer Modification;
  • Start of Intercept on an Active Conference;
  • End of Conference;
  • Creation of Conference;
  • Update of Conference.
A set of possible elements as shown below that may be reported with the events. Information associated with the events is transmitted from the AS/MRFC server to DF2.
Element
Description

Observed IMPU
IMS Public User identity (IMPU) of the target. In some cases, this identity may not be observed by the MRFC. Also see Note 1.
Observed IMPI
IMS Private User identity (IMPI) of the target. In some cases, this identity may not be observed by the MRFC. Also see Note 1.
Observed Other Identity
Target Identifier with the NAI of the target.
Event Type
Description which type of event is delivered: Start of Conference, Party Join, Party Leave, Start of Intercept on an Active Conference, Conference End.
Event Date
Date of the event generation in the AS/MRFC.
Event Time
Time of the event generation in the AS/MRFC server. Timestamp shall be generated relative to the AS/MRFC internal clock.
Correlation Number
The correlation number is used to correlate CC and IRI. The correlation number is also used to allow the correlation of IRI records.
Network Element Identifier
Unique identifier for the element reporting the ICE.
Initiator
The initiator of a request, for example, the target, the network, a conferee.
Join Party ID
Identity of the party successfully joining or attempting to join the conference.
Leave Party ID
Identity of the party leaving or being requested to leave the conference.
List of Potential Conferees
Identifies each of the parties to be invited to a conference or permitted to join the conference (if available).
Observed Conference URI
A URI associated with the conference being monitored.
Temporary Conference URI
A temporarily allocated URI associated with a conference being monitored.
List of Conferees
Identifies each of the conferees currently on a conference (e.g., via SIP URI or TEL URI).
Failed Conference Start Reason
Provides a reason for why a conference start attempt failed.
Failed Party Join Reason
Provides a reason for why a party join attempt failed.
Party Leave Reason
Provides a reason for the party leaving.
Failed Party Leave reason
Provides a reason for why a party leave attempt failed.
Conference End Reason
Provides a reason for why the conference ended.
Potential Conference Start Date and Time
The expected start date and time of the conference, if start time information is configured in the system.
Potential Conference End Date and Time
The expected end date and time of the conference, if such end information is configured in the system.
Recurrence Information
Information indicating the recurrence pattern for the event as configured for the created conference.
Identity(ies) of Conference Controller
Identifies the parties that have control privileges on the conference, if such information is configured in the system.
Bearer Modify ID
Identifies the party modifying a conference bearer.
Failed Bearer Modify Reason
Provides a reason for a bearer modification attempt failed.
Failed Conference End Reason
Provides a reason why a conference end attempt failed.
Join Party Supported Bearers
Identifies the bearer types supported by the party joining the conference.
List of Waiting Conferees
Identifies each of the parties that have called into a conference but have not yet joined.
Media Modification
Identifies how the media was modified (i.e., added, removed, changed)
Parties Affected by Bearer Modification
Identifies all conference party identities affected by the bearer modification.
Supported Bearers
Identifies all bearer types supported by a conferee in a conference.
Update Type
Indicates what update was done to a conference (e.g., update List of Potential Conferees, update of Start Time, update of End Time, Update of Recurrence Information, Cancellation of Conference, etc.).

Up

11.3.3  Structure of Conference EventsWord‑p. 109

11.3.3.1  Start of Conference

For the start of a conference, a Start of Conference-event is generated in the following cases:
  • When a target provisioned or requested conference or a conference that is the target of interception is started. The conference is started when the first party is joined to the conference.;
  • When a conference that is a target of interception or when a target provisioned or requested conference fails to start.
The fields, shown in Table 11.3.2, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
List of Potential Conferees
List of Conferees
List of Waiting Conferees
Supported Bearers
Observed Conference URI
Temporary Conference URI
Failed Conference Start Reason

Up

11.3.3.2  Party Join

A Party Join-event is generated in the following cases:
  • When a party successfully joins the target's conference or a conference that is the target of interception.
  • When a party unsuccessfully attempts to join the target's conference or a conference that is the target of interception.
The fields, shown in Table 11.3.3, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
Join Party ID
Join Party Supported Bearers
Initiator (of the Party Join request)
Observed Conference URI
Temporary Conference URI
Failed Party Join Reason (e.g., not available)

Up

11.3.3.3  Party LeaveWord‑p. 110
A Party Leave-event is generated in the following cases:
  • When a party leaves a target's conference or a conference that is the target of interception. This includes situations where the party simply disconnects themselves from the conference (hang up), the party's connection to the conference is broken (e.g., party leaves wireless coverage area), and where the party's connection to the conference is forcefully terminated due to another party's drop request or operator policy.
  • When a party unsuccessfully attempts to drop another party from the conference. This applies to all the conferencing scenarios described earlier.
The fields, shown in Table 11.3.4, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
Leave Party ID
Supported Bearers (of Leaving Party)
Initiator (of the Party Leave request)
Observed Conference URI
Temporary Conference URI
Party Leave Reason - see Note.
Failed Party Leave Reason

Up

11.3.3.3A  Conference Bearer Modification

A Conference Bearer Modification-event is generated for the following cases:
  • When a party to a conference successfully modifies (i.e., add, remove, change) a bearer stream in the conference;
  • When a party to a conference unsuccessfully attempts to modify (i.e., add, remove, change) a bearer stream in the conference.
The fields, shown in Table 11.3.4A, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
Observed Conference URI
Temporary Conference URI
Bearer Modify ID
Media Modification
Parties Affected by Bearer Modification
Failed Bearer Modify Reason

Up

11.3.3.4  Start of Intercept on an Active ConferenceWord‑p. 111
A Start of Intercept on an Active Conference-event (a conference with at least one party) is generated for the following cases:
  • When interception is activated during an ongoing conference call.
The fields, shown in Table 11.3.5, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
List of Conferees
Supported Bearers
Observed Conference URI
Temporary Conference URI

11.3.3.5  Conference End

When a conference is terminated, a Conference End-event is generated in the following cases:
  • When a target provisioned or requested conference is terminated. This occurs when the last party on the conference leaves or the conference is terminated by the conference server;
  • When there is an unsuccessful attempt to terminate a target provisioned or requested conference or a conference that is the target of interception.
The fields, shown in Table 11.3.6, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Event Type
Event Time
Event Date
Network Element Identifier
Correlation Number
Initiator (e.g., target, network, conferee) - see Note
Observed Conference URI
Temporary Conference URI
Conference End Reason
Failed Conference End Reason

Up

11.3.3.6  Creation of ConferenceWord‑p. 112
When a conference is created, a Creation of Conference-event is generated in the following cases:
  • When a target successfully provisions or requests a conference to be created.
This event is applicable provided that at least one of the two identities (IMPU, IMPI) are available at the AS/MRFC. Other scenarios, such as in case the creation is done via a web interface and the IMPU/IMPI cannot be seen are outside the scope of this specification.
The fields, shown in Table 11.3.7, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Observed Other Identity
Event Type
Event Time
Event Date
Network Element Identifier
List of Potential Conferees (if available)
Observed Conference URI
Temporary Conference URI
Potential Conference Start Date and Time (if available) - See Note 1
Potential Conference End Date and Time (if available) - See Note 1
Recurrence Information - See Note 2.
Identity(ies) of Conference Controller

Up

11.3.3.7  Update of Conference

When a conference is updated, an Update of Conference-event is generated in the following cases:
  • When a target successfully provisions or requests a conference to be updated (e.g., changes to List of Potential Conferees, Start Time, End Time, Recurrence Information, or Cancellation of Conference).
This event is applicable provided that at least one of the two identities (IMPU, IMPI) are available at the AS/MRFC. Other scenarios, such as in case the update is done via a web interface and the IMPU/IMPI cannot be seen are outside the scope of this specification.
The fields, shown in Table 11.3.8, will be delivered to the DF2, if available, by the AS/MRFC.
Information Element

Observed IMPU
Observed IMPI
Observed Other Identity
Event Type
Event Time
Event Date
Network Element Identifier
Update Type
List of Potential Conferees (if available)
Observed Conference URI
Temporary Conference URI
Potential Conference Start Date and Time (if available) - See Note 1
Potential Conference End Date and Time (if available) - See Note 1
Recurrence Information - See Note 2.
Identity(ies) of Conference Controller

Up


Up   Top   ToC