11 3GPP IMS Conference Services
33.1083G Security3GPPHandover interface for Lawful Interception (LI)Release 17TS
11.1 Identifiers
11.1.1 Overview
Specific identifiers are necessary to identify a target for interception uniquely and to correlate between the data, which is conveyed over the different handover interfaces (HI2 and HI3). The identifiers are defined in the subsections below.
For the delivery of CC, the MRFP provides correlation numbers and target identities to the HI3. The AS/MRFC reports the IRI associated with the conference services.
For the delivery of CC and IRI, the AS/MRFC/MRFP provides correlation numbers and target identities to the HI2 and HI3. For a given target the correlation number is unique per conference session.
NOTE: If two or more target identities are involved in the same conference session the same Correlation Number may be assigned by the relevant network element to the communication sessions of the different target identities.
11.1.2 Lawful interception identifier
For each target identity related to an interception measure, the authorized operator (NO/AN/SP) shall assign a special Lawful Interception Identifier (LIID), which has been agreed between the LEA and the operator (NO/AN/SP).
Using an indirect identification, pointing to a target identity makes it easier to keep the knowledge about a specific target limited within the authorized operator (NO/AN/SP) and the handling agents at the LEA.
The LIID is a component of the CC delivery procedure and of the IRI records. It shall be used within any information exchanged at the handover interfaces HI2 and HI3 for identification and correlation purposes.
The LIID format shall consist of alphanumeric characters. It might for example, among other information, contain a lawful authorization reference number, and the date, when the lawful authorization was issued.
The authorized operator (NO/AN/SP) shall either enter, based on an agreement with each LEA, a unique LIID for each target identity of the target or a single LIID for multiple target identities all pertaining to the same target.
If more than one LEA intercepts the same target identity, there shall be unique LIIDs assigned relating to each LEA.
Note that, in order to simplify the use of the LIID at LEMF for the purpose of correlating IMS signalling with GSN CC, the use of a single LIID in association with potentially numerous IMS identities (SIP and TEL URIs) is recommended.
In case the LIID of a given target has different values in the GSN and in the CSCF, it is up to the LEMF to recover the association between the two LIIDs.
11.1.3 Network identifier
The network identifier (NID) is a mandatory parameter; it should be internationally unique. It consists of the following two identifiers.
1) Operator- (NO/AN/SP) identifier (mandatory):
Unique identification of network operator, access network provider or service provider.
2) Network element identifier NEID (optional):
The purpose of the network element identifier is to uniquely identify the relevant network element carrying out the LI operations, such as LI activation, IRI record sending, etc.
A network element identifier may be an IP address or other identifier. National regulations may mandate the sending of the NEID.
11.1.4 Correlation number
For a given target the Correlation Number is unique per conference session and used for the following purposes:
– correlate CC with IRI,
– correlate different IRI records within one conference session.
NOTE: The Correlation Number is at a minimum unique for each concurrent communication of a target within a lawful authorization.
11.2 Timing and quality
11.2.1 Timing
As a general principle, within a telecommunication system, IRI, if buffered, should be buffered for as short a time as possible.
NOTE: If the transmission of IRI fails, it may be buffered or lost.
Subject to national requirements, the following timing requirements shall be supported:
– Each IRI data record shall be sent by the delivery function to the LEMF over the HI2 within seconds of the detection of the triggering event by the IAP at least 95% of the time.
– Each IRI data record shall contain a time-stamp, based on the intercepting node’s clock that is generated following the detection of the IRI triggering event.
11.2.2 Quality
The quality of service associated with the result of interception should be (at least) equal to the highest quality of service of the original content of communication for all participants. This may be derived from the QoS class used for the original intercepted session, TS 23.107 [20]. However, when TCP is used as an OSI layer 4 protocol across the HI3, real time delivery of the result of the interception cannot be guaranteed. The QoS used from the operator (NO/AN/SP) to the LEMF is determined by what operators (NO/AN/SP) and law enforcement agree upon.
11.2.3 Void
(Void)
11.3 Security aspects
Security is defined by national requirements.
11.4 Quantitative aspects
The number of target interceptions supported is a national requirement.
The area of Quantitative Aspects addresses the ability to perform multiple, simultaneous interceptions within a provider’s network and at each of the relevant intercept access points within the network. Specifics related to this topic include:
– The ability to access and monitor all simultaneous communications originated, received, or redirected by the target;
– The ability for multiple LEAs (up to five) to monitor, simultaneously, the same target while maintaining unobtrusiveness, including between agencies;
– The ability of the network to simultaneously support a number of separate (i.e. multiple targets) legally authorized interceptions within its service area(s), including different levels of authorization for each interception (i.e. IRI only, or IRI and communication content), including between agencies.
11.5 IRI for IMS Conference Services
11.5.0 Introduction
The IRI will in principle be available in the following phases of a conference service transmission:
1) At a conference creation, when the target successfully provisions or requests that a conference is created;
2) At the start of a conference, when the first party is joined to the conference; the conference may be provisioned or requested by the target or the conference is the target of interception;
3) At the end of a conference, when the last party on the conference leaves or the conference is terminated by the conference server; the conference may be provisioned or requested by the target or the conference is the target;
4) At certain times when relevant information are available.
The IRI may be subdivided into the following categories:
1. Control information for HI2 (e.g. correlation information);
2. Basic data communication information, for standard data transmission between two parties.
The events defined in TS 33.107 [19] are used to generate records for the delivery via HI2.
There are multiple different event types received at DF2 level. According to each event, a Record is sent to the LEMF if this is required. The following table gives the mapping between event type received at DF2 level and record type sent to the LEMF.
Table 11.1: Mapping between IMS Conference Service Events and HI2 records type
|
Event |
IRI Record Type |
|
Start of Conference (successful) |
BEGIN |
|
Start of Intercept with Conference Active |
BEGIN |
|
Conference Service Party Join |
CONTINUE |
|
Conference Service Party Leave |
CONTINUE |
|
Conference Service Bearer Modify |
CONTINUE |
|
Conference Service End (unsuccessful) |
CONTINUE |
|
Conference Service End (successful) |
END |
|
Start of Conference (unsuccessful) |
REPORT |
|
Conference Service Creation |
REPORT |
|
Conference Service Update |
REPORT |
A set of information is used to generate the records. The records used transmit the information from mediation function to LEMF. This set of information can be extended in the ICE or DF2 MF, if this is necessary in a specific country. The following table gives the mapping between information received per event and information sent in records.
Table 11.2: Mapping between Events information and IRI information
|
Parameter |
description |
HI2 ASN.1 parameter |
|---|---|---|
|
Bearer Modify ID |
Identity of the party modifying or attempting to modify a media bearer |
bearerModifyPartyID (partyIdentity) |
|
Conference End Reason |
Provides a reason for why the conference ended. |
confEndReason |
|
Conference URI |
A URI associated with the conference being monitored. |
confID |
|
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. |
confCorrelation |
|
Event Date |
Date of the event generation in the AS/MRFC. |
timestamp |
|
Event Time |
Time of the event generation in the AS/MRFC server. Timestamp shall be based on the AS/MRFC internal clock. |
|
|
Event Type |
Description which type of event is delivered: Start of Conference, Party Join, Party Leave, Bearer Modify, Start of Intercept on an Active Conference, Conference End |
confEvent |
|
Failed Bearer Modify Reason |
Provides a reason for why a bearer modification attempt failed |
confEventFailureReason |
|
Failed Conference End Reason |
Provides a reason for why a conference end attempt failed |
confEventFailureReason |
|
Failed Conference Start Reason |
Provides a reason for why a conference start attempt failed. |
confEventFailureReason |
|
Failed Party Join Reason |
Provides a reason for why a party join attempt failed. |
confEventFailureReason |
|
Failed Party Leave Reason |
Provides a reason for why a party leave attempt failed. |
confEventFailureReason |
|
Identity(ies) of Conference Controller |
Identifies the parties that have control privileges on the conference, if such information is configured in the system. |
confControllerID (partyIdentity) |
|
Initiator |
The initiator of a request, for example, the target, the network, a conferee. |
confEventInitiator |
|
Join Party ID |
Identity of the party successfully joining or attempting to join the conference. |
joinPartyID (partyIdentity) |
|
Join Party Supported Bearers |
Identity of bearer types supported by the party successfully joining the conference |
confPartyInformation (supportedmedia) |
|
Leave Party ID |
Identity of the party leaving or being requested to leave the conference. |
leavePartyID (partyIdentity) |
|
List of Conferees |
Identifies each of the conferees currently on a conference (e.g. via SIP URI or TEL URI). |
confPartyInformation (partyIdentity) |
|
List of Potential Conferees |
Identifies each of the parties to be invited to a conference or permitted to join the conference (if available). |
listOfPotConferees (partyIdentity) |
|
List of Waiting Conferees |
Identifies each of the conferees awaiting to join a conference (e.g. called in to a conference that has not yet started) |
listOfWaitConferees (partyIdentity) |
|
Media Modification |
Identifies how the media was modified (i.e., added, removed, or changed) and the value for the media |
mediaModification |
|
Network Identifier |
Operator ID plus ICE address. This is an unique identifier for the element reporting the ICE. |
networkIdentifer |
|
Lawful Interception identifier |
Unique number for each lawful authorization. |
lawfulInterceptionIdentifier |
|
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. |
partyInformation (partyIdentity) |
|
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. |
partyInformation (partyIdentity) |
|
Observed Other Identity |
Target identifier with the NAI of the target. |
partyInformation (partyIdentity) |
|
Party Leave Reason |
Provides a reason for why a party left the conference |
reason |
|
Party(ies) Affected by Bearer Modification |
The list of parties affected by a media bearer modification |
confPartyInformation (partyIdentity) |
|
Potential Conference End Time |
The expected end time of the conference, if such end information is configured in the system. |
potConfEndInfo (timestamp) |
|
Potential Conference Start Time |
The expected start time of the conference, if start time information is configured in the system. |
potConfStartInfo (timestamp) |
|
Recurrence Information |
Information indicating the recurrence pattern for the event as configured for the created conference. |
RecurrenceInfo |
|
Supported Bearers |
Provides all bearer types supported by a conferee in a conference |
confPartyInformation (supportedmedia) |
|
Temporary Conference URI |
A temporarily allocated URI associated with a conference being monitored. |
tempConfID |
NOTE 1: In most cases, either the IMPU or IMPI may be available, but not necessarily both.
NOTE 2: LIID parameter has to be present in each record sent to the LEMF.
11.5.1 Events and information
11.5.1.1 Overview
This clause describes the information sent from the Delivery Function (DF) to the Law Enforcement Monitoring Facility (LEMF) to support Lawful Interception (LI). The information is described as records and information carried by a record. This focus is on describing the information being transferred to the LEMF.
The IRI events and data are encoded into records as defined in the Table 11.1 Mapping between Conference Service Events and HI2 records type and Annex B.11 Intercept related information (HI2). IRI is described in terms of a ‘causing event’ and information associated with that event. Within each IRI record there is a set of events and associated information elements to support the particular service.
The communication events described in Table 11.1: Mapping between Conference Service Events and HI2 record type and Table 11.2: Mapping between Events information and IRI information convey the basic information for reporting the disposition of a communication. This clause describes those events and supporting information.
Each record described in this clause consists of a set of parameters. Each parameter is either:
mandatory (M) – required for the record,
conditional (C) – required in situations where a condition is met (the condition is given in the Description), or
optional (O) – provided at the discretion of the implementation.
The information to be carried by each parameter is identified. Both optional and conditional parameters are considered to be OPTIONAL syntactically in ASN.1 Stage 3 descriptions. The Stage 2 inclusion takes precedence over Stage 3 syntax.
11.5.1.2 BEGIN record information
The BEGIN record is used to convey the first event of conference service communication interception.
The BEGIN record shall be triggered when:
– a target provisioned or requested conference is started (i.e., when the first party is joined to the conference, or when the first party accesses the conference but has to wait for a conference host/owner/chairman to join);
– a conference that is the target is started (i.e., when the first party is joined to the conference, or when the first party accesses the conference but has to wait for a conference host/owner/chairman to join);
– an interception is activated during an on-going conference call.
Table 11.3: Conference Service Start (Successful) BEGIN Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide Conference event type (i.e., Conference Start). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
list of potential conferees |
C |
Provide, when available, the party identities that are invited or permitted to join the conference. |
|
list of conferees |
C |
Provide at least one when available; provide the party identities on the current conference and/or party identities of those who have accessed the conference. See Note |
|
list of waiting conferees |
||
|
supported bearers |
C |
For each conferee, provide all bearers that are actively supported in this conference |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
NOTE: List of Waiting Conferees is only reported if the conference service allows party members to access a conference but they do not receive conference media.
Table 11.4: Start of Intercept with Conference Active BEGIN Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide Conference event type (i.e., Intercept Start with Active Conference). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
list of conferees |
M |
Provide the party identities on the current conference. |
|
supported bearers |
M |
For each conferee, provide all bearers that are actively supported in this conference |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
When the AS/MRFC is not aware of the activation of multiple lawfully authorized intercepts on an on-going conference call of a single target, the MF/DF shall generate the BEGIN record with Start of Intercept with Conference Active on its own using information that it has retained.
When the BEGIN-record is used to convey the start of interception on an on-going conference, the DF2 shall not send the Start of Intercept with Conference Active BEGIN record to the LEMFs that were already intercepting the conference due previous LI activation on the same target or conference.
11.5.1.3 CONTINUE record information
The CONTINUE record is used to convey the events during an active conference.
The CONTINUE record shall be triggered when:
– a party successfully joins the target’s conference or a conference that is the target;
– a party unsuccessfully attempts to join the target’s conference or a conference that is the target;
– a party successfully leaves (e.g. normal disconnection or involuntary termination/removal) a target’s conference or a conference that is a target;
– a party unsuccessfully attempts to drop another party from the target’s conference or a conference that is the target;
– a party successfully modifies (e.g. adds, removes, changes) media in the conference;
– a party unsuccessfully manages modifies (e.g. adds, removes, changes) media in the conference;
– there was an unsuccessful attempt to terminate a target provisioned or requested conference;
– there was an unsuccessful attempt to terminate a conference that is the target.
In order to enable the LEMF to correlate the information on HI3, a new correlation number shall not be generated within a CONTINUE record.
NOTE: Reporting of participant signalling to manage conference features (e.g. (un)mute) is for further study.
Table 11.5: Conference Service Party Join (successful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Party Join). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
join party ID |
M |
Provide the identity of the party joining the conference. |
|
initiator (of party join request) |
C |
Provide if different from join party ID. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance. |
|
temporary conference URI |
||
|
join party supported bearers |
M |
Provide all bearers that the party joining the conference supports. |
Table 11.6: Conference Service Party Join (unsuccessful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Party Join). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
join party ID |
M |
Provide the identity of the party attempting to join the conference. |
|
initiator (of party join request) |
C |
Provide if different from join party ID. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
failed party join reason |
M |
Provide information about the reason the attempted party join failed. |
Table 11.7: Conference Service Party Leave (successful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Party Leave). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
leave party ID |
M |
Provide the identity of the party leaving the conference or the identity of the party dropped from the conference |
|
initiator (of party leave request) |
C |
Provide if different from leave party ID |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
party leave reason |
M |
Provide information about the cause of the party leave (e.g. party hang up, party drop, or removed by conference controller) |
|
supported bearers |
M |
Provide all bearers that the party leaving the conference supported. |
Table 11.8: Conference Service Party Leave (unsuccessful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Party Leave). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
leave party ID |
M |
Provide the identity of the party attempting to leave the conference or the identity of the party that was requested to be dropped from the conference. |
|
initiator (of party leave request) |
C |
Provide if different from leave party ID. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
failed party leave reason |
M |
Provide information about the reason the conference party leave or dropped failed. |
Table 11.9: Conference Service Bearer Modify (successful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Bearer Modify). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
bearer modify ID |
M |
Provide the identity of the party modifying a bearer. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
media modification |
M |
Provide information about bearer modification (i.e., add, remove, change) and value of media. |
|
Parties affected by bearer modification |
M |
Provide the party identities of those conferees affected by the bearer modification. |
Table 11.10: Conference Service Bearer Modify (unsuccessful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide conference event type (i.e., Bearer Modify). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
bearer modify ID |
M |
Provide the identity of the party who attempted the action |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
media modification |
M |
Provide information about the attempt to modify a bearer (i.e., add, remove, change) and value of media. |
|
failed bearer modify reason |
M |
Provide information about the reason for failed bearer modification. |
Table 11.11: Conference Service End (unsuccessful) CONTINUE Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide Conference event type (i.e., Conference End). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
initiator (of conference end request) |
M |
Provide information on the initiator of the conference end (e.g,, target, network, conferee). |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance. |
|
temporary conference URI |
||
|
failed conference end reason |
M |
Provide information about the reason for the failed conference end. |
11.5.1.4 END record information
The END record is used to convey the last event of a conference service communication.
The END record shall be triggered when:
– a target provisioned or requested conference is terminated;
– a conference that is the target is terminated;
Table 11.12: Conference Service End (successful) END Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide Conference event type (i.e., Conference End). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
initiator (of a conference end request) |
M |
Provide information on the initiator of the conference end (e.g,, target, network, conferee). |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance. |
|
temporary conference URI |
||
|
conference end reason |
M |
Provide information about the reason for the conference end (e.g. expiration of time limit; party termination command, last user left conference). |
11.5.1.5 REPORT record information
The REPORT record is used to report non-communication related subscriber actions (events) and for reporting creations and updates of provisioned (e.g. future) conferences.
The REPORT record shall be triggered when:
– a target successfully provisions or requests that a conference be created;
– a target successfully provisions or requests that a conference be updated (e.g. modify or delete);
– a target provisioned or requested conference fails to start (e.g. no parties join the conference);
– a conference that is the target fails to start (e.g. no parties join the conference).
Table 11.13: Conference Service Start (Unsuccessful) REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
event type |
M |
Provide Conference event type (i.e., Conference Start). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
correlation number |
C |
Provide to allow correlation of CC and IRI and correlation of IRI records. |
|
list of potential conferees |
C |
Provide, when available, the party identities that are invited or permitted to join the conference. |
|
list of waiting conferees |
C |
Provide, when available, the known party identities of those parties awaiting to join the conference. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
failed conference start reason |
M |
Provide information about the reason for a failure of a conference start. |
Table 11.14: Conference Service Creation REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
observed other identity |
||
|
event type |
M |
Provide Conference event type (i.e., Creation). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
list of potential conferees |
C |
Provide, when available, the identities to be invited to or allowed to join the provisioned (i.e., future) conference. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance |
|
temporary conference URI |
||
|
potential conference start date and time |
C |
Provide, when available, the date and start time of the conference that is being created. This is statically provisioned information and is not correlated to the timestamp requirements for LI |
|
potential conference end date and time |
C |
Provide, when available, the date and end time of the conference that is being created. This is statically provisioned information and is not correlated to the timestamp requirements for LI |
|
recurrence information |
C |
Provide, when available, information concerning the frequency or pattern of recurrence of the created conference. Will be NULL if a single instance of a conference is created. |
|
identity(ies) of conference controller |
C |
Provide, when available, identity(ies) of parties that have control privileges on the conference. |
Table 11.15: Conference Service Update REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPU |
||
|
observed IMPI |
C |
Provide at least one and others when available. |
|
observed other identity |
||
|
event type |
M |
Provide Conference event type (i.e., Conference Update). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful interception identifier |
M |
Shall be provided. |
|
list of potential conferees |
C |
Provide, when available, the identities to be invited to or allowed to join the provisioned (i.e., future) conference. |
|
conference URI |
C |
Provide at least one and others when available; provide the URI associated with the conference under surveillance. |
|
temporary conference URI |
||
|
potential conference start date and time |
C |
Provide, when available, the date and/or start time of the conference that is being created. This is statically provisioned information and is not correlated to the timestamp requirements for LI. |
|
potential conference end date and time |
C |
Provide, when available, the date and/or end time of the conference that is being created. This is statically provisioned information and is not correlated to the timestamp requirements for LI. |
|
recurrence information |
C |
Provide, when available, information concerning the frequency or pattern of recurrence of the created conference. Will be NULL if a single instance of a conference is created. |
|
identity(ies) of conference controller |
C |
Provide, when available, identity(ies) of parties that have control privileges on the conference. |
11.6 CC for IMS Conference Services
The interface protocols and data structures defined in Annex B.11.2 have been enhanced to cater for the requirements of IMS Conferencing services. In particular, media types (bearers) that require multicasting at the MRFP, a party identifier is needed to identify the source of that bearer stream. The enhanced data structure also allows for the reporting of separate media streams for each user on the conference.